Resources · Make integration

easybill Make integrationAutomate easybill with Make.

Can Make take the repetitive easybill work off your plate? The easybill Make integration gives you 44 modules, 5 of them instant triggers, covering documents, payments, customers, projects and tasks. This page walks you through the connection and a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the easybill Make integration do for you?

The easybill Make integration links your easybill account to Make, a no-code tool that chains apps together. You build a scenario (the automation itself) out of modules, which are single bricks: a trigger that starts things, an action that changes something, or a search that finds records. easybill tells Make when a document, payment, contact or customer changes, and Make can write back to it.

Payments that turn into work. Watch Document Payments fires as soon as easybill records a payment event, and Create a Task puts the next step in front of your team without anyone checking the bank feed by hand.

Documents that go out on their own. Create a Document opens the document, Create an Invoice Item adds each line, and Send a Document delivers it once the content is right. The data can come from a form, a CRM or a spreadsheet you already use.

A customer base that stays clean. Search Customers checks whether a person already exists before Create a Customer adds them, and Update a Customer corrects the record when another tool holds the newer details.

What Make does not do here: the 44 modules do not cover every corner of the easybill API. Make an API Call reaches the rest with the same connection. The Make documentation page for easybill is AI-generated and asks you to verify important details against easybill itself. On the Free plan you get 2 active scenarios; Make pricing lays out what the paid plans add.

easybill may also have an n8n node. If you are choosing between the two tools, n8n vs Make sets out the criteria, and Make training helps if the editor is new to you.

Connect

How do you connect easybill to Make?

  1. 01

    Add an easybill module

    In your scenario, click the +, search for easybill and pick any module. Then click Create a connection. With an instant module such as Watch Documents, click Create a webhook first, then Create a connection.

  2. 02

    Generate the API key in easybill

    In easybill, click your username in the top blue menu bar and open Profile and Settings. Scroll to the API Key section. No key there yet? Click Generate new key, then Save in the top right corner, and copy it.

  3. 03

    Paste the key into Make

    Back in Make, type a label in Connection name if you want one (the field is optional), paste the API key and confirm. That connection, your easybill account linked to Make, is reused by every easybill module you add later.

First scenario

Your first scenario: a task for every easybill payment

GoalWhen easybill reports a document payment event, Make creates a follow-up task in easybill for your team.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large + to place the first module. Search for easybill and choose Watch Document Payments.

  2. 02

    Connect the trigger

    Click Create a webhook, then Create a connection, and paste your easybill API key. The webhook is the address easybill calls whenever a payment event happens.

  3. 03

    Add the task

    Click the + on the right of the trigger and pick Create a Task. Map data from the payment bundle (the item the trigger hands over) into the task, so whoever opens it knows which payment it is about.

  4. 04

    Test with Run once

    Click Run once, then record a test payment in easybill. Read the bundles each module received and open easybill to check that the new task is there.

  5. 05

    Switch it on

    Turn the scenario on. A scheduled trigger would wait for the clock (every 15 minutes by default), but this one is instant: Make runs the scenario each time easybill calls the webhook.

Triggers

The easybill triggers: what starts a scenario

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

easybill1Watch Contacts

Watch Contacts

Instant trigger

In MakeTriggers when a contact event has happened.

Watch Contacts starts your scenario whenever easybill reports an event on a contact, so the change reaches Make without anyone retyping it. Each event arrives as one bundle that the next module can read.

How it fires
instant. easybill calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for.
When to use it
your team edits contact people inside easybill and a mailing list or shared sheet should carry the same details.
Watch out
the official description only says "a contact event", so run the scenario once and read the bundle before you add filters.
easybill2Watch Customers

Watch Customers

Instant trigger

In MakeTriggers when a customer event has happened.

Watch Customers wakes your scenario up the moment a customer event happens in easybill, which makes it the natural entry point for anything that mirrors your client list elsewhere.

How it fires
instant. easybill notifies Make through a webhook right away; you create that webhook with the Create a webhook button before the connection.
When to use it
a new or edited customer in easybill should appear in your CRM or support tool without a manual export.
Watch out
if the scenario also writes customers back into easybill with Update a Customer, that update can fire this trigger again. Keep the two directions in separate, filtered scenarios.
easybill3Watch Document Payments

Watch Document Payments

Instant trigger

In MakeTriggers when a document payment event has happened.

