Resources · Make integration

Invoice Ninja Make integrationAutomate Invoice Ninja with Make.

Billing runs on small manual steps, and Make can take most of them over. The Invoice Ninja Make integration links your account to a scenario, the automation you build from modules, and opens 47 of them: 6 triggers, 33 actions, 8 searches. Start with one.

Try the Invoice Ninja integration on MakeSee the 47 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Invoice Ninja Make integration actually do?

It plugs your Invoice Ninja account into Make so billing records move without anyone pushing them. A module is one brick of a scenario: a trigger that starts it, an action that writes something, or a search that reads. Invoice Ninja brings 47 of them, and you only need the two or three that match the job you have in mind.

All six triggers here are instant, which in Make means Invoice Ninja calls a webhook, a short signal sent to Make the moment something happens, instead of Make asking over and over. Each module run on each item costs one operation, the unit your Make plan counts, so a scenario that answers a single event stays cheap while one that reads long lists does not.

Three jobs come up again and again. Client intake: a signup form fires Create a Client, and the record exists before anyone opens the app. Cash tracking: Watch New Payment passes a payment to the tools that need it the second it lands. Catalog upkeep: List Products reads what you sell and Update a Product writes the new price back, one run instead of an afternoon of typing.

Two limits are worth knowing before you build. On the Invoice Ninja side the app expects a paid Pro or Enterprise account, so a free workspace will not connect. And the official app documentation carries a warning of its own: it was generated by AI from Invoice Ninja's docs and may contain mistakes, which is a fair reason to test each module on one throwaway record first.

Make is not the only route. Invoice Ninja also exists as a node in n8n, so the real question is where your team already works and who maintains the thing once it runs. The n8n vs Make comparison sets out the criteria, the Invoice Ninja n8n integration page covers the node side, and Make training helps if you would rather learn the editor than copy a recipe.

Connect

How do you connect Invoice Ninja to Make?

  1. 01

    Copy your API token

    In Invoice Ninja, open Settings, then Advanced Settings, then API Tokens, and copy the token shown on screen. Check the plan while you are there: the app works with a paid Pro or Enterprise Invoice Ninja account.

  2. 02

    Add a module and start the connection

    Back in Make, drop an Invoice Ninja module into your scenario and click Create a connection. A connection is your Invoice Ninja account linked to Make once, then reused by every Invoice Ninja module you add later, so this is a one-time job.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, though naming it after the workspace it points to saves confusion later. Paste the authentication credentials you copied from Invoice Ninja, or follow the instructions on screen, and save.

First scenario

Your first scenario, step by step

GoalWhen a new client is added in Invoice Ninja, Make creates the task that starts the onboarding.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Nothing else is on the canvas yet, and that is fine: a scenario is a chain of modules, and yours will have two of them.

  2. 02

    Place Watch New Client

    Search Invoice Ninja by name, pick Watch New Client, then click Create a webhook followed by Create a connection. This trigger is instant, so Invoice Ninja will call Make the moment a client is added.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and add Create a Task. Once the connection exists, Make lists what it can write, and you map into it the data the trigger passed along.

  4. 04

    Test with Run once

    Click Run once, then add a client in Invoice Ninja. The scenario runs a single time and shows you the bundles, the items that travelled from one module to the next, so you can read what the trigger sent and what the task received.

  5. 05

    Switch it on

    Turn the scenario on and leave it alone. An instant trigger has no interval to set: the run starts when Invoice Ninja calls, not when a clock says so. Check the history after the first real client to confirm the task landed where you expect.

Triggers

What starts a scenario

6 modules start a scenario when something happens in Invoice Ninja. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Invoice Ninja as soon as it happens.

Invoice Ninja1Watch New Client

Watch New Client

Instant trigger

In Make“Triggers when a new client is added.”

A new client record is the starting gun for everything else, and Watch New Client is what lets Make hear it. The scenario begins the moment the client is added in Invoice Ninja.

