Resources · Make integration

Invoiced Make integrationAutomate Invoiced with Make.

Can Make create customers and invoices in Invoiced for you? Yes. The Invoiced Make integration offers 42 modules, 12 of them instant triggers. This guide is for finance and ops teams who bill with Invoiced, and it takes you from the API key to a first working scenario.

Try the Invoiced integration on MakeSee the 42 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Invoiced Make integration do for you?

The Invoiced Make integration links your billing account to Make, so invoices, customers, estimates and subscriptions can be created, read, updated or deleted by a scenario, the automation you build in Make. Invoiced can also call Make the instant something changes, which starts the scenario without anyone clicking.

Bill the moment a deal closes. Your CRM marks a deal as won, Create a Customer adds the client and Create an Invoice bills it. Nobody retypes a name or an amount.

Keep the account manager informed. Watch Invoice fires when an invoice is viewed, commented or paid; Get a Customer adds the client's details and the next app posts the alert where the team works.

Collect billable work as it happens. Each entry validated in a time tracker becomes a charge through Create a Pending Line Item, instead of a pile of lines typed at the end.

Some objects are only watched: tasks, notes, transactions and payment plans have triggers but no action module. Make an API Call fills that gap with the same connection. The same app often has an n8n node too; the n8n vs Make comparison lays out the differences, and Make training helps if this is your first scenario.

Connect

How do you connect Invoiced to Make?

  1. 01

    Copy your API key

    In the Invoiced dashboard, open Settings, then Developers, then API Keys. Copy the key shown on screen. The Make documentation asks for an active Invoiced account and this key.

  2. 02

    Open the connection window

    In Make, add any Invoiced module to your scenario and click Create a connection. A connection is your Invoiced account linked to Make once, then reused by every Invoiced module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the window, or follow the instructions Make shows on screen, then save. Make can now read and write in your Invoiced account for this scenario and the next ones.

First scenario

Your first scenario with Invoiced

GoalWhen a deal is marked won in your CRM, Make creates the customer in Invoiced and sends the bill.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick your CRM and the trigger that reacts to a won deal, then connect that account.

  2. 02

    Add Create a Customer

    Click the + on the right of the CRM module, search Invoiced and choose Create a Customer. Connect with your API key, then map the client's details from the deal bundle, the item passed along by the CRM.

  3. 03

    Add Create an Invoice

    Add one more module with the + and pick Create an Invoice. Map the customer returned by the previous module, then what the deal says was sold.

  4. 04

    Test with Run once

    Click Run once and mark a test deal as won. Open each module's bubble to read the bundles it received, and check the new customer and invoice in Invoiced.

  5. 05

    Schedule and switch it on

    Set the schedule on the CRM module (every 15 minutes by default for a scheduled trigger) and switch the scenario on. From then on, each won deal is billed without a copy and paste.

Triggers

What can start an Invoiced scenario?

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

Invoiced1New Event

New Event

Instant trigger

In Make“Triggers when a new event is appeared.”

One trigger for the whole account: every new event Invoiced records reaches your scenario as a bundle, the item that flows to the next module. It spares you from wiring a separate trigger per object type.

How it fires
instant. Invoiced calls Make through a webhook as soon as the event appears.
When to use it
you want one activity log, for instance a sheet where the finance lead reads everything that happens in Invoiced.
Watch out
all kinds of records arrive mixed in the same stream, so the modules after it must handle each kind.
Invoiced2Watch Contact

Watch Contact

Instant trigger

In Make“Triggers when a new contact is created.”

You learn about each new contact in Invoiced right away, and the contact comes along as a bundle your next module can map into another tool.

How it fires
instant. Invoiced notifies Make through a webhook the moment the contact is created.
When to use it
copy every new billing contact into your email platform or CRM, so the person who receives invoices is known everywhere the team works.
Watch out
Make describes it for new contacts only, so don't count on it to report an edit to an existing one.
Invoiced3Watch Credit Note

Watch Credit Note

Instant trigger

In Make“Triggers when a credit note is created, updated, deleted, viewed or commented.”

You get a signal each time a credit note moves: created, updated, deleted, viewed or commented on. The whole life of a refund document becomes visible outside Invoiced.

How it fires
instant. Invoiced calls Make through a webhook as soon as one of those events happens.
When to use it
accounting wants a message when a credit is issued, or when a client reacts to it in a comment.
Watch out
one credit note can start the scenario several times over its life, and each run costs operations, the unit Make counts on your plan.
Invoiced4Watch Customer

Watch Customer

Instant trigger

In Make“Triggers when a customer is created, updated, deleted or merged.”

Keeps other tools in step with your Invoiced customer list: it starts the scenario when a customer is created, updated, deleted or merged with another record.

How it fires
instant. Invoiced pushes the change to Make through a webhook right away.
When to use it
your CRM or support desk should mirror billing customers, including the day two duplicates get merged into one.
Watch out
a deletion arrives as a bundle too. Decide what the next module does with a customer that no longer exists, not only with a new one.
Invoiced5Watch Estimate

Watch Estimate

Instant trigger

In Make“Triggers when an estimate is created, updated, deleted, viewed, commented or approved.”

Brings the life of your quotes into Make: an estimate created, updated, deleted, viewed, commented on or approved starts the scenario.

How it fires
instant. Invoiced calls Make through a webhook as soon as the estimate changes.
When to use it
sales wants to hear when a prospect opens a quote or approves it, without refreshing the dashboard.
Watch out
approval is one of six events it reports. A scenario designed for approvals also runs when someone simply views the estimate, so plan for every event.
Invoiced6Watch Invoice

Watch Invoice

Instant trigger

In Make“Triggers when an invoice is created, updated, deleted, commented, viewed or paid.”

Follows each invoice from start to finish: creation, update, deletion, comment, view and payment all start your scenario with the invoice as a bundle.

How it fires
instant. Invoiced sends each event to Make through a webhook the moment it happens.
When to use it
tell the account manager that a client opened or paid an invoice, or push paid invoices into your bookkeeping sheet.
Watch out
the same invoice comes back at every stage of its life. The bundle for a payment belongs to an invoice that already came through when it was created.
Invoiced7Watch Line Item

Watch Line Item

Instant trigger

In Make“Triggers when a line item is created, updated or deleted.”

Gives you a view on billable lines: a line item created, updated or deleted in Invoiced starts the scenario straight away.

How it fires
instant. Invoiced calls Make through a webhook as soon as the line changes.
When to use it
log every line change in a sheet so someone can review charges before they reach a client.
Watch out
lines change often. Each creation, edit or deletion is its own run and its own set of operations, which adds up fast on a busy account.
Invoiced8Watch Note

Watch Note

Instant trigger

In Make“Triggers when a note is created, updated or deleted.”

Surfaces what your team writes in Invoiced: a note created, updated or deleted starts the scenario with the note as a bundle.

How it fires
instant. Invoiced notifies Make through a webhook right after the note is saved or removed.
When to use it
collections staff log what a client promised on the phone, and the channel where overdue accounts are discussed should see it too.
Watch out
an edited note comes through again, so the channel may show two versions of the same text. Notes have no action module in Make.
Invoiced9Watch Payment Plan

Watch Payment Plan

Instant trigger

In Make“Triggers when a payment plan created, updated, deleted.”

Flags every change to a payment plan: set up, edited or deleted, the plan reaches your scenario as a bundle.

How it fires
instant. Invoiced calls Make through a webhook as soon as the plan changes.
When to use it
the person who follows clients paying in instalments should hear about a new plan without checking each account.
Watch out
Make lists no action module for payment plans. To change one from a scenario, you go through Make an API Call with the same connection.
Invoiced10Watch Subscription

Watch Subscription

Instant trigger

In Make“Triggers when a subscription is created, updated or deleted.”

Reports the subscriptions that appear, change or disappear in Invoiced, each one as a bundle ready to map into another app.

How it fires
instant. Invoiced sends the change to Make through a webhook without delay.
When to use it
welcome a new subscriber in your onboarding tool, or warn customer success when a subscription is deleted.
Watch out
a scenario that also runs Create a Subscription or Update a Subscription will wake this trigger with its own changes. Keep those in separate scenarios so nothing loops.
Invoiced11Watch Task

Watch Task

Instant trigger

In Make“Triggers when a task is created, updated, deleted or completed.”

Mirrors your Invoiced tasks elsewhere: a task created, updated, deleted or completed starts the scenario.

How it fires
instant. Invoiced calls Make through a webhook as soon as the task changes.
When to use it
copy follow-up tasks into the to-do tool your team already opens every morning, and close them there when they are completed in Invoiced.
Watch out
tasks have no create or update module in Make. This trigger only reads them; Make an API Call is the path for anything more.
Invoiced12Watch Transaction