Watch Document Payments tells you the instant money is booked against a document in easybill. It hands Make one bundle per payment event, ready to feed a task, a message or an accounting sheet.

How it fires
instant. easybill sends the event to Make through a webhook as soon as it is recorded.
When to use it
an agency starts the project once the deposit lands, or a shop releases an order when the invoice is paid.
Watch out
the description speaks of a "payment event", not only a new payment. Test with Run once and check what a deleted payment sends before you act on every bundle.
easybill4Watch Documents

Watch Documents

Instant trigger

In MakeTriggers when a document event has happened.

Watch Documents reacts to events on your easybill documents and passes each one to Make as a bundle, so a document that changes can set off the rest of your process on its own.

How it fires
instant. easybill calls Make through a webhook as soon as the document event happens, with no schedule involved.
When to use it
you want a copy of every document logged in a spreadsheet, or a manager alerted when one changes.
Watch out
a scenario that answers this trigger with Update a Document or Send a Document may produce a new document event and run itself again. Add a filter after the trigger.
easybill5Watch Invoice Items

Watch Invoice Items

Instant trigger

In MakeTriggers when an invoice item event has happened.

Watch Invoice Items goes one level below the document: it fires on events about the individual lines of an invoice, and each line reaches Make as its own bundle.

How it fires
instant. easybill warns Make through a webhook the moment an invoice item event occurs.
When to use it
you track which products or services get billed, line by line, in a reporting sheet or a stock tool.
Watch out
an invoice with many lines produces many bundles, and every module after the trigger spends one operation per bundle. Filter early if you only care about some lines.
Modules

Every easybill module, and when to reach for it

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

easybill1

Cancel a Document

Action

In MakeCancels a specific document.

Cancel a Document voids an existing easybill document from inside your scenario, so a cancellation decided elsewhere shows up in your books too.

When to use it
a customer withdraws an order in your shop or CRM and the matching document should be cancelled without anyone logging in.
Watch out
point it at the right document, ideally one returned by Get a Document or List Documents earlier in the flow.
easybill2

Complete a Document

Action

In MakeCompletes a specific document.

Complete a Document moves a draft to its completed state in easybill, the step you would otherwise click through by hand once the content is final.

When to use it
your scenario builds a document with Create a Document and Create an Invoice Item, and the last step should close it off before Send a Document.
Watch out
run it only after every line is in place; test the whole chain with Run once on a dummy customer first.
easybill3

Create a Customer

Action

In MakeCreates a new customer.

Create a Customer adds a brand new customer record to easybill using data mapped from an earlier module, such as a signed quote form or a CRM deal.

When to use it
a lead becomes a client in another tool and you want easybill ready before the first document is due.
Watch out
its description mentions no duplicate check, so put Search Customers in front of it and continue only when the search comes back empty.
easybill4

Create a Customer Group

Action

In MakeCreates a new customer group.

Create a Customer Group sets up a new group in easybill, giving you a container to sort customers by segment, region or contract type.

When to use it
a new segment appears in your CRM and easybill should get a matching group without a trip to the settings.
Watch out
groups rarely change, so check with List Customer Groups first; otherwise every run adds another group with the same name.
easybill5

Create a Document

Action

In MakeCreates a new document.

Create a Document opens a new document in easybill from data your scenario already has, which saves you from rebuilding the same header by hand each time.

When to use it
an order in your online shop or a won deal should produce the matching easybill document straight away.
Watch out
if Watch Documents runs in another active scenario, this new document will fire it; make sure that scenario expects documents created by Make.
easybill6

Create a Document Payment

Action

In MakeCreates a new document payment.

Create a Document Payment books a payment against a document in easybill, so what your payment provider already knows lands on the invoice too.

When to use it
a payment tool or bank export reports money received and easybill should show the document as paid without manual matching.
Watch out
Watch Document Payments will fire on the payment you create. Keep the scenario that records payments separate from the one that reacts to them.
easybill7

Create an Invoice Item

Action

In MakeCreates a new invoice item.

Create an Invoice Item adds one line to an easybill invoice, the building block for documents whose content comes from a cart or a timesheet.

When to use it
after Create a Document, you loop over the products of an order and add each one as its own line.
Watch out
each line is one operation, the unit Make counts on your plan. A basket of many products costs as many operations as it has lines.
easybill8

Create a Project

Action

In MakeCreates a new project.

Create a Project opens a project in easybill so that tasks and documents for one engagement can live together from day one.

When to use it
a consultancy signs a new assignment in its CRM and wants the easybill project ready before the kickoff call.
Watch out
map a name you will recognise later, since List Projects and Get a Project rely on it when other scenarios look the project up.
easybill9

Create a Task

Action

In MakeCreates a new task.

Create a Task drops a to-do into easybill, filled with whatever your scenario knows at that point: a customer, an amount, a document.

When to use it
after Watch Document Payments, so a paid invoice immediately becomes a clear next step for someone on the team.
Watch out
a trigger that fires several times for one event creates several tasks. Check a few bundles with Run once before you switch the scenario on.
easybill10

Delete a Customer

Action

In MakeDeletes a specific customer.

Delete a Customer removes a customer from easybill for good, which is handy when your source of truth has already dropped them.

When to use it
an erasure request processed in your CRM must also clear the easybill record.
Watch out
there is no undo in Make. Run Get a Customer first, add a filter that confirms it is the right record, and test on a dummy customer.
easybill11

Delete a Customer Group

Action

In MakeDeletes a specific customer group.

Delete a Customer Group clears out a group you no longer use, keeping the easybill group list as tidy as the segments in your other tools.

When to use it
a segment is retired in your CRM and its twin group in easybill should disappear too.
Watch out
deleting cannot be reversed from Make. Look at which customers still belong to the group with Search Customers before you let the scenario remove it.
easybill12

Delete a Document

Action

In MakeDeletes a specific document.

Delete a Document removes a document from easybill. Cancel a Document is the other way out, when the document should be voided rather than removed.

When to use it
cleaning up test drafts that a scenario created while you were building it.
Watch out
the deletion is final. For a real document sent to a customer, Cancel a Document is usually the safer choice; keep Delete for drafts you are sure about.
easybill13

Delete a Document Payment

Action

In MakeDeletes a specific document payment.

Delete a Document Payment removes a payment booked on a document, undoing a record that should never have been there.

When to use it
your payment provider reports a refund or a failed charge and the payment recorded in easybill must go.
Watch out
Make cannot restore it afterwards, and Watch Document Payments may fire on the deletion. Use Get a Document Payment first to confirm you hold the right one.
easybill14

Delete an Invoice Item

Action

In MakeDeletes a specific invoice item.

Delete an Invoice Item takes one line off an invoice while leaving the rest of the document untouched.

When to use it
a product is removed from an order after the document was drafted, and only that line should go.
Watch out
the line is gone for good. List Invoice Items helps you find the exact line before the scenario removes it, especially when two lines look alike.
easybill15

Delete a Project

Action

In MakeDeletes a specific project.

Delete a Project removes an easybill project once the engagement it tracked has no reason to exist in your records anymore.

When to use it
a deal marked lost in your CRM had already created a project in easybill that nobody will use.
Watch out
Make offers no way back after the deletion. Check with Get a Project that the scenario is holding the right one before this module runs.
easybill16

Delete a Task

Action

In MakeDeletes a specific task.

Delete a Task clears a to-do from easybill when the work it described is no longer needed.

When to use it
a scenario created a follow-up task on payment, and a later refund means the follow-up should vanish as well.
Watch out
there is no undo, so find the task with List Tasks or Get a Task first and filter on something that identifies it without doubt.
easybill17

Get a Customer

Action

In MakeRetrieves a specific customer.

Get a Customer fetches the full record of one customer, giving later modules everything easybill knows about that person or company.

When to use it
the bundle you hold has less than you need, and the next step, an email or a CRM update, needs the complete details.
Watch out
it returns one customer you already identified. To find someone by name, reach for Search Customers instead.
easybill18

Get a Customer Group

Action

In MakeRetrieves a customer group.

Get a Customer Group reads the details of one group, so your scenario can make decisions based on the segment a customer sits in.

When to use it
after Get a Customer, you want the group's details to route the customer to the right salesperson or mailing list.
Watch out
it reads a single group you already know. List Customer Groups is the one that shows you every group available.
easybill19

Get a Document

Action

In MakeRetrieves a specific document.

Get a Document pulls one easybill document into the scenario with all its content, ready to be copied, checked or sent elsewhere.

When to use it
Watch Document Payments tells you money arrived, and you need the document itself to know what was bought.
Watch out
one run reads one document. To handle a batch, List Documents returns several bundles that the following modules process one by one.
easybill20

Get a Document Payment

Action

In MakeRetrieves a specific document payment.

Get a Document Payment reads a single payment recorded on a document, so you can check it before anything else happens.

When to use it
before Delete a Document Payment, to make sure the payment you are about to remove is the one your provider refunded.
Watch out
this module needs a payment already identified; to look through many payments, use Search Document Payments.
easybill21

Get an Invoice Item

Action

In MakeRetrieves a specific invoice item.

Get an Invoice Item reads one line of an invoice on its own, handy when a single line matters more than the whole document.

When to use it
Watch Invoice Items fired and you want the full details of that line before logging it in a report.
Watch out
it covers one line only. List Invoice Items gives you all of them when you need the complete picture.
easybill22

Get a Project

Action

In MakeRetrieves a specific project.

Get a Project reads one easybill project, letting later steps use its details without anyone looking them up.

When to use it
a task or document belongs to a project and your status report in a sheet needs the project's details next to it.
Watch out
it only works on a project you can already point to; if you only know part of the name, start with List Projects.
easybill23

Get a Task

Action

In MakeRetrieves a specific task.

Get a Task reads a single to-do from easybill, giving your scenario its current state before it decides what to do next.

When to use it
before Update a Task or Delete a Task, to confirm the task still matches what the scenario expects.
Watch out
it reads one task at a time. For a list of open work, List Tasks is the better starting point.
easybill24

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets your scenario reach any endpoint of the easybill API with the connection you already set up, covering what the dedicated modules leave out.

When to use it
you need an easybill feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the easybill API documentation open. If you would rather not, a Make agency can build that step for you.
easybill25

Send a Document

Action

In MakeSends a document of a specific type.

Send a Document delivers an easybill document to its recipient, which closes the loop on a document your scenario just prepared.

When to use it
the last step of a flow that creates, fills and completes a document, so the customer receives it without a manual click.
Watch out
the module sends a document of a specific type, so check the type you pick. Test with Run once on your own address before real customers are in the flow.
easybill26

Update a Customer

Action

In MakeUpdates a specific customer.

Update a Customer changes an existing customer in easybill, so a new address or contact detail entered elsewhere reaches your billing too.

When to use it
your CRM is where people edit client details, and easybill should follow it.
Watch out
if Watch Customers feeds another active scenario, the update fires it. A two-way sync without filters can bounce the same change back and forth.
easybill27

Update a Customer Group

Action

In MakeUpdates a specific customer group.

Update a Customer Group edits an existing group, keeping its details in line with the segment it mirrors in your other tools.

When to use it
a segment gets renamed in your CRM and the matching easybill group should carry the new name.
Watch out
find the group with List Customer Groups first, or the wrong group ends up with the new details.
easybill28

Update a Document

Action

In MakeUpdates a specific document.

Update a Document edits a document already in easybill, useful when the data behind it changes after creation.

When to use it
a draft built by your scenario needs a corrected detail pulled from the order it came from.
Watch out
the change may fire Watch Documents. If that trigger drives this same scenario, add a filter or you will update the document over and over.
easybill29

Update an Invoice Item

Action

In MakeUpdates a specific invoice item.

Update an Invoice Item corrects one line of an invoice without touching the others, so a price or quantity fix stays surgical.

When to use it
the source order changes one product after the draft exists and only that line needs editing.
Watch out
identify the line precisely with List Invoice Items or Get an Invoice Item, since several lines can look alike.
easybill30

Update a Project

Action

In MakeUpdates a specific project.

Update a Project refreshes an easybill project so its details follow what happens in the tool where your team actually manages the work.

When to use it
a project changes status in your project board and easybill should reflect it for billing.
Watch out
map only the values you mean to change, and confirm the target with Get a Project during your first Run once tests.
easybill31

Update a Task

Action

In MakeUpdates a specific task.

Update a Task changes a to-do that already exists in easybill, so progress made elsewhere shows up where your billing team looks.

When to use it
a follow-up task created on payment should be updated when your support tool marks the case as handled.
Watch out
check the task with Get a Task before editing, especially if several tasks were created for the same customer.
easybill32

List Contacts

Search

In MakeRetrieves a list of contacts.

List Contacts brings back the contacts easybill holds, each as a separate bundle, so you can copy or check them in bulk.

When to use it
filling a spreadsheet or mailing tool with every contact person once, before Watch Contacts keeps it current.
Watch out
a search returns zero, one or many bundles, and each bundle costs an operation in every module that follows it.
easybill33

List Customer Groups

Search

In MakeRetrives a list of customer groups.

List Customer Groups returns every group defined in easybill, a quick way to see your segments from inside a scenario.

When to use it
before Create a Customer Group, to check that the group does not already exist.
Watch out
if the list comes back empty, the next modules simply do not run, so plan for that case when you test with Run once.
easybill34

List Documents

Search

In MakeRetrieves a list of documents.

List Documents returns a set of easybill documents as separate bundles, so the rest of the scenario can handle them one after another.

When to use it
exporting a batch of documents into a spreadsheet or archive, or finding the one you need before Get a Document.
Watch out
every returned document runs through the following modules, and each pass costs operations. Narrow the list before connecting heavy steps.
easybill35

List Invoice Items

Search

In MakeRetrieves a list of invoice items.

List Invoice Items returns invoice lines as individual bundles, giving you line-level data without opening each document.

When to use it
building a sales report by product, or locating one line before Update an Invoice Item or Delete an Invoice Item.
Watch out
invoices with many lines multiply bundles fast; plan for the operations each one will use downstream.
easybill36

List Projects

Search

In MakeRetrieves a list of projects.

List Projects gives you the easybill projects as a series of bundles, a starting point for overviews and lookups.

When to use it
matching a project from your planning tool to its easybill twin before Update a Project runs.
Watch out
with no project returned, the rest of the route stops quietly; test with Run once and read what the module actually sent.
easybill37

List Tasks

Search

In MakeRetrieves a list of tasks.

List Tasks pulls the to-dos stored in easybill, one bundle per task, so you can review or move them in a single run.

When to use it
sending your team a digest of open follow-ups in a chat tool, or finding a task before Delete a Task.
Watch out
each task returned costs an operation in every later module, so filter out finished ones as early as you can.
easybill38

Search Customers

Search

In MakeSearches for a list of customers.

Search Customers looks through your easybill customers and returns the matches, so a scenario can tell whether someone already exists.

When to use it
right before Create a Customer, to avoid a duplicate when the same person buys twice.
Watch out
a search can return several customers; if you only want one, add a filter before the next module.
easybill39

Search Document Payments

Search

In MakeSearches for a list of documents.

Search Document Payments finds payments recorded in easybill and returns each match as a bundle, useful for reconciliation work.

When to use it
comparing what your payment provider settled with what easybill has booked, before you create or delete a payment.
Watch out
the official description of this module mentions documents rather than payments; run it once and read the bundles to see exactly what comes back.
Need help

Need help automating easybill with Make?

A person reads every message.

FAQ

easybill and Make: common questions

01Is the easybill Make integration free?
Yes, on the Make side. easybill is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow 40 minutes per run. Each module execution counts as an operation, the unit Make tracks on your plan. You still need an active easybill account, which Make does not provide.
02What do you need to connect easybill to Make?
An active easybill account and its API key. In easybill, click your username in the top blue bar, open Profile and Settings, scroll to the API Key section, click Generate new key if none exists, then Save in the top right corner and copy the key. In Make, add any easybill module, click Create a connection, optionally name it, and paste the key. For an instant trigger, click Create a webhook first. One connection serves every easybill module you add afterwards.
03Do easybill triggers in Make fire in real time?
Yes. All 5 easybill triggers are instant: Watch Contacts, Watch Customers, Watch Document Payments, Watch Documents and Watch Invoice Items. easybill calls Make through a webhook as soon as the event happens, so the 15-minute default schedule of a new scenario does not apply to them. When you add one, Make asks you to create the webhook before the connection. A scenario that starts with an action or a search instead, such as List Documents, runs on the schedule you set on its first module.
04What if an easybill module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the easybill API with the connection you already created, so you are not limited to the 44 listed modules. You write the request yourself, which means reading the easybill API documentation. Also keep in mind that the Make documentation page for easybill is AI-generated and asks readers to verify important information. If a module behaves differently from what the page says, easybill's own screens and support are the reference.
05Should you use Make or n8n for easybill?
It depends on your setup. In Make, easybill comes with 44 modules, including 5 instant triggers and Make an API Call for anything uncovered, and it runs on the Free plan. easybill may also have an n8n node, so compare what each side offers for the exact actions you need. If your team already runs one of the two tools for other apps, staying there keeps your automations in one place. Neither is ranked above the other here; the comparison page linked above lists the criteria.