How it fires
instant. Invoice Ninja calls Make through a webhook as soon as the client is saved, so there is no interval to set.
When to use it
a studio that wants every new client to arrive with a welcome message and a folder already created.
Watch out
clients created by an import land here too, so filter early if a bulk load would otherwise fire hundreds of runs.
Invoice Ninja2Watch New Expense

Watch New Expense

Instant trigger

In Make“Triggers when a new expense is added.”

Expenses get recorded and then forgotten. Watch New Expense makes each one an event, so the rest of the chain can react while the receipt is still fresh.

How it fires
instant. The app pings Make the moment the expense is recorded, through a webhook rather than a schedule.
When to use it
an IT services firm that copies every billable expense into the client's project file the same day.
Watch out
the trigger tells you an expense exists, nothing more, so read it back with Get an Expense when the next step needs its content.
Invoice Ninja3Watch New Invoice

Watch New Invoice

Instant trigger

In Make“Triggers when a new invoice is added.”

Every invoice that appears in Invoice Ninja can push the rest of the paperwork along. Watch New Invoice is the entry point for anything that should happen once a document exists.

How it fires
instant. Invoice Ninja sends the call itself when the invoice appears, so Make is not polling on a clock.
When to use it
a print shop that files a copy of each invoice in shared storage and drops a line in the finance channel.
Watch out
invoices your own scenarios create will trigger it as well, which is how an accidental loop gets built.
Invoice Ninja4Watch New Payment

Watch New Payment

Instant trigger

In Make“Triggers when a new payment is added.”

Money landing is the event most teams want to hear about first. Watch New Payment starts a scenario as soon as a payment is recorded in Invoice Ninja.

How it fires
instant. The webhook fires as the payment is saved, which is why nothing here depends on a scheduling interval.
When to use it
a design studio that thanks the client and releases the delivery as soon as the payment shows up.
Watch out
a recorded payment is not the same as a cleared one, so agree with your finance side on what the scenario is allowed to promise.
Invoice Ninja5Watch New Quote

Watch New Quote

Instant trigger

In Make“Triggers when a new quote is added.”

Quotes are where a deal becomes real, and Watch New Quote gives Make the signal. Anything that should accompany a quote can start from here.

How it fires
instant. Make hears about the quote through a webhook the moment it exists, not on a timer.
When to use it
a moving company that opens a follow-up reminder for the salesperson each time a quote is issued.
Watch out
the trigger covers the quote appearing, not the client answering, so the follow-up logic belongs in the modules after it.
Invoice Ninja6Watch New Task

Watch New Task

Instant trigger

In Make“Triggers when a new task is added.”

Tasks created in Invoice Ninja can drive the work that happens outside it. Watch New Task hands each new one to Make as it is created.

How it fires
instant. The task reaches Make by webhook as soon as it is created, without any polling.
When to use it
a consultancy that mirrors billable tasks into the project board the team actually looks at.
Watch out
if another scenario also creates tasks, this trigger will catch its own output, so keep the two sides clearly separated.
Modules

What Invoice Ninja can do inside a scenario

Invoice Ninja gives you 41 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Invoice Ninja1

Create a Client

Action

In Make“Creates a client.”

Create a Client writes a new client record in Invoice Ninja from data another module gathered, so nobody retypes a name, an address and a contact by hand.

When to use it
a signup form on your site fills the record before the first invoice is even discussed.
Watch out
the module creates every time it runs, so a scenario that fires twice on the same event leaves you two clients to merge.
Invoice Ninja2

Create an Expense

Action

In Make“Creates an expense.”

Spending recorded somewhere else can land straight in the books. Create an Expense adds one expense to Invoice Ninja with the figures the previous module carried.

When to use it
a contractor forwards a receipt and the expense exists before the month closes.
Watch out
the module writes what it is given without judging it, so filter duplicates upstream rather than cleaning up after.
Invoice Ninja3

Create an Invoice

Action

In Make“Creates an invoice.”

This is the billing step itself. Create an Invoice turns whatever started the scenario into an invoice inside Invoice Ninja, ready for the usual review.

When to use it
an online order is paid and the invoice is drawn up while the customer is still on the confirmation page.
Watch out
an invoice written by a scenario is a real document, so test the mapping on one order before you let a full day of sales through.
Invoice Ninja4

Create a Payment

Action

In Make“Creates a payment.”

Money that arrived elsewhere gets recorded here. Create a Payment logs one payment in Invoice Ninja so the books match what the bank already knows.

When to use it
your payment processor confirms a transfer and the entry appears without anyone opening a statement.
Watch out
a payment logged twice is harder to spot than a missing one, so have the scenario react to a single confirmed event.
Invoice Ninja5

Create a Product

Action

In Make“Creates a product.”

Catalog work goes the same way. Create a Product adds one item to the Invoice Ninja product list so it can be picked on a quote or an invoice later.

When to use it
a new item is published in your store and the billing side learns about it the same minute.
Watch out
the module adds rather than checks, so an item already in the list will simply gain a twin.
Invoice Ninja6

Create a Quote

Action

In Make“Creates a quote.”

Before an invoice there is usually a quote. Create a Quote builds one in Invoice Ninja from the details a form or an earlier module supplied.

When to use it
a request for an estimate arrives at night and the quote is waiting when you open the laptop.
Watch out
a quote is a commitment, so keep the pricing values coming from a source you control, not from free text a visitor typed.
Invoice Ninja7

Create a Recurring Invoice

Action

In Make“Creates a recurring invoice.”

Retainers and subscriptions need a bill that comes back on its own. Create a Recurring Invoice sets that up in Invoice Ninja in a single run.

When to use it
a retainer client signs, and the recurring bill is configured the same day the contract is.
Watch out
this writes the recurring setup, not one invoice, so reach for it only when the billing genuinely repeats.
Invoice Ninja8

Create a Task

Action

In Make“Creates a task.”

Work that has to be tracked and billed starts as a task. Create a Task opens one in Invoice Ninja so the hours have somewhere to go.

When to use it
a project is approved and the task exists before the first hour is logged against it.
Watch out
tasks pile up quietly, so give the scenario a clear condition instead of opening one on every event that passes.
Invoice Ninja9

Delete a Client

Action

In Make“Deletes a client.”

Delete a Client removes a client record from Invoice Ninja. It is the tidy-up module rather than an everyday one.

When to use it
a test account created while you were building the scenario has to disappear before the workspace goes live.
Watch out
deleting is not a step you take back, so try it with Run once on a record you can afford to lose.
Invoice Ninja10

Delete an Expense

Action

In Make“Deletes an expense.”

An expense that should never have been recorded can be pulled back out by Delete an Expense, one record per run.

When to use it
an import ran twice and the second copy of each receipt has to go.
Watch out
point it at the copy and not the original, and confirm that logic before the scenario handles more than one record.
Invoice Ninja11

Delete an Invoice

Action

In Make“Deletes an invoice.”

Removing an invoice is a serious act. Delete an Invoice does exactly that, on the single invoice you point it at, and nothing else in the workspace moves.

When to use it
a draft left behind by a test run has to go.
Watch out
invoices carry accounting weight. Get sign-off from whoever keeps the books before a scenario is allowed to delete one.
Invoice Ninja12

Delete a Payment

Action

In Make“Deletes a payment.”

Delete a Payment takes one payment entry out of Invoice Ninja when it should not be there at all.

When to use it
a transfer was logged against the wrong client and the entry has to go before anyone reconciles.
Watch out
correcting is usually safer than deleting, so look at Update a Payment first and keep this for genuine mistakes.
Invoice Ninja13

Delete a Product

Action

In Make“Deletes a product.”

Items leave the catalog too. Delete a Product removes one product from the Invoice Ninja list so it stops appearing when someone builds a quote.

When to use it
a reference is discontinued in your store and the billing catalog should not keep offering it.
Watch out
the live catalog and past documents are different things, so agree with your team on what should happen to old lines before automating this.
Invoice Ninja14

Delete a Quote

Action

In Make“Deletes a quote.”

Quotes that will never turn into anything clutter the list, and Delete a Quote clears them one at a time.

When to use it
a prospect says no and the quote goes as part of closing the file.
Watch out
an old quote is sometimes worth keeping as history, so settle the rule before a scenario starts deleting on its own.
Invoice Ninja15

Delete a Recurring Invoice

Action

In Make“Deletes a recurring invoice.”

Delete a Recurring Invoice stops a repeating bill by removing its setup from Invoice Ninja.

When to use it
a subscription is cancelled and nothing more should be issued for that client.
Watch out
this targets the recurring setup, not the invoices already issued from it, so decide separately what happens to those.
Invoice Ninja16

Delete a Task

Action

In Make“Deletes a task.”

Tasks opened by mistake do not have to be closed by hand. Delete a Task removes the one you point at.

When to use it
an automated task was created on a false alarm and the list should not keep it.
Watch out
a task someone has already worked on is not the same as an empty one, so keep a human in the loop on this one.
Invoice Ninja17

Get a Client

Action

In Make“Gets a client.”

Get a Client reads one client record and hands its content to the rest of the scenario, changing nothing in Invoice Ninja.

When to use it
a contract needs the client details filled in automatically before it goes out for signature.
Watch out
the module has to know which client, so place it after something that identifies one rather than at the top of a scenario.
Invoice Ninja18

Get an Expense

Action

In Make“Gets an expense.”

One expense, read and passed on. Get an Expense pulls a single expense out of Invoice Ninja so another tool can work with its content.

When to use it
your accountant's folder needs the details of the expense that was just approved.
Watch out
reading is cheap but not free, every run counts as an operation, so avoid fetching the same expense in a loop.
Invoice Ninja19

Get an Invoice

Action

In Make“Gets an invoice.”

Get an Invoice fetches a single invoice and makes its content available to the modules that follow.

When to use it
a reminder message has to quote the exact document rather than a vague amount.
Watch out
it reads, it does not send, so pair it with whatever actually delivers the message to the client.
Invoice Ninja20

Get a Payment

Action

In Make“Gets a payment.”

Reading a payment back is often the last step of a check. Get a Payment returns one payment entry and nothing else.

When to use it
a finance channel gets a short confirmation line as soon as a transfer is recorded.
Watch out
it returns what Invoice Ninja holds at that moment, so read after the write, never before it.
Invoice Ninja21

Get a Product

Action

In Make“Gets a product.”

Get a Product looks up one catalog item and passes it down the scenario, which matters when a price or a label has to be exact.

When to use it
a quote is assembled from a form and the product details should come from the catalog, not from the visitor.
Watch out
one product per run, so a document with several lines needs a different design.
Invoice Ninja22

Get a Quote

Action

In Make“Gets a quote.”

The quote a client just accepted can be read straight back. Get a Quote returns that single quote for the next module to work with.

When to use it
an accepted quote has to be handed to the team that will deliver the work.
Watch out
reading a quote does not turn it into an invoice, that is a separate module and a separate decision.
Invoice Ninja23

Get a Recurring Invoice

Action

In Make“Gets a recurring invoice.”

Get a Recurring Invoice reads one recurring setup so the scenario knows what is currently billed on repeat.

When to use it
a support agent needs to see what a subscription contains without opening Invoice Ninja.
Watch out
it shows the setup, not the payments that came out of it, so do not treat its output as billing history.
Invoice Ninja24

Get a Task

Action

In Make“Gets a task.”

Get a Task brings one task back into the scenario, handy when a report needs its content rather than a link to it.

When to use it
a status summary sent to a client should describe the task in its own words.
Watch out
the task has to be identified first, so this module sits after a trigger or a search, never alone at the top.
Invoice Ninja25

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the escape hatch, covering what the other modules do not. It runs on the connection you already created and reaches any endpoint of the Invoice Ninja API.

When to use it
the thing you need lives in Invoice Ninja but has no module of its own among the 47.
Watch out
this one expects you to know the API, so keep it for the gap and build the rest with the ready-made modules.
Invoice Ninja26

