Resources · Make integration

Rebill Make integrationAutomate Rebill with Make.

Need your Rebill billing data inside other tools without copying it by hand? The Rebill Make integration gives you 8 modules that read customers, payments, prices, products and subscriptions. This page shows how to connect your account and build a first working scenario.

Try the Rebill integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Rebill Make integration do for you?

The Rebill Make integration links your Rebill account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Every Rebill module in Make reads data: a customer, an organization, a payment, a price, a product or a subscription, which you then pass to the next app in the chain.

Know who is writing to support. When a ticket or a form reaches another app, Get Customer by Email finds the matching Rebill customer, so the agent answering sees the billing side of the account instead of guessing.

Explain a charge. Starting from a payment ID, Get Payment by ID pulls the payment, then Get Price ID by Payment ID and Get Price by ID tell you which price it belongs to. Handy when finance asks what a line on a statement was for.

Enrich a subscription record. Get a Subscription By ID and Get Product By ID bring the subscription and the product behind it into a spreadsheet or a CRM, where the rest of the team already works.

What Make does not do here: Rebill has no trigger module, so nothing starts on its own when something changes in Rebill. The scenario begins with another app or with a schedule. Make also warns that its Rebill documentation is limited, so plan to test each module with real data. The same app often has an n8n node too; the n8n vs Make comparison lays out the differences, and the Make training covers scenario basics if this is your first one. When a module fails, Make troubleshooting is the next stop.

Connect

How do you connect Rebill to Make?

  1. 01

    Open a Rebill module

    Add any Rebill module to your scenario, for example Get Customer by Email, then click Create a connection. A connection is your Rebill account linked to Make once and reused by every Rebill module afterwards.

  2. 02

    Name the connection

    Give the connection a name if you like. It is optional, but a clear label such as the account or workspace it points to saves confusion when you manage more than one Rebill account.

  3. 03

    Authorize and save

    Authorize Make on the Rebill page that opens, or paste the key Rebill gives you, depending on what the connection window asks for. Then click Save and the module is ready to fill.

First scenario

Build your first Rebill scenario in Make

GoalWhen a new support request lands in your helpdesk, Make looks up the sender in Rebill and hands the billing details to the next step.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Rebill has no trigger, pick the app where requests arrive, such as your helpdesk or form tool.

  2. 02

    Add the Rebill lookup

    Click the + on the right of that first module, search for Rebill and choose Get Customer by Email. Create the connection if you have not already done so.

  3. 03

    Map the email address

    In the Rebill module, map the sender address coming from the first module. A bundle is one item passed from a module to the next, here a single request with its email.

  4. 04

    Test with Run once

    Click Run once and send a test request. Open the bubble above each module to read the bundles it received and check that Rebill returned the right customer.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Add a module after the lookup to post the customer data where your agents read it.

Modules

Every Rebill module, explained

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

Rebill1

Get Customer by Email

ActionIn the docs only

This lookup turns an email address into the Rebill customer behind it, which is usually the only identifier another app knows about a person.

When to use it
right after a form, an inbox or a helpdesk hands you an email and you want the billing profile that goes with it.
Watch out
the address has to match the one stored in Rebill, so test with a real customer before switching the scenario on.
Rebill2

Get Organization by ID

ActionIn the docs only

You get the details of one Rebill organization when you already hold its ID, useful once a scenario needs to know which account a record sits under.

When to use it
a previous module returned an organization ID and the next app needs readable organization information rather than a bare code.
Watch out
the module needs the ID itself; map it from an earlier bundle instead of typing it.
Rebill3

Get Payment by ID

ActionIn the docs only

Pulls a single Rebill payment from its ID, so the rest of the scenario can work with that payment instead of someone searching for it in the dashboard.

When to use it
a payment ID shows up in an email, a ticket or a spreadsheet row and you need the payment itself to record or explain it.
Watch out
each call reads one payment, and each run of the module counts as one operation on your Make plan.
Rebill4

Get Price ID by Payment ID

ActionIn the docs only

Answers a narrow question: which price a given payment was made against. It returns the price ID, the bridge between a charge and what was sold.

When to use it
chain it after Get Payment by ID when finance wants to know which offer a payment belongs to.
Watch out
it gives you the ID only, so add Get Price by ID after it if you need the price details.
Rebill5

Get Price by ID

ActionIn the docs only

Fetches the full Rebill price that matches an ID, giving the next module something a human can read instead of a reference string.

When to use it
as the second half of a pair with Get Price ID by Payment ID, or whenever another tool stores price IDs and a report needs the real price record.
Watch out
map the ID from the previous module; typing it by hand invites mistakes.
Rebill6

Get Product By ID

ActionIn the docs only

Brings back the Rebill product tied to an ID, so the name of what a customer bought can travel to a CRM, a sheet or a message.

When to use it
you hold a product ID from another module and a teammate needs to see which product it is without opening Rebill.
Watch out
Make documents this app only lightly, so run it once and read the returned bundle before relying on it.
Rebill7

Get a Subscription By ID

ActionIn the docs only

Reads one subscription from Rebill so you can check where a recurring customer stands without leaving the scenario you are building.

When to use it
a support or account manager workflow already carries the subscription ID and the next step depends on that subscription.
Watch out
it reads data only; nothing in the subscription changes. To edit one, look at Make an API Call, provided the Rebill API offers that change.
Rebill8

Make an API Call

ActionIn the docs only

Covers everything the seven listed modules leave out: it calls any endpoint of the Rebill API from your scenario, reusing the same connection.

When to use it
you need a Rebill action or a piece of data that no other module in this list offers.
Watch out
you write the request yourself, so check every request with Run once before switching the scenario on.
Need help

Need help automating Rebill with Make?

A person reads every message.

FAQ

Questions about Rebill and Make

01Is the Rebill Make integration free?
Yes, Rebill is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Every module execution counts as one operation, so a scenario that chains two Rebill lookups uses two operations each time it handles a request.
02What is needed to connect Rebill to Make?
A Rebill account and a Make account. The Make documentation lists no specific prerequisite for Rebill. You add a Rebill module, click Create a connection, optionally name it, then either authorize Make on the Rebill page or paste the key Rebill gives you, and click Save. That connection is then reused by all 8 Rebill modules, so you only set it up once per account. If you manage several Rebill accounts, create one connection for each and give each a clear name.
03Does the Rebill Make integration react in real time?
No, because Rebill has no trigger module in Make. Every one of its 8 modules is an action that reads data, so the scenario has to start somewhere else. Two options: start with a trigger from another app, such as a helpdesk or a form, or start on a schedule set on the first module, every 15 minutes by default. The Rebill modules then run as steps inside that scenario and fetch the data you need.
04What if a Rebill module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Rebill API with the connection you already created, which covers actions and data the seven other modules do not. Keep in mind that Make says its Rebill documentation is limited, because little public information about the app is available, so test each call with Run once and read the returned bundles before switching the scenario on.
05Should you use Make or n8n for Rebill?
It depends on the tool your team already runs. Make offers 8 Rebill modules, all of them actions, plus Make an API Call for the rest, and every scenario is built visually from these bricks. The same app often has an n8n node as well, so check what that node covers against the modules you need. Neither choice changes the fact that Rebill has no trigger in Make: scenarios start from another app or a schedule.
Same platform

Other docs you might need on this stack.

Browse all integrations