Resources · Make integration

Billit Make integrationAutomate Billit with Make.

Can Billit orders, customers and products move on their own? The Billit Make integration offers 3 scheduled triggers, 10 actions and 3 searches. This guide is for finance and operations people: link your account, build a first scenario, then pick the right module.

Try the Billit integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Billit Make integration automate?

The Billit Make integration links your Billit account to Make, a tool where you build a scenario, meaning an automation made of modules that pass data along. Billit brings 16 modules to that chain: it can spot new orders, parties and products, create or update them, and look them up, all without writing code.

A clean customer file. When a lead signs up in another tool, Create a Party adds it to Billit, and List Parties checks first that the same company is not already there. Your contact list stops drifting away from what sales actually closed.

A shared view of new sales. Watch Orders spots each new order, invoices included, and hands it to the next module, which can post it to a sheet or a team chat. Nobody has to export a report to know what came in.

One catalog, not two. If your shop or stock tool is the reference for prices, Update a Product keeps the Billit catalog in line, and Watch Products tells other tools when someone adds an item directly in Billit.

The module list covers create, get, update and list, with no Delete module; for any other request, Make an API Call reaches the Billit API with the same connection. To see how Make compares with its closest alternative, read n8n vs Make, and check Make pricing before you scale. If you would rather have it built for you, the Make agency team can help.

Connect

How do you connect Billit to Make?

  1. 01

    Add a Billit module

    Open your scenario, add any Billit module, and click Create a connection. A connection is your Billit account linked to Make once, then reused by every Billit module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the company name helps when you manage more than one Billit account in the same Make organization.

  3. 03

    Sign in or paste your key

    Follow the on-screen instructions to authorize Make, or paste an API key. You find it in Billit under the Account section, where the key is displayed and ready to copy.

First scenario

Your first scenario with Billit

GoalWhen a sale is closed in the app your team sells with, Make turns it into a new order in Billit.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module on the canvas.

  2. 02

    Start from your sales app

    Pick the module of the app where sales are recorded, a shop or a CRM, so each new sale enters the scenario as one bundle, the item passed from module to module.

  3. 03

    Add Create an Order

    Click the + on the right, search for Billit, choose Create an Order and click Create a connection to link your account.

  4. 04

    Map the sale

    Fill the fields of Create an Order with data from the first module. Once the connection exists, Make lists what it can read in Billit to help you.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time; open each module to read the bundles it received and check the new order in Billit.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on so new sales keep reaching Billit by themselves.

Triggers

What starts a Billit scenario

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

Billit1Watch Orders

Watch Orders

Scheduled trigger

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

Watch Orders hands your scenario every new order created in Billit, invoices included, so the next modules can file, share or copy it without anyone retyping numbers.

How it fires
this is a scheduled trigger. Make checks Billit on the scenario's schedule, every 15 minutes by default, and the minimum interval is 15 minutes on the Free plan.
When to use it
when each new sale should reach your tracker or alert whoever prepares the delivery.
Watch out
each order comes out as one bundle, and every module after it spends one operation per bundle.
Billit2Watch Parties

Watch Parties

Scheduled trigger

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

Watch Parties starts your scenario with each new party created in Billit, meaning the record of a company you bill, so your CRM or mailing tool gets it without a manual export.

How it fires
scheduled. Make polls Billit following the scenario's schedule, shown by the clock badge on the module, rather than being called by Billit.
When to use it
when accountants add parties straight in Billit and the sales side needs the same list.
Watch out
every new party is one bundle, so when many parties are added at once, the next check sends them all through the scenario and each one costs operations.
Billit3Watch Products

Watch Products

Scheduled trigger

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

With Watch Products, an item added to the Billit catalog can be copied to your shop, a price sheet or a stock tool, and the catalogs stay aligned.

How it fires
on a schedule. Make asks Billit for new products at each run of the scenario, 15 minutes apart by default, with a shorter minimum interval on paid plans.
When to use it
when Billit is where your team creates items first and other tools follow.
Watch out
the trigger is described as reacting to new products; for a price change on an existing item, plan another route.
Modules

What each Billit module does

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

Billit1

Create an Order

Action

In Make“Creates a new order (e.g. invoices).”

This module writes a new order into Billit, such as an invoice, from data another module collected, so a deal marked as won turns into a billing document without copy and paste.

When to use it
right after a quote is accepted or a web shop checkout completes.
Watch out
run Get a Party or List Parties first so the order points to the right customer.
Billit2

Create a Party

Action

In Make“Creates a new party.”

Adding a party, the customer record Billit invoices, to Billit from another app is the job of Create a Party, which saves you from typing the same company details twice.

When to use it
when a signed form or a CRM deal introduces a new client you will soon invoice.
Watch out
nothing on this page says Billit blocks duplicates, so search with List Parties before creating.
Billit3

Create a Product

Action

In Make“Creates a new product.”

Your Billit catalog gains a new item each time Create a Product runs, fed by the tool where products are born, for example a shop back office.

When to use it
when a new item goes on sale elsewhere and should be ready to add to Billit orders.
Watch out
pair it with List Products to avoid adding the same item on every run.
Billit4

Get an Order

Action

In Make“Gets information about an order.”

Pulling the full details of one known order is what Get an Order does, handy when the trigger or another app only gave you its identifier.

When to use it
when a customer message mentions an order and the scenario needs its content before replying or updating it.
Watch out
it reads one order at a time; for several, List Orders is the better fit.
Billit5

Get a Party

Action

In Make“Gets information about a party.”

Get a Party returns the record of a single party, so later modules can reuse its details instead of asking for them again.

When to use it
before creating an order or sending a message, when you already hold the party identifier from an earlier module.
Watch out
without that identifier, start with List Parties to find the right record first.
Billit6

Get a Product

Action

In Make“Gets information about a product.”

One product, fully described: Get a Product fetches a single catalog item so its data can feed an order, a quote or a message elsewhere.

When to use it
when a scenario knows which item it needs, for instance from a line of a shop order.
Watch out
each call counts as one operation, so avoid fetching the same product again inside one run.
Billit7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the listed modules leave out can still be reached: Make an API Call sends a request of your choice to the Billit API, using the connection you already set up.

When to use it
when you need an endpoint without a dedicated module or an object the other modules do not handle; no Delete module exists, for example.
Watch out
you write the request yourself, so keep the Billit API documentation open beside the editor.
Billit8

Update an Order

Action

In Make“Updates information about an order.”

Changes made in another system can flow into an existing Billit order through Update an Order, which keeps the billing record matching what really happened.

When to use it
when a delivery, a payment or a correction is recorded outside Billit and the order must reflect it.
Watch out
map only the values you mean to change, and test with Run once before switching the scenario on.
Billit9

Update a Party

Action

In Make“Updates information about a party.”

When a client moves or changes its contact person, Update a Party edits the Billit record so the next invoice carries the right details.

When to use it
when your CRM is the place where customer data gets corrected and Billit should follow.
Watch out
find the party first with List Parties or Get a Party, since the update needs to target an existing record.
Billit10

Update a Product

Action

In Make“Updates information about a product.”

Update a Product brings an existing catalog item in Billit up to date, so orders built later reuse the data your reference tool holds.

When to use it
when your shop or stock tool owns product data and Billit copies it.
Watch out
it edits an item that already exists, so find it first with List Products or Get a Product.
Billit11

List Orders

Search

In Make“Retrieves a filtered list of orders.”

List Orders searches Billit and returns the orders that match your filter, each one as its own bundle, which suits reports and batch checks.

When to use it
when you need every open order for one customer before a follow-up call or a summary email.
Watch out
a search can return zero, one or many bundles, and each following module runs once per bundle.
Billit12

List Parties

Search

In Make“Retrieves a filtered list of parties.”

Finding a party from data you already hold is where List Parties helps, and it prevents duplicate records.

When to use it
as the check before Create a Party, then route the scenario depending on whether a match came back.
Watch out
when several parties match, later modules run for each, so narrow the filter or keep only the first.
Billit13

List Products

Search

In Make“Retrieves a filtered list of products.”

A filtered view of your Billit catalog comes out of List Products, one bundle per item, ready to compare with another tool or to export.

When to use it
when you align two catalogs or build a price list from what Billit already holds.
Watch out
a broad filter returns many bundles and uses operations fast; start narrow and test with Run once.
Need help

Need help automating Billit with Make?

A person reads every message.

FAQ

Billit and Make: common questions

01Is the Billit Make integration free?
Yes, Billit is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations, one per module and bundle. You also need your own active Billit account.
02What is needed to connect Billit to Make?
An active Billit account and a Make account are enough to start. When you add a Billit module, click Create a connection, give it a name if you like, then either follow the on-screen authorization or paste an API key. That key sits in the Account section of Billit, ready to copy. The Make documentation names OAuth or OpenID Connect as the main methods and reserves the API key for noncommercial integrations, so pick the method that matches your situation.
03Do Billit triggers in Make react in real time?
No. All three Billit triggers, Watch Orders, Watch Parties and Watch Products, are scheduled: Make checks Billit on the scenario's schedule rather than Billit calling Make. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. For most billing flows that delay is fine, but plan for it if another tool expects an update the moment an order appears.
04What if a Billit module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. The Billit app lists 16 modules for creating, reading, updating and searching orders, parties and products, and there is no Delete module. Make an API Call lets the scenario call any endpoint of the Billit API with the connection you already created, so a missing action does not force you to switch tools. Keep in mind that the Make documentation for Billit warns it may contain mistakes, so check important details with Billit.
05Should Billit be automated with Make or n8n?
It depends on your criteria rather than on a winner. In Make, Billit comes with 3 scheduled triggers, 10 actions and 3 searches, with Make an API Call among the actions for the gaps, and it runs on the Free plan, which lets you test a real flow before paying. Apps often have an n8n node as well, so check whether one exists for Billit and whether it covers the same objects. Then compare which tool your team already knows and which one fits the rest of your stack.
Same platform

Other docs you might need on this stack.

Browse all integrations