Invoice Ninja n8n integrationAutomate Invoice Ninja with n8n.

This writes a line into the bank transactions of Invoice Ninja, useful when the movement comes from somewhere other than a bank connector. Nothing is required, everything sits in Additional Fields.

• Amount: the value of the movement, often pulled from the step before with {{ $json.field }}.
• Base Type: CREDIT for a deposit, DEBIT for a withdrawal.
• Bank Integration Name or ID: the account the line belongs to, picked from the list or given as an ID through an expression.
• Date and Description: when it happened, and the wording that appears on the statement.

Removing a line takes a single value. The operation deletes the bank transaction whose identifier you hand it, and nothing else.

• Bank Transaction ID: required, the identifier of the line to drop, usually carried over from a listing step as {{ $json.field }}.
• API Version: v4 or v5, matching the instance the credential points at.

One identifier in, one bank transaction out. The operation retrieves the data of a single line so the rest of the workflow can decide what to do with it.

• Bank Transaction ID: required, the identifier of the line to read.
• API Version: v4 or v5, kept consistent across every Invoice Ninja node of the workflow.

Listing the bank feed comes with the usual pair of switches, and they decide how much of it the workflow actually sees.

• Return All: on, n8n chains the API pages and brings back every bank transaction; off, it stops at Limit.
• Limit: the maximum number of transactions returned when Return All stays off, handy while you are still testing.

Reconciliation lives in this operation: it links a bank transaction to a payment, so the movement stops being an orphan line in the feed.

• Bank Transaction ID: required, the line to match.
• Payment Name or ID: the payment to tie it to, chosen from the list or supplied as an ID through an expression.

A new client record gets built from optional blocks rather than a fixed form, which is why nothing here is mandatory.

• Contacts: a repeatable block where First Name, Last Name, Email and Phone describe the people to bill.
• Billing Address and Shipping Address: the two address blocks, with Street Address, City, Postal Code and Country Code Name or ID.
• Additional Fields: Client Name, VAT Number, Website, Private Notes and the rest of the profile.

The account disappears from Invoice Ninja once this runs, so it belongs behind a step that is sure of its target.

• Client ID: required, the identifier of the account to remove.
• API Version: v4 or v5, the same value used everywhere else in the workflow.

Reading one account gives the workflow the details the trigger payload does not carry on its own, and it can bring the billing history along.

• Client ID: required, the identifier of the account to read.
• Include: set to Invoices, the response also carries the client's invoices, which saves a second call.

The client directory comes back as a list you can narrow before it ever reaches the next node.

• Return All: on, every client comes through page after page; off, the run stops at Limit.
• Status: Active, Archived or Deleted, to keep a sync on live accounts only.
• Created At and Updated At: date filters for an incremental run rather than a full reload.

Booking a cost takes one call, and the 17 fields of Additional Fields decide how much detail lands in the books.

• Amount: what was spent.
• Vendor Name or ID and Category Name or ID: who was paid and under which heading, from the list or as an ID through an expression.
• Billable: on when the cost is meant to be passed back to a client.
• Expense Date, Payment Type and Transaction Reference: when, how, and under which reference it was settled.

An expense that should never have been booked leaves the ledger here, one record per execution.

• Expense ID: required, the identifier of the cost to remove.
• API Version: v4 or v5, aligned with the instance behind the credential.

Pulling a single cost back gives the workflow something to quote, attach or compare later on.

• Expense ID: required, the identifier of the expense to read, commonly supplied as {{ $json.field }} from the step before.
• API Version: v4 or v5, matching the rest of the workflow.

Costs come back as a list, and the two switches below decide whether that list is complete or just a sample.

• Return All: on, n8n follows the API pages until every expense is in; off, it stops at Limit.
• Limit: the maximum number of expenses to bring back, which is the sane setting while a workflow is being built.

Here is where a document actually comes into existence, with its lines and its 23 optional fields.

• Invoice Items: the repeatable block of lines, each with Description, Cost, Hours and Service.
• Client Name or ID: the account being billed, from the list or as an ID through an expression.
• Invoice Status: 1 for Draft, 2 for Sent.
• Due Date, Tax Name 1 and Tax Rate 1: the terms and the tax line carried on the document.
• Email Invoice: on, the document is emailed as part of the same call.

One identifier, one invoice gone from Invoice Ninja. Straightforward, and worth guarding with a condition upstream.

• Invoice ID: required, the identifier of the document to remove.
• API Version: v4 or v5, consistent with the credential's instance.

Sending is its own operation, separate from creation, which means a document can be reviewed first and mailed later by another workflow.

• Invoice ID: required, the identifier of the invoice to send.
• API Version: v4 or v5, matching the instance.

Reading one document is what turns a trigger payload into something the next steps can use, especially when the client details matter.

• Invoice ID: required, the identifier of the invoice to read.
• Include: set to Client, the response carries the client alongside the invoice.

The receivables workhorse. Its 7 options let the list arrive already filtered instead of sorted after the fact.

• Client Status: All, Paid, Unpaid or Overdue.
• Return All: switched on, every matching invoice comes back page after page, one API call chained to the next until nothing is left to fetch; switched off, the run stops as soon as it hits Limit.
• Invoice Number and Status: to target one document, or to keep Archived and Deleted records out.

Recording cash against a document is what moves an invoice out of the chasing list, and this operation does it in one step.

• Invoice Name or ID: the document being paid, from the list or as an ID through an expression.
• Amount: the sum received, which can differ from the invoice total on a partial settlement.
• Payment Type: Bank Transfer, Cash, SEPA and the rest of the list.
• Transfer Reference: the bank reference, so the line can be found again later.

Cash entered against the wrong invoice is corrected here, by removing the payment record itself.

• Payment ID: required, the identifier of the payment to remove.
• API Version: v4 or v5, the same version the rest of the workflow uses.

A single payment comes back with its detail, and optionally with the account it belongs to.

• Payment ID: required, the identifier of the payment to read.
• Include: set to Client, the client travels back with the payment in the same response.

Cash-in history arrives as a list, filtered on dates or on the state of the records.

• Return All: on, n8n pages through every payment rather than stopping at the first batch that comes back; off, Limit decides where it stops.
• Created At and Updated At: the pair of date filters that turns a full reload into a short, incremental daily or weekly run instead.
• Include: set to Client, each payment carries its account, which saves a lookup per row.

A quote lands in Invoice Ninja with its line items already filled in, and the created record comes back into the workflow.

• Invoice Items: the repeating collection that holds the quote lines, one entry per Add Invoice Item.
• Client Name or ID: choose the client from the list, or pass an identifier through an expression, a snippet like {{ $json.field }} that reads a value from the incoming item.
• Quote Status: two values are offered, 1 (Draft) and 2 (Sent).
• Due Date: a date-time value, set in Additional Fields.

Removing a quote from Invoice Ninja takes one identifier and nothing else. The call hits a single record, so most workflows put a check step in front of it.

• Quote ID: the required identifier of the quote to remove. A required field left empty stops the node before it runs, so feed it from an expression such as {{ $json.field }} rather than typing it by hand.
• API Version: pick v4 or v5 to match the Invoice Ninja instance behind the credential.

Sending a quote out is its own operation: the workflow points at one quote and Invoice Ninja sends it by email. No template step and no mail node sit in between.

• Quote ID: the required identifier of the quote to send, typically carried over from the node that created or fetched it, for example {{ $json.field }}.
• API Version: the same v4 or v5 choice as the rest of the node.

One quote, read by its identifier, with the data Invoice Ninja returns for that record. Useful whenever a later branch needs the quote itself and not just its number.

• Quote ID: required, the identifier of the quote to read.
• Include: the Options collection offers one value, client.

This one reads several quotes in a single node, which is what reporting and export workflows run on.

• Return All: switched on, n8n walks through the API pages and brings back every quote; switched off, Limit caps how many items come out.
• Status: three values, active, archived and deleted.
• Quote Number: a text value in the Options collection, for narrowing the read down.
• Created At and Updated At: date-time values in the same collection.

Billable time gets a home here: the operation writes a task into Invoice Ninja, with or without the hours already logged against it.

• Time Logs: the repeating collection for the logged periods, one entry per Add Time Log.
• Client Name or ID and Project Name or ID: both come from a dropdown, and both accept an identifier through an expression when the value arrives from an earlier node.
• Duration (Hours): a number, set in Additional Fields.

Tasks pile up fast when a workflow creates them automatically. This operation removes one of them, identified by its own ID.

• Task ID: required. It is the Invoice Ninja identifier of the task, not its description, and an empty value stops the node before the call goes out.
• API Version: v4 or v5, matching the instance the credential points at.

Reading a single task gives the workflow what Invoice Ninja holds on it, which is the usual first step before a branch decides what to do next.

• Task ID: required, the identifier of the task to read, often passed as {{ $json.field }} from the node before it.
• Include: one value here too, client.

Bulk reading of tasks, for the workflows that count hours rather than handle them one by one.

• Return All: on, n8n follows the API pages until every task has been read; off, Limit sets the maximum number of tasks returned.
• Include: the Options collection offers client.
• API Version: v4 or v5.