Watch Transaction

Instant trigger

In Make“Triggers when a transaction is created, updated or deleted.”

Puts transactions on your radar: each one created, updated or deleted in Invoiced starts the scenario with its details as a bundle.

How it fires
instant. Invoiced notifies Make through a webhook the moment the transaction changes.
When to use it
send each new transaction to the spreadsheet your accountant reconciles, instead of exporting files from the dashboard.
Watch out
no module in the list creates or searches transactions, so this trigger is your main window on them.
Modules

What can Make do in Invoiced?

Invoiced gives you 30 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Invoiced1

Create a Credit Note

Action

In Make“Creates a credit note.”

Issues a credit note from your scenario, so a refund or a billing correction gets its document without anyone opening Invoiced.

When to use it
a support ticket closes with a goodwill gesture and finance wants the credit on file.
Watch out
each run issues one more credit note. Try it with Run once on a test customer before the scenario goes live.
Invoiced2

Create a Customer

Action

In Make“Creates a customer.”

Adds a new customer record to Invoiced from data captured elsewhere, a signup form or a won deal.

When to use it
the first billing step after a sale, before any invoice or subscription can go out.
Watch out
a module runs every time a bundle reaches it, so a returning client can end up twice. Put Search Customers in front when that can happen.
Invoiced3

Create an Estimate

Action

In Make“Creates an estimate.”

Drafts a quote in Invoiced from what your form or CRM already knows, so sales starts from a filled estimate instead of a blank one.

When to use it
a quote request lands through your website and someone should only review it before it goes out.
Watch out
Watch Estimate will report this creation too, which is handy for a follow-up scenario but a trap if both sit in one.
Invoiced4

Create an Invoice

Action

In Make“Creates an invoice.”

Produces an invoice in Invoiced from a bundle, for example an order or a signed contract coming from another app.

When to use it
bill a client as soon as the work is confirmed elsewhere, without copying amounts by hand.
Watch out
a scenario that runs twice on the same order bills twice. Search Invoices before this module lets you check first.
Invoiced5

Create a Pending Line Item.

Action

In Make“Creates a line item.”

Records a single charge as a pending line item, so billable work can pile up line by line instead of being typed into an invoice in one go.

When to use it
each delivery or approved timesheet in another tool should become one line on the customer's account.
Watch out
this module adds a line, while Create an Invoice builds a whole invoice. Pick the one that matches how you bill.
Invoiced6

Create a Subscription

Action

In Make“Creates a subscription.”

Signs a customer up for a subscription in Invoiced straight from your scenario, so nobody enters the plan a second time.

When to use it
a client picks a plan on your site or in your app, and the subscription must exist in Invoiced as well.
Watch out
Watch Subscription reports this creation as well, so a scenario listening to subscriptions will run right after it.
Invoiced7

Delete a Credit Note

Action

In Make“Deletes a credit note.”

Removes a credit note from Invoiced as soon as the scenario reaches this module, for instance one issued by mistake.

When to use it
a cleanup scenario that clears credit notes created while you tested another automation.
Watch out
a deletion cannot be undone from Make. Try it on one test item before you map it to real data.
Invoiced8

Delete a Customer

Action

In Make“Deletes a customer.”

Erases a customer record in Invoiced, the right move when a record was created twice or a prospect never became a client.

When to use it
your CRM closes a lead as lost and the billing side should not keep an empty customer.
Watch out
nothing in Make restores it. Run Get a Customer first and store the result if you may need the details later.
Invoiced9

Delete an Estimate

Action

In Make“Deletes an estimate.”

Takes an estimate out of Invoiced when a deal falls through or a quote was created twice by accident.

When to use it
an opportunity is marked lost in your CRM and the quote attached to it should go too.
Watch out
Watch Estimate reports deletions, so any scenario listening to estimates will run as well.
Invoiced10

Delete an Invoice

Action

In Make“Deletes an invoice.”

Deletes an invoice in Invoiced, which suits invoices made by a test or by a scenario that ran once too often.

When to use it
clean up after Run once sessions that created real invoices on a test customer.
Watch out
the delete is final from Make's side. Map the exact invoice from Search Invoices rather than typing a reference by hand.
Invoiced11

Delete a Pending Line Item

Action

In Make“Deletes a line item.”

Removes one pending line item from Invoiced, for a charge that was logged by error or cancelled later.

When to use it
a timesheet entry is withdrawn in your tracking tool and the matching charge has to disappear with it.
Watch out
Watch Line Item fires on deletions, so a scenario listening to lines will see this one leave.
Invoiced12

Delete a Subscription

Action

In Make“Deletes a subscription.”

Deletes a subscription in Invoiced when the customer relationship behind it has ended.

When to use it
a user closes their account in your product, and the subscription record should not stay behind in billing.
Watch out
Watch Subscription reports deletions too. Check which scenarios listen to subscriptions before your first Run once.
Invoiced13

Get a Credit Note

Action

In Make“Retrieves a credit note.”

Fetches one credit note from Invoiced and passes it on as a bundle, ready for the next modules to map into a message or a sheet.

When to use it
an earlier module tells you which credit note matters and you need its content to explain it to the client.
Watch out
it reads one credit note. To find several by criteria, Search Credit Notes is the module.
Invoiced14

Get a Customer

Action

In Make“Retrieves a customer.”

Reads a single customer record, which lets you enrich an alert or an email with the client's details instead of a bare invoice.

When to use it
Watch Invoice fired and the message in your team chat should name the customer, not only the invoice.
Watch out
reading counts as well. Each Get uses one operation, like any other module.
Invoiced15

Get an Estimate

Action

In Make“Retrieves an estimate.”

Returns one estimate with its content as a bundle, so the quote can travel to the tool where the work will actually happen.

When to use it
a quote was approved and your project tool needs its details to open the job for the delivery team.
Watch out
to list estimates instead of reading one, switch to Search Estimates.
Invoiced16

Get an Invoice

Action

In Make“Retrieves an invoice.”

Loads one invoice from Invoiced so a later module can quote it, attach it to a ticket or copy it into a report.

When to use it
a client writes to your helpdesk about a bill and the agent should see that invoice in the ticket without searching for it.
Watch out
Get needs to know which invoice; map it from an earlier module rather than typing it.
Invoiced17

Get a Pending Line Item

Action

In Make“Retrieves a line item.”

Looks up one pending line item, the charge waiting on a customer account, and hands it to the next module.

When to use it
before you update or delete a charge, confirm what it holds so the scenario acts on the right line.
Watch out
there is no search module for lines, so this module works best after a trigger or module that already points to the line.
Invoiced18

Get a Subscription

Action

In Make“Retrieves a subscription.”

Pulls one subscription from Invoiced, with what the account stores about it, as a bundle your next modules can read.

When to use it
a support tool asks which subscription a caller is on, and the answer should come from billing, not from memory.
Watch out
no search module exists for subscriptions, so you reach this one through a known subscription.
Invoiced19

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Invoiced API to your scenario: any endpoint can be called with the connection you already set up.

When to use it
you need to act on tasks, notes, transactions or payment plans, which the other modules only watch.
Watch out
you write the request yourself, so keep the Invoiced API reference open and test with Run once.
Invoiced20

Update a Credit Note

Action

In Make“Updates a credit note.”

Changes an existing credit note in Invoiced instead of issuing a second one, so the client keeps a single document.

When to use it
the credit agreed with a client moves after a second discussion that was logged in your support tool.
Watch out
Watch Credit Note fires on updates. A scenario that updates credit notes and also listens to them can run itself in circles.
Invoiced21

Update a Customer

Action

In Make“Updates a customer.”

Writes new details into a customer who already exists in Invoiced, so billing follows what sales knows.

When to use it
the client's details change in your CRM, and the next invoice must go to the right place.
Watch out
choose it over Create a Customer whenever the client exists; otherwise two records split the history.
Invoiced22

Update an Estimate

Action

In Make“Updates an estimate.”

Edits an estimate that is still in play, so the prospect sees one quote that moves with the discussion.

When to use it
the scope of a deal grows in your CRM during negotiation and the quote in Invoiced has to follow.
Watch out
an update is an event for Watch Estimate, so a listening scenario will run again.
Invoiced23

Update an Invoice

Action

In Make“Updates an invoice.”

Modifies an invoice that is already in Invoiced, which avoids deleting it and creating a fresh one.

When to use it
a client asks for a correction, the manager approves it in another tool, and the invoice changes without manual edits.
Watch out
Watch Invoice listens to updates. Test with Run once to see which scenarios wake up.
Invoiced24

Update a Pending Line Item

Action

In Make“Updates a line item.”

Adjusts a pending line item already on the customer account, so the charge stays correct until it is invoiced.

When to use it
hours logged earlier were corrected in your time tracker, and the matching line must carry the new figure.
Watch out
each update is an event for Watch Line Item as well.
Invoiced25

Update a Subscription

Action

In Make“Updates a subscription.”

Changes a subscription in Invoiced from another system, so a plan switch made by the customer shows up in billing.

When to use it
a customer upgrades inside your app, and Invoiced should reflect the new plan without a support ticket.
Watch out
keep it away from a scenario that starts on Watch Subscription, or the two will trigger each other.
Invoiced26

Upload a File

Action

In Make“Uploads a new file.”

Sends a file into Invoiced from an earlier module, such as a PDF made by a document tool or an attachment received by email.

When to use it
a signed contract or a proof of delivery should sit in Invoiced, close to the billing record it supports.
Watch out
on the Free plan, Make handles files up to 5 MB.
Invoiced27

Search Credit Notes

Search

In Make“Searches for credit notes.”

Looks for credit notes that match your criteria and returns zero, one or several bundles, one per credit note found.

When to use it
before a call with a client who disputes a balance, gather every credit already granted to them.
Watch out
each bundle found runs the following modules once, so a broad search multiplies operations.
Invoiced28

Search Customers

Search

In Make“Searches for customers.”

Searches your Invoiced customer list and tells you whether a client is already there, with each match as its own bundle.

When to use it
right before Create a Customer, to avoid adding the same company a second time.
Watch out
zero results is a normal answer. Test that case with Run once so you know how the scenario behaves.
Invoiced29

Search Estimates

Search

In Make“Searches for estimates.”

Finds the estimates that fit what you ask for, which turns a pile of quotes into a short list you can act on.

When to use it
prepare a pipeline review by pushing open quotes into the sheet that sales discusses.
Watch out
several estimates mean several bundles, and each one runs the next modules separately.
Invoiced30

Search Invoices

Search

In Make“Searches for invoices.”

Returns the invoices that match your criteria, one bundle each, so a scenario can find a bill without anyone opening the dashboard.

When to use it
a payment arrives through another channel and you need the matching invoice before updating anything.
Watch out
the list has no search for line items or subscriptions; Get modules and Make an API Call cover those.
Need help

Need help automating Invoiced with Make?

A person reads every message.

FAQ

Questions about Invoiced and Make

01Is the Invoiced Make integration free?
Yes, on the Make side. Invoiced is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in credits, one per operation. Your Invoiced subscription is separate: you need an active account there, and its pricing page tells you which plan to pick.
02What do you need to connect Invoiced to Make?
An active Invoiced account and its API key. You find the key in the Invoiced dashboard under Settings, then Developers, then API Keys, and you copy it. In Make, add an Invoiced module, click Create a connection, give it a name if you like and paste the key. For a trigger, which is always instant with this app, click Create a webhook first and create the connection from that window. The connection is then reused by every Invoiced module in your scenarios.
03Do Invoiced triggers in Make fire in real time?
Yes. All 12 Invoiced triggers are instant: Invoiced calls Make through a webhook as soon as the event happens, so the scenario does not wait for the 15 minute default schedule that applies to scheduled triggers. This covers invoices, customers, estimates, credit notes, subscriptions, line items, notes, tasks, transactions, payment plans, contacts and the general event feed. Each trigger reports several kinds of change, such as creation, update or deletion, so the modules after it should expect all of them.
04What if an Invoiced module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Invoiced API with the same connection, which covers what the listed modules do not. The gap is clearest for tasks, notes, transactions and payment plans: Make can watch them but has no action module to create or change them. You write the request yourself, so test it with Run once before switching the scenario on. The Make documentation page for Invoiced also warns that its content is AI generated, so verify important details with Invoiced.
05Should you use Make or n8n for Invoiced?
It depends on where your automations already live. On Make, Invoiced comes with 42 modules: 12 instant triggers, 26 actions and 4 searches, plus Make an API Call for the rest of the API. The same app often has an n8n node as well, so compare the modules you need on each side before choosing. The comparison page linked above lists the criteria side by side; neither tool is ranked here, and your own list of needs decides.
Same platform

Other docs you might need on this stack.

Browse all integrations