Update a Client

Action

In Make“Updates a client.”

Update a Client changes an existing client record instead of creating another one, which keeps a single version of the truth in Invoice Ninja.

When to use it
a customer changes address in your own database and billing should not lag a month behind.
Watch out
the client has to exist already, so a trigger or a search has to identify it before this module runs.
Invoice Ninja27

Update an Expense

Action

In Make“Updates an expense.”

An expense rarely arrives complete. Update an Expense edits one that is already in Invoice Ninja, once the missing piece is known.

When to use it
a manager approves a spend and the record reaches its final state without a second entry.
Watch out
the scenario writes exactly what it is given, so send only the values you actually mean to change.
Invoice Ninja28

Update an Invoice

Action

In Make“Updates an invoice.”

Update an Invoice edits a document that already exists, so a correction does not leave a second invoice floating around.

When to use it
a line has to be fixed after a client call, before the document goes out.
Watch out
an invoice already sent lives in your client's inbox too, so agree internally on what a scenario may rewrite.
Invoice Ninja29

Update a Payment

Action

In Make“Updates a payment.”

Recorded payments sometimes need a correction, and Update a Payment applies it to the entry that is already there.

When to use it
a transfer was logged with the wrong details and the entry has to be put right.
Watch out
it edits one entry per run, so a batch of corrections needs a search feeding it one at a time.
Invoice Ninja30

Update a Product

Action

In Make“Updates a product.”

Prices move. Update a Product pushes the new value onto an item already sitting in the Invoice Ninja catalog.

When to use it
a price change is decided in your spreadsheet and the billing catalog follows the same day.
Watch out
the item has to exist, so a scenario that might meet a brand new reference needs Create a Product as its other branch.
Invoice Ninja31

Update a Quote

Action

In Make“Updates a quote.”

Update a Quote revises a quote in place, which is usually what a client wants after a quick call about one line.

When to use it
a discount is agreed and the document reflects it without anyone rebuilding it from scratch.
Watch out
revise before the client accepts rather than after, or the version they said yes to stops matching the one in the app.
Invoice Ninja32

Update a Recurring Invoice

Action

In Make“Updates a recurring invoice.”

Update a Recurring Invoice changes what a repeating bill contains, without rebuilding the setup around it.

When to use it
a client moves up a plan and the recurring amount follows the new contract.
Watch out
the change lands on the setup itself, so check separately what should happen to documents already issued from it.
Invoice Ninja33

Update a Task

Action

In Make“Updates a task.”

Update a Task edits a task that is already open, which is how progress recorded in another tool finds its way back into Invoice Ninja.

When to use it
a card moves to done on your project board and the task should say the same thing.
Watch out
two tools writing the same task will fight, so decide which one is the reference before wiring both directions.
Invoice Ninja34

List Clients

Search

In Make“Gets all clients.”

List Clients reads clients out of Invoice Ninja and passes them on, the module you want when a scenario needs the list rather than one record.

When to use it
a mailing audience is rebuilt from the billing side instead of being maintained twice.
Watch out
a search returns zero, one or many items, and everything after it runs once per item, so count the operations before you let it loose.
Invoice Ninja35

List Expenses

Search

In Make“Gets all expenses.”

Expenses are easier to handle in bulk. List Expenses hands the scenario what it finds, one item at a time for the modules that follow.

When to use it
an expense report is being assembled and the figures should come from the app, not from memory.
Watch out
an empty result is a perfectly normal outcome, so design the next step to survive a run that finds nothing.
Invoice Ninja36

List Invoices

Search

In Make“Gets all invoices.”

List Invoices goes looking for invoices and returns what matches, which is how a scenario gets a set of documents to work through.

When to use it
a dashboard is refreshed from the invoices that exist rather than from a copy someone keeps updating.
Watch out
how many come back depends entirely on the data, so never build the scenario as if exactly one invoice will arrive.
Invoice Ninja37

List Payments

Search

