Resources · Make integration

Billsby Make integrationAutomate Billsby with Make.

Can Make react when a Billsby subscription, invoice or customer changes? Yes. The Billsby Make integration offers 22 modules, 9 of them triggers. This guide is for teams running subscriptions who want to connect their account and ship a first working scenario.

Try the Billsby integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Billsby Make integration let you automate?

The Billsby Make integration links your Billsby account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. Each module is one brick of that chain. With Billsby, those bricks watch customers, invoices, credit notes and subscriptions, then read or change them.

Know about new revenue without opening Billsby. Watch Subscriptions picks up each new subscription, and Get a Customer adds the person behind it, so the next module (a chat message, a spreadsheet row) has a name to show.

Keep finance in the loop. Watch Invoices and Watch Credit Notes hand every new document to the rest of your stack, while their Updated twins catch the edits that follow.

Act on customer records from other tools. Search Customers finds the right account, then Update a Customer, Add a Feature Tag or Cancel a Subscription does the change, so a request logged elsewhere lands in Billsby without copy and paste.

What the listed modules do not cover goes through Make an API Call, which reuses the same connection. The documentation behind this integration is marked by Make as AI-generated, so check important details against Billsby itself. If you are still weighing the tool, the Make review and the Make pricing page help, and n8n vs Make sets the two side by side.

Connect

How do you connect Billsby to Make?

  1. 01

    Copy your Billsby API key

    In Billsby, open Settings, then Configuration, then API keys and webhooks. The key is shown on screen: copy it. You need an active Billsby account to reach this screen.

  2. 02

    Add a Billsby module in Make

    In your scenario, search for Billsby, pick any module and click Create a connection. A connection is your Billsby account linked to Make once, then reused by every Billsby module you add later.

  3. 03

    Paste the key and save

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the API key where Make asks for it, or follow the instructions on screen, then save.

First scenario

Your first scenario: a new subscription with its customer

GoalWhen a new subscription appears in Billsby, Make fetches the matching customer so the next module can use the customer's details.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add its first module. An empty canvas is normal at this stage.

  2. 02

    Place the trigger

    Search for Billsby and pick Watch Subscriptions. Select the connection made earlier, or click Create a connection if this is your first Billsby module.

  3. 03

    Add Get a Customer

    Click the + on the right of the trigger and choose Get a Customer. Map the customer reference from the trigger's output; Make shows what it can read once the trigger has run.

  4. 04

    Test with Run once

    Click Run once. Each bubble then shows the bundles it received, a bundle being one item passed along, here one subscription and one customer. Fix the mapping if a field comes back empty.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Keep that or pick your own interval, then switch the scenario on.

Triggers

Which Billsby events can start a scenario?

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

Billsby1Watch Credit Notes

Watch Credit Notes

triggerIn the docs only

Brings each new credit note into your scenario, so a refund or correction issued in Billsby reaches your accounting side without anyone forwarding it.

How it fires
scheduled, Make checks Billsby on the scenario's schedule, which is every 15 minutes by default. Make's documentation lists no instant version of this module.
When to use it
your bookkeeper wants every credit note logged in a shared sheet the moment Make spots it.
Watch out
this module only sees new credit notes; a change to an existing one belongs to Watch Updated Credit Notes.
Billsby2Watch Customers

Watch Customers

triggerIn the docs only

Starts your scenario with every customer newly created in Billsby, which makes it the natural entry point for onboarding flows and welcome sequences outside the billing tool.

How it fires
scheduled, Make polls Billsby on the scenario's schedule rather than hearing from it directly.
When to use it
a new sign-up should appear in your CRM or your support desk without manual entry.
Watch out
an edited customer is not new, so this trigger ignores it; pair it with Watch Updated Customers if you need both.
Billsby3Watch Deleted Customers

Watch Deleted Customers

triggerIn the docs only

Tells your scenario when a customer has been removed from Billsby, so the other tools that hold a copy of that person can be cleaned up too.

How it fires
scheduled, the check runs whenever the scenario's schedule comes round, not at the instant of deletion.
When to use it
a deleted account should also leave your mailing list or your internal customer sheet.
Watch out
the customer is already gone in Billsby, so a Get a Customer placed after this trigger has nothing left to read.
Billsby4Watch Invoices

Watch Invoices

triggerIn the docs only

Hands every new Billsby invoice to the rest of the scenario, the simplest way to get billing data flowing into reporting or a team channel.

How it fires
scheduled, Make queries Billsby at the interval set on the first module, 15 minutes unless you change it.
When to use it
finance wants a line per invoice in a spreadsheet, or sales wants a ping when a large one is issued.
Watch out
each invoice counts as one bundle, and every module after it spends an operation on it, which is what Make counts on your plan.
Billsby5Watch Subscriptions

Watch Subscriptions

triggerIn the docs only

Fires your scenario for each subscription created in Billsby, giving you a clean signal that a customer has just started paying.

How it fires
scheduled, Make asks Billsby for new subscriptions each time the scenario's schedule runs.
When to use it
a new plan purchase should trigger access in another tool, a welcome email or a message to the account manager.
Watch out
plan changes and cancellations on existing subscriptions are updates, which Watch Updated Subscriptions handles instead.
Billsby6Watch Updated Credit Notes

Watch Updated Credit Notes

triggerIn the docs only

Catches credit notes that change after creation, so the copy held in your accounting sheet or ledger tool stays in step with Billsby.

How it fires
scheduled, Make looks for changes on the scenario's schedule, so an edit shows up at the next check.
When to use it
credit notes get corrected after the fact and your records must follow.
Watch out
if you run it next to Watch Credit Notes in separate scenarios, decide which one writes to the sheet so the same document is not logged twice.
Billsby7Watch Updated Customers

Watch Updated Customers

triggerIn the docs only

Picks up customer records that have been edited in Billsby, which keeps every other copy of that customer accurate without a manual sync.

How it fires
scheduled, Make reads Billsby for recent changes at each scheduled run of the scenario.
When to use it
a customer updates an email or company name and your CRM should reflect it.
Watch out
if a scenario started by this trigger ends with Update a Customer on the same record, the edit it makes can wake the trigger again; write the change to another tool instead.
Billsby8Watch Updated Invoices

Watch Updated Invoices

triggerIn the docs only

Reports invoices that change after they are issued, useful when the status or content of a bill matters more than its creation.

How it fires
scheduled, the scenario's clock decides when Make asks Billsby what has changed.
When to use it
your dashboard or collections sheet tracks invoices through their life, not just the day they appear.
Watch out
the documentation behind this app does not say which changes count as an update, so run it once on a real invoice and read the bundle before building on it.
Billsby9Watch Updated Subscriptions

Watch Updated Subscriptions

triggerIn the docs only

Follows existing subscriptions as they change, giving you one entry point for upgrades, downgrades and other edits made in Billsby.

How it fires
scheduled, Make polls Billsby on the scenario's schedule, never the second something happens.
When to use it
customer success wants a heads-up when an account moves between plans.
Watch out
this trigger does not tell you by itself what kind of change occurred; check the bundle after Run once and filter on what you actually need.
Modules

What can the Billsby modules do in a scenario?

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

Billsby1

Add a Feature Tag

ActionIn the docs only

Puts a feature tag on a record in Billsby from your scenario, so an entitlement decided somewhere else is written where billing can see it.

When to use it
a sales rep grants an add-on in your CRM and Billsby should carry the matching tag.
Watch out
Make's documentation does not detail what a tag unlocks, so try it on a test customer first.
Billsby2

Cancel a Subscription

ActionIn the docs only

Ends a Billsby subscription directly from a scenario, which spares your team the trip into the dashboard when the decision is already made elsewhere.

When to use it
a cancellation request arrives through a form or a support ticket and should be applied as soon as it is approved.
Watch out
a cancellation is hard to walk back, so place a filter or an approval step before this module.
Billsby3

Create a One-Time Charge

ActionIn the docs only

Adds a single charge to a customer in Billsby, for anything billed once rather than on the recurring plan, such as a setup fee or an extra service.

When to use it
an order or a signed quote in another tool should turn into a charge without retyping the amount.
Watch out
a scenario that runs twice on the same item charges twice, so test with Run once on sample data.
Billsby4

Delete a Customer

ActionIn the docs only

Removes a customer from Billsby at the end of a scenario, the tidy finish to an off-boarding or data-removal request handled elsewhere.

When to use it
a verified deletion request comes in through your privacy form or your helpdesk.
Watch out
a deleted record cannot be brought back by Make, so check you have the right customer with Get a Customer first.
Billsby5

Delete a Feature Tag

ActionIn the docs only

Takes a feature tag off a Billsby record, the counterpart of Add a Feature Tag when an entitlement should no longer apply.

When to use it
a trial add-on ends or a promotion is withdrawn and billing must stop reflecting it.
Watch out
removing a tag that someone added by hand also erases their choice, so limit the scenario to tags your automation owns.
Billsby6

Get a Customer

ActionIn the docs only

Reads one Billsby customer in full, so the following modules can work with that customer's record, even when the scenario started from an invoice or a subscription.

When to use it
after an invoice or subscription trigger, when your message or sheet needs the customer's name and contact details.
Watch out
it needs to know which customer to read, so map the reference from an earlier module.
Billsby7

Get a Shipping Address

ActionIn the docs only

Fetches where a customer's physical goods should go, straight from Billsby, so your fulfillment tool gets the address without anyone copying it.

When to use it
a new subscription includes a box or a printed welcome pack that someone has to ship.
Watch out
the documentation does not say what comes back when no address is stored, so run it once on such a customer before going live.
Billsby8

Get a Subscription

ActionIn the docs only

Loads a single Billsby subscription with its current state, handy when a scenario starts from another app and needs the billing side of the story.

When to use it
a support ticket mentions an account and the agent should see the plan in the ticket itself.
Watch out
this reads one subscription you point to; to find one by criteria, Search Subscriptions is the better fit.
Billsby9

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Billsby API from your scenario, with the connection you already set up, for whatever the other modules leave out.

When to use it
you need a Billsby object or action that has no dedicated module on this page.
Watch out
you write the request yourself, so keep the Billsby API reference open while you build it.
Billsby10

Search Customers

SearchIn the docs only

Looks up Billsby customers and returns those that match, the starting point when all you have is information from another tool.

When to use it
a form or a ticket gives you an email and you need the matching Billsby account before updating it.
Watch out
a search can return zero, one or several bundles, and every module after it runs once per result.
Billsby11

Search Subscriptions

SearchIn the docs only

Finds the Billsby subscriptions that fit your criteria and sends each one down the scenario, so a batch job covers them all in a single run.

When to use it
you want every subscription in a given state pushed to a report or a review list.
Watch out
an empty result stops the modules that follow, which is normal and not an error.
Billsby12

Update a Counter

ActionIn the docs only

Changes the value of a counter in Billsby from a scenario, the way to feed usage recorded in another system back to billing.

When to use it
your product logs usage elsewhere and Billsby should hold the figure it bills on.
Watch out
Make's documentation does not say whether the value is added or replaced, so check the result in Billsby after Run once.
Billsby13

Update a Customer

ActionIn the docs only

Writes changes to an existing Billsby customer, so details corrected in your CRM or support desk also reach the billing record.

When to use it
a customer changes company name or contact email in another tool and invoices should follow.
Watch out
identify the customer first with Search Customers, or you risk editing the wrong account.
Need help

Need help automating Billsby with Make?

A person reads every message.

FAQ

Billsby and Make: common questions

01Is the Billsby Make integration free?
Yes, Billsby is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes 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 count usage in operations per month. You still need your own active Billsby account, whose pricing is set by Billsby, not by Make.
02What do you need to connect Billsby to Make?
An active Billsby account and its API key. In Billsby, the key sits under Settings, then Configuration, then API keys and webhooks, and you copy it from that screen. In Make, add any Billsby module, click Create a connection, optionally give it a name, then paste the key you copied. That single connection serves all 22 Billsby modules in every scenario you build, so the setup happens once per account.
03Do Billsby triggers in Make fire in real time?
No. Make's documentation lists 9 Billsby triggers, all Watch modules, and marks none as instant, so they work as scheduled triggers: Make checks Billsby on the scenario's schedule instead of being called the moment something changes. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Plan your flows around that small delay rather than expecting an immediate reaction from Make.
04What if a Billsby module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Billsby API from the scenario and reuses the connection you already created, so there is no second setup. It asks more of you, since you write the request by hand with Billsby's API reference open. Also keep in mind that Make flags the documentation for this app as AI-generated, so confirm important behavior with Billsby directly before relying on it.
05Make or n8n for Billsby?
It depends on what your team already uses. On Make, Billsby comes with 22 ready modules, including 9 scheduled triggers and a generic API call for the rest. The same app often has an n8n node too, so check what n8n offers for Billsby before choosing. Compare the modules each tool gives you for the events you care about, and pick the editor your team finds easiest to maintain. The comparison page linked above sets out the broader criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations