Linking Invoice Ninja as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more

The Invoice Ninja connector syncs clients, credits, expense categories, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

Enter your Invoice Ninja API token to pull your invoicing data.

You can create an API token in Invoice Ninja under Settings > Account Management > Integrations > API tokens.

Self-hosted users should set the API URL to their own Invoice Ninja host (for example https://invoices.example.com). Leave it blank to use the hosted Invoice Ninja (https://invoicing.co).

You'll be asked for:

API token

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

All Invoice Ninja tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Type	Required
`API token`	password	Yes
`API URL (self-hosted only)`	text	No

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`bank_transactions`	A transaction imported from a connected bank feed, with its match state against invoices, payments, and expenses.	Full refresh	—	—
`clients`	A customer you invoice. Contacts are nested under each client as a `contacts` array.	Full refresh	—	—
`credits`	A credit note reducing what a client owes.	Full refresh	—	—
`expense_categories`	A category used to classify expenses.	Full refresh	—	—
`expenses`	A business expense, optionally billable to a client.	Full refresh	—	—
`invoices`	A bill sent to a client, with line items, totals, and payment status.	Full refresh	—	—
`payments`	A payment recorded against one or more invoices.	Full refresh	—	—
`payment_terms`	A reusable net payment term (e.g. Net 30) offered to clients.	Full refresh	—	—
`products`	A reusable catalog item that can be added to invoices and quotes.	Full refresh	—	—
`projects`	A project used to group tasks and expenses for a client.	Full refresh	—	—
`purchase_orders`	An order sent to a vendor to purchase goods or services.	Full refresh	—	—
`quotes`	A proposal sent to a client that can be converted into an invoice.	Full refresh	—	—
`recurring_invoices`	A template that automatically generates invoices on a schedule.	Full refresh	—	—
`tasks`	A unit of tracked work, often billed by time, belonging to a project or client.	Full refresh	—	—
`task_statuses`	A workflow status (Kanban column) a task can be in. Resolves the `status_id` on tasks.	Full refresh	—	—
`tax_rates`	A named tax rate applied to invoice and quote line items.	Full refresh	—	—
`users`	A user of the Invoice Ninja company. Resolves `user_id` and `assigned_user_id` on other records.	Full refresh	—	—
`vendors`	A supplier you pay. Contacts are nested under each vendor as a `contacts` array.	Full refresh	—	—

Troubleshooting

If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.