In Make“Gets all payments.”

Reconciliation starts with reading. List Payments returns the payment entries Invoice Ninja holds so another system can compare them with its own.

When to use it
a bank export has to be matched against what was recorded on the billing side.
Watch out
each returned item costs an operation in every module that follows, so narrow the search instead of pulling everything.
Invoice Ninja38

List Products

Search

In Make“Gets all products.”

List Products reads the catalog out of Invoice Ninja, item by item, for whatever needs to know what you sell.

When to use it
a store or a price sheet is rebuilt from the billing catalog so the two stop drifting apart.
Watch out
reading the catalog is not syncing it, the writing back is a separate module and a separate decision.
Invoice Ninja39

List Quotes

Search

In Make“Gets all quotes.”

Open quotes are only useful if someone looks at them. List Quotes returns the quotes that match, ready for a follow-up step.

When to use it
a reminder goes out on quotes that are still waiting for an answer.
Watch out
the search has no idea what a stale quote is, that rule lives in the filter you place after it.
Invoice Ninja40

List Recurring Invoices

Search

In Make“Gets all recurring invoices.”

List Recurring Invoices returns the repeating setups in Invoice Ninja, the practical way to audit what bills itself without anyone watching.

When to use it
someone asks what is being billed on repeat and the answer should not come from a spreadsheet.
Watch out
the list tells you what exists, not what was collected, so pair it with payments when the question is really about cash.
Invoice Ninja41

List Tasks

Search

In Make“Gets all tasks.”

List Tasks goes and fetches the tasks already recorded in Invoice Ninja and passes them on, one at a time, to whatever comes next in your scenario.

When to use it
a consultancy that gathers every task tied to a client before Make drafts the invoice.
Watch out
a search can return nothing, one task or a whole batch, and every module after it runs once per task, so each one costs an operation, the unit Make counts on your plan.
Need help

Need help automating Invoice Ninja with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Invoice Ninja Make integration free?
On the Make side, yes to start with. Invoice Ninja is a standard app, so it works from the Free plan, which runs 2 active scenarios, caps a run at 5 minutes and includes 512 MB of data transfer. What you consume is operations, one per module run per item, so a scenario that answers single events costs far less than one reading long lists. The catch sits on the other side: the app expects a paid Pro or Enterprise Invoice Ninja account, and a free workspace there will not connect.
02What do you need to connect Invoice Ninja to Make?
Three things. A Make account with a scenario open, an Invoice Ninja account on a paid Pro or Enterprise plan, and an API token taken from Invoice Ninja under Settings, then Advanced Settings, then API Tokens. In Make you add an Invoice Ninja module, click Create a connection, optionally name it in the Connection name field, then paste those credentials or follow the on-screen instructions. One detail trips people up: instant modules ask for Create a webhook before Create a connection.
03Does the Invoice Ninja trigger react in real time?
Yes. All six triggers here are instant, which means Invoice Ninja calls Make through a webhook as soon as the thing happens: a client added, an expense, an invoice, a payment, a quote, a task. There is no polling interval to choose and no clock to configure on the first module, and that is exactly why the setup asks you to create the webhook before the connection. Being instant is what lets a scenario answer a new payment while the customer is still on the page.
04What if a module is missing or a limit gets in the way?
Reach for Make an API Call. It runs on the connection you already created and calls any endpoint of the Invoice Ninja API, so anything the 47 listed modules do not cover is still within reach of the same scenario. Worth knowing as well: the official app documentation states that it was generated by AI from Invoice Ninja's own docs and may contain mistakes, so check any detail that matters in your own account, with Run once, before it touches real billing.
05Make or n8n for Invoice Ninja?
It depends on who will maintain it. Make gives you a visual editor, a connection set up once and reused by every module, and the 47 modules this page lists. n8n covers the same app with a node of its own, which suits teams already working in that environment and keen to keep the automation next to the rest. Neither choice changes what Invoice Ninja can do, only how you build it and who looks after it. The useful question is which editor the person responsible will still open happily in a year.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations