Resources · Make integration

InvoiceBerry Make integrationAutomate InvoiceBerry with Make.

Tired of retyping the same client details into InvoiceBerry? The InvoiceBerry Make integration gives you 6 modules: 4 actions and 2 searches. This page is for freelancers and small finance teams, and it walks you through the connection and a first scenario that creates invoices for you.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the InvoiceBerry Make integration do for InvoiceBerry?

The InvoiceBerry Make integration links your InvoiceBerry account to Make, a visual tool where you chain apps together without code. Inside Make you build a scenario (the automation itself, made of modules, one brick per step) that can add clients, create invoices and read back what already exists in InvoiceBerry.

Invoices that start where the sale happens. When a deal closes in your CRM or a form comes in, a scenario can add the buyer with Create a Client and then draft the bill with Create an Invoice. Nobody copies an address by hand anymore.

A clean client list in your other tools. List Clients hands every client to Make as a bundle (one item passed from module to module), so you can copy them into a spreadsheet or a mailing tool and keep both sides aligned.

A payment follow-up view. List Invoices and Return an invoice let a scenario read your invoices and push them to a shared sheet or a team chat, so the person chasing payments sees the same thing as the person who billed.

Know the limits before you start. InvoiceBerry has no trigger in Make, so InvoiceBerry itself never starts a scenario: another app or Make's clock does. There is no Make an API Call module either, and Make says its own documentation for this app is limited. If you want to see how Make handles this kind of setup in general, read the Make review, and if you hesitate between tools, the n8n vs Make comparison lays out the differences. Stuck on a run that fails? Make troubleshooting covers the usual errors.

Connect

How do you connect InvoiceBerry to Make?

  1. 01

    Add an InvoiceBerry module

    In your scenario, click the + and search for InvoiceBerry. Pick any of its modules, for example Create a Client, then click Create a connection. A connection is your InvoiceBerry account linked to Make once, then reused by all six modules.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear label such as the company or the account owner helps later, when several people or several InvoiceBerry accounts share the same Make organization.

  3. 03

    Authorize and save

    Follow what Make shows next: either sign in to InvoiceBerry and allow access, or paste the key InvoiceBerry gives you. Then click Save. Make now reads your account and can fill the module fields for you.

First scenario

Build your first scenario with InvoiceBerry

GoalWhen a new customer shows up in another app, Make adds them to InvoiceBerry and prepares their invoice.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the screen. That first module is the one that starts everything, so pick the app where your new customers appear.

  2. 02

    Add Create a Client

    Click the + on the right of that first module, search for InvoiceBerry and choose Create a Client. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the customer data

    Fill the fields of Create a Client by clicking into each one and picking values from the first module, like the name or email it received. Make shows the available data in a panel.

  4. 04

    Chain Create an Invoice

    Add Create an Invoice after it with the + and map the client that the previous module just created, so the invoice lands on the right person instead of a random one.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows, above each module, the bundles it received. Open InvoiceBerry to check the new client and the new invoice.

  6. 06

    Schedule and switch on

    On the first module, set the schedule (a new scenario runs every 15 minutes by default), then flip the scenario on. From then on, each new customer gets a client record and an invoice.

Modules

What each InvoiceBerry module does

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

InvoiceBerry1

Create a Client

Action

In Make“Creates a client for a specific user.”

Adds a new client to your InvoiceBerry account from data that another app sends to Make, so the contact exists before you ever bill it.

When to use it
right after a quote is accepted or a signup form is submitted, when the buyer is new to you.
Watch out
the module creates a record every time it runs, so check with List Clients first if the same buyer can come back twice.
InvoiceBerry2

Create an Invoice

Action

In Make“Creates an invoice for a specific user.”

Produces an invoice in InvoiceBerry without opening the app, which is the step most people want to automate first.

When to use it
at the end of a scenario, once the client exists, to bill an order, a finished project or a booking recorded somewhere else.
Watch out
test it with Run once and open the result in InvoiceBerry before switching the scenario on, since a wrong mapping creates real invoices.
InvoiceBerry3

Get a Client

Action

In Make“Returns client details for a specific user.”

Fetches the details of one client you already know about, so later modules can reuse them without you looking them up.

When to use it
you have a single client in mind and need their details to fill an email, a document or a record in another tool.
Watch out
it targets one client only; to scan all your clients, pick List Clients instead.
InvoiceBerry4

Return an invoice

Action

In Make“Returns an invoice for a specific user.”

Reads one existing invoice and hands its content to the rest of the scenario, which saves you from exporting it by hand.

When to use it
a teammate asks about a specific invoice, and you want its data pushed to a chat message or a follow-up sheet.
Watch out
Make's documentation for this app is limited, so check the output of a Run once test to see exactly which details come back.
InvoiceBerry5

List Clients

Search

In Make“Lists all clients for a specific user.”

Gives you your whole InvoiceBerry client list inside Make, one bundle per client, ready to be copied or compared elsewhere.

When to use it
you want to sync clients into a spreadsheet or a CRM, or check whether a buyer already exists before creating them.
Watch out
the next modules run once per client returned. Each of those runs is an operation, the unit Make counts on your plan.
InvoiceBerry6

List Invoices

Search

In Make“Lists all invoices for a specific user.”

Pulls every invoice from your account into the scenario so you can report on them or share them without logging into InvoiceBerry.

When to use it
you need a shared view of billing, for instance a sheet where the team tracks which invoices are still unpaid.
Watch out
a search can return zero, one or many bundles, so add a filter after it if only some invoices matter.
Need help

Need help automating InvoiceBerry with Make?

A person reads every message.

FAQ

InvoiceBerry and Make: common questions

01Is the InvoiceBerry Make integration free?
Yes, it works on the Make Free plan. InvoiceBerry is a standard app in Make, not an Enterprise one, so all six modules are open on every plan. The Free plan has limits though: 2 active scenarios, at least 15 minutes between two scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your InvoiceBerry subscription is a separate matter.
02What do you need to connect InvoiceBerry to Make?
An InvoiceBerry account and a Make account are enough to start, as Make's documentation lists no extra prerequisite. Add any InvoiceBerry module, click Create a connection, give it a name if you like, then either authorize Make on the InvoiceBerry page or paste the key InvoiceBerry provides, depending on what Make asks. Click Save and the connection is reused by all six modules. Make notes that its documentation for this app is limited, so test the connection with a single module and Run once first.
03Can InvoiceBerry trigger a Make scenario in real time?
No, InvoiceBerry has no trigger module in Make, scheduled or instant. The scenario has to start somewhere else. You have two options. Start from another app that has a trigger, such as the tool where orders or signups land, and add the InvoiceBerry modules after it. Or put a schedule on the first module so Make runs the scenario on its own clock, every 15 minutes by default on a new scenario, then use List Invoices or List Clients to read the current state of your account.
04What if an InvoiceBerry module you need is missing in Make?
It depends on what you need. The InvoiceBerry app in Make has six modules and no Make an API Call module, so you cannot reach other parts of InvoiceBerry from the same app. Make also warns that its documentation for InvoiceBerry is incomplete. When a step is missing, look for another app in your process that can take over that part, or combine the existing modules differently. If the gap blocks a real project, the Hack'celeration team can look at the scenario with you and suggest a workaround.
05Should you use Make or n8n for InvoiceBerry?
It depends on the tool your team already uses. Make gives you six ready InvoiceBerry modules on every plan, including Free, and you build the scenario visually with a connection set up once. An app like InvoiceBerry often has an n8n node too, so check that side if your team works in n8n already. The honest criterion is simple: pick the tool where your other apps and your team already live, then confirm the modules you need exist there before building.