Resources · Make integration

Bullet Make integrationAutomate Bullet with Make.

What if new clients and their invoices appeared in Bullet without anyone typing them? The Bullet Make integration gives you 21 modules: 16 actions and 5 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Bullet integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bullet Make integration do for you?

The Bullet Make integration lets a Make scenario, the automation you build in Make, read and write your Bullet clients, invoices, bills and client payments. Each step is a module, one brick of the scenario, and all of them reuse the same link to your Bullet account.

Onboard a client in one pass. When a deal closes in your CRM or a form comes in, Create a Client adds the record and Create an Invoice drafts the first invoice right behind it, with the customer data mapped from the earlier module.

Keep payments in step. Record money received with Create a Client Payment, then check open items with List Invoices before anyone chases a customer who already paid.

Feed a report. List Bills and List Employees return every item, each as one bundle (one item passed to the next module), which you can send to a spreadsheet or a team channel.

Bullet has no trigger in Make, so a scenario starts from another app or from Make's schedule. Make's own documentation for Bullet is limited, so test each module with a real record first. The Make troubleshooting guide helps when a run fails. Building the same flow in n8n? The n8n vs Make comparison lays out the differences, and the Make training covers the editor from zero.

Connect

How do you connect Bullet to Make?

  1. 01

    Add a Bullet module

    In your scenario, click the +, search for Bullet and pick any of its modules, for example List Clients. Then click Create a connection. The connection is your Bullet account linked to Make once and reused everywhere.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the company it belongs to. Then either approve Make on the Bullet page that opens, or paste the key Bullet gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Make now lists what it can read from your Bullet account in the module fields. If those lists stay empty, reconnecting is the first thing to try.

First scenario

Your first scenario with Bullet and Make

GoalWhen a new customer shows up in another app, Make creates the client in Bullet and drafts their first invoice.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since Bullet has no trigger, start with the module of the app where new customers first appear, such as your form tool or CRM.

  2. 02

    Add Create a Client

    Click the + on the right of that first module, search for Bullet and choose Create a Client. Pick your connection, then map the customer details coming from the previous module.

  3. 03

    Chain Create an Invoice

    Add Create an Invoice after it. Map the client that the previous module just created, so the invoice lands on the right record instead of an older one.

  4. 04

    Test with Run once

    Click Run once and create one test customer in the source app. Open each module's bubble to read the bundles it received and check the new client and invoice in Bullet.

  5. 05

    Schedule and switch on

    On the first module, set the Scheduling: every 15 minutes by default. Then switch the scenario on. From now on, each new customer becomes a Bullet client with its first invoice.

Modules

What each Bullet module does in Make

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

Bullet1

Create a Bill

ActionIn the docs only

Adds a new bill to Bullet from data your scenario already holds, so supplier costs stop living in someone's inbox.

When to use it
right after a supplier invoice is approved in another tool, to record it in Bullet without retyping.
Watch out
without a check first, a scenario that runs twice creates the bill twice; List Bills can confirm it is not already there.
Bullet2

Create a Client

ActionIn the docs only

Opens a fresh client record in Bullet, which gives every later invoice and payment a customer to attach to.

When to use it
when a deal is marked won or an intake form arrives, as the first Bullet step of the flow.
Watch out
the same person signing up twice becomes two clients; search with List Clients beforehand and add a filter so only unknown customers pass.
Bullet3

Create a Client Payment

ActionIn the docs only

Records money a client has paid, so the balance in Bullet matches what actually reached the bank.

When to use it
when a payment tool confirms a charge, map the payment details to log it straight away.
Watch out
the payment has to point at an existing client, so find that client first with Get a Client or List Clients in the same scenario.
Bullet4

Create an Invoice

ActionIn the docs only

Drafts an invoice in Bullet for one client, with the details mapped from earlier modules, so billing starts the moment the work is agreed.

When to use it
after Create a Client in an onboarding flow, or when a project is marked delivered elsewhere.
Watch out
run it once on a test client and open the result in Bullet before letting it bill real customers.
Bullet5

Delete a Bill

ActionIn the docs only

Removes one bill from Bullet, handy for clearing an entry that should never have been recorded.

When to use it
when a supplier invoice is rejected upstream and the matching Bullet bill has to go with it.
Watch out
treat the removal as final; put Get a Bill or a filter in front so the scenario deletes only the bill you meant.
Bullet6

Delete a Client

ActionIn the docs only

Takes a client out of your Bullet records, which keeps the list tidy after a merge or a cancelled signup.

When to use it
when a contact is erased in your CRM and Bullet should follow the same rule.
Watch out
a mapping error here can remove the wrong customer; test with Run once on a dummy client and add a filter on a value you trust.
Bullet7

Delete a Client Payment

ActionIn the docs only

Erases a payment entry in Bullet, so a refund or a duplicate no longer inflates what the client appears to have paid.

When to use it
when your payment provider reports a charge as reversed and the Bullet record must match.
Watch out
confirm the entry with Get a Client Payment before the delete runs, since the scenario acts on whatever payment it receives.
Bullet8

Delete an Invoice

ActionIn the docs only

Clears one invoice from Bullet, useful when one was created by mistake or an order was cancelled before billing.

When to use it
when an order is voided in your shop or project tool and the invoice is no longer wanted.
Watch out
a scenario does not ask for confirmation; check the invoice with Get an Invoice and a filter before this step.
Bullet9

Get a Bill

ActionIn the docs only

Fetches the full details of one bill you already know, so later modules can read its data without searching.

When to use it
when a previous module hands you a specific bill and you need its contents, for example to post them to your team channel.
Watch out
it returns a single bill; to browse several, List Bills is the better choice.
Bullet10

Get a Client

ActionIn the docs only

Pulls up one Bullet client with all its stored information, which lets you reuse that data further down the scenario.

When to use it
before sending a personalized email or creating a payment, when you already know which client is concerned.
Watch out
if you only have a name or an email, find the client with List Clients first, then pass it along.
Bullet11

Get a Client Payment

ActionIn the docs only

Reads one payment record in detail, so you can confirm what was paid before acting on it.

When to use it
ahead of a receipt email or an update in your accounting sheet, when the payment is already identified.
Watch out
it looks up one payment only; to see every payment for a period or a client, use List Client Payments.
Bullet12

Get an Invoice

ActionIn the docs only

Retrieves a single invoice with its details, giving the rest of the scenario something solid to work with.

When to use it
when an invoice has been sent and you want to copy its details into a CRM deal or a shared folder.
Watch out
pair it with a filter before any Update or Delete step, so the scenario checks the invoice before changing it.
Bullet13

List Bills

SearchIn the docs only

Returns the bills recorded in Bullet, one bundle per bill, so you can review or export them in one pass.

When to use it
to build a cost overview in a spreadsheet, or to check a bill does not exist before creating it.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which counts as extra operations on your plan.
Bullet14

List Client Payments

SearchIn the docs only

Gathers the payments recorded for your clients, each one as its own bundle, ready to be summed or sent somewhere else.

When to use it
to reconcile Bullet with your bank export, or to spot clients whose payments are missing.
Watch out
add an aggregator after it if you want one message with all payments instead of one message per payment.
Bullet15

List Clients

SearchIn the docs only

Walks through your Bullet clients and hands each one to the next module, which makes it the natural lookup step of many flows.

When to use it
to check whether a customer already exists before Create a Client, or to sync your client list to a CRM.
Watch out
when nothing matches, it returns no bundle and the next modules simply do not run; plan for that case.
Bullet16

List Employees

SearchIn the docs only

Brings back the employees stored in Bullet, so your scenario knows who is on the team without a separate list to maintain.

When to use it
to alert the right person about a new invoice, or to keep a staff sheet aligned with Bullet.
Watch out
it is a search, so each employee becomes a separate bundle and each later module runs once per person.
Bullet17

List Invoices

SearchIn the docs only

Collects your Bullet invoices one bundle at a time, which is the starting point for follow-ups and reports.

When to use it
in a scheduled scenario that looks at open invoices and flags them to the team before a customer is chased.
Watch out
the more invoices it returns, the more operations the next modules use; filter early to keep only the ones you need.
Bullet18

Make an API Call

ActionIn the docs only

Calls any endpoint of the Bullet API with the connection you already set up, covering what the other Bullet modules leave out.

When to use it
when you need a Bullet feature no listed module offers, and you have the API reference at hand.
Watch out
this one expects you to know the endpoint and its parameters; start with a read-only request and check the answer in the bundle.
Bullet19

Update a Bill

ActionIn the docs only

Changes an existing bill in Bullet, so corrections made in another tool reach your records without manual edits.

When to use it
when a supplier sends a corrected invoice and the Bullet bill has to reflect it.
Watch out
map only the values you mean to change, and identify the bill with Get a Bill or List Bills first.
Bullet20

Update a Client

ActionIn the docs only

Edits a client record in place, which keeps Bullet aligned when a customer changes address or contact person.

When to use it
when a contact is edited in your CRM and the change should follow to Bullet.
Watch out
the scenario needs the right client first; locate it with List Clients so the update does not land on a namesake.
Bullet21

Update an Invoice

ActionIn the docs only

Modifies an invoice that already exists, so a revised order shows up in Bullet on its own.

When to use it
when an order changes after the invoice was created, to bring the invoice in line.
Watch out
run it once on a test invoice and compare the result in Bullet before letting it touch invoices already sent.
Need help

Need help automating Bullet with Make?

A person reads every message.

FAQ

Questions about the Bullet Make integration

01Is the Bullet Make integration free?
Yes, Bullet is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. An operation is one module running on one bundle. Bullet's own subscription is a separate matter this page does not cover.
02What do you need to connect Bullet to Make?
A Bullet account and a Make account. Make's documentation lists no specific prerequisite for Bullet, so the generic steps apply: add any Bullet module, click Create a connection, optionally name it, then authorize Make on the Bullet page or paste the key Bullet provides, and click Save. The connection is stored once and reused by every Bullet module. Make also notes that its Bullet documentation is limited, so check the first runs carefully.
03Does the Bullet Make integration react in real time?
No, because Bullet has no trigger module in Make, neither scheduled nor instant. A scenario therefore starts elsewhere: on the trigger of another app, such as a new form entry or a won deal, or on Make's own schedule, which runs the scenario every 15 minutes by default. In the second case, a search such as List Invoices can open the scenario and pass each result on. Whether it feels immediate depends on the app that starts the flow.
04What if a Bullet module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Bullet API with the connection you already have, so whatever the listed modules do not cover can still be done from the same scenario. You will need the Bullet API reference to know which endpoint to call. Make states its Bullet documentation is limited, so test the call with Run once and read the returned bundle before relying on it in production.
05Should you use Make or n8n for Bullet?
It depends on where your other automations already live. On Make, Bullet comes with 21 modules covering clients, invoices, bills, payments and employees, plus Make an API Call for the rest, and it works from the Free plan. The same app often has a node in n8n too, so check what that node covers before deciding. Keeping all your flows on one platform usually matters more than the tool itself, since connections and habits carry over.
Same platform

Other docs you might need on this stack.

Browse all integrations