B33 Make integrationAutomate B33 with Make.
Can Make keep your B33 customers, invoices and payments in step with the rest of your tools? The B33 Make integration gives you 17 modules: 13 actions and 4 searches. This page shows how to link your account, build a first scenario and pick the right module.
Verified Trustpilot reviews · AI, automation & growth agency
What can the B33 Make integration do for you?
The B33 Make integration lets a Make scenario, the automation you build as a chain of modules, create, read, change and delete records in B33: customers, invoices, invoice lines and payments. Each module is one brick of that chain, so you assemble the steps visually and never write code.
A customer file that fills itself. When a new client signs up in another tool, Create Customer adds them to B33, and Update Customer keeps their details current when something changes upstream. No more typing the same name twice.
Invoices built from real data. Create Invoice opens the document, then Create Invoice Line adds each item that came in from your order or project tool. The invoice ends up complete, line by line, without copy and paste.
Payments that land where they belong. Create payment records money received against the right invoice, and List Payments lets a later step check what has already been paid before anything else happens.
Know the limits before you start. B33 has no trigger in Make, so a scenario starts on a schedule or on another app, and the official documentation is limited because little public information exists about B33. If you want a second pair of eyes, our Make agency can review your build, and the Make training covers the editor from zero. Curious about the alternative? The n8n vs Make comparison lays out the criteria.
How do you connect your B33 account to Make?
- 01
Add a B33 module
In your scenario, click the +, search for B33 and pick any module, for example Create Customer. Then click Create a connection: this is your B33 account linked to Make once, and every B33 module reuses it.
- 02
Name it and authorize Make
Give the connection a name you will recognize later, which helps when you run several accounts. Then either authorize Make on the B33 page that opens, or paste the key B33 gives you, depending on what the window asks for.
- 03
Save and check
Click Save. Once the connection exists, Make can read your B33 data and offer lists in the module fields, so you pick values instead of typing them. If nothing shows up, the connection is the first thing to recheck.
Build your first scenario with B33
GoalWhen a new client arrives from another app, Make creates the customer in B33 and opens an invoice for them.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the +. B33 has no trigger, so the first module comes from the app where your new clients appear, such as a form or a CRM.
- 02
Add Create Customer
Click the + on the right of that first module, search for B33 and choose Create Customer. Pick your connection, or click Create a connection if this is your first B33 module.
- 03
Map the client data
Fill the customer fields by mapping values from the first module: click a field, then pick the matching item from the data the previous step received. Make lists what it can read once the connection works.
- 04
Add Create Invoice
Add a third module with the +, choose B33 Create Invoice, and map the customer that Create Customer just returned. Each bundle, one item passing from module to module, carries that customer forward.
- 05
Test with Run once
Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received, then check in B33 that the customer and the invoice really exist.
- 06
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, or let the other app start it. Then switch the scenario on. Every module that runs on a bundle counts as one operation on your plan.
Every B33 module in Make, explained
B33 gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Customer
ActionIn the docs onlyAdds a new customer to B33 from data another app already holds, so the client exists before any invoice is written.
Create Invoice
ActionIn the docs onlyOpens a new invoice in B33 for a customer, which gives the rest of the scenario a document to attach lines and payments to.
Create Invoice Line
ActionIn the docs onlyAdds one item to an existing B33 invoice, so an invoice can grow line by line from the products or hours recorded elsewhere.
Create payment
ActionIn the docs onlyRecords a payment in B33, which keeps your books aligned with the money that actually came in through your payment tool.
Delete Customer
ActionIn the docs onlyRemoves a customer from B33, which keeps the client list clean when an account is closed in the tool you treat as the reference.
Delete Invoice
ActionIn the docs onlyErases an invoice in B33, useful to clear drafts that a scenario created by mistake or that were cancelled at the source.
Delete Invoice Line
ActionIn the docs onlyTakes one line off a B33 invoice while the rest of the document stays as it is, so a single wrong item can be fixed on its own.
Delete Payment
ActionIn the docs onlyRemoves a payment record from B33, which lets a scenario correct the books when a charge is refunded or was logged by mistake.
Get Customer
ActionIn the docs onlyFetches one specific customer from B33, handing the next modules that customer's full record to work with.
List Customers
SearchIn the docs onlySearches your B33 customers and returns every match as a separate bundle, which is how a scenario checks whether a client already exists.
List Invoice Lines
SearchIn the docs onlyReturns the lines of your B33 invoices, one bundle each, so a scenario can read what was actually billed item by item.
List Invoices
SearchIn the docs onlyPulls a set of invoices out of B33, each one as its own bundle, which is the starting point for any follow-up on billing.
List Payments
SearchIn the docs onlyRetrieves the payments stored in B33 as separate bundles, giving you a clear view of what has already been collected.
Update Customer
ActionIn the docs onlyChanges the record of a customer who already exists in B33, so a correction made in your CRM also reaches your invoices.
Update Invoice
ActionIn the docs onlyEdits an invoice that already exists in B33 instead of creating a new one, so corrections stay on the same document.
Update Invoice Line
ActionIn the docs onlyCorrects a single line on a B33 invoice, without touching the other items.
Update Payment
ActionIn the docs onlyAdjusts a payment already recorded in B33, which keeps the record right when the payment tool later corrects what it first reported.
Need help automating B33 with Make?
A person reads every message.
