Resources · Zapier integration

Chargebee Zapier integrationAutomate Chargebee with Zapier.

The Chargebee Zapier integration gives you 17 triggers, 9 actions and 4 searches. Every trigger is instant, so a failed payment or a cancelled subscription reaches the rest of your tools without waiting, even on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Chargebee Zapier integration actually does

It links Chargebee, the subscription billing tool, to the other apps you run through Zapier. Chargebee reports billing events (a new customer, a payment, a cancellation) and Zapier reacts by writing, updating or looking things up, in Chargebee or elsewhere, with no copy-paste in between.

Three results come up again and again. First, a dunning alert: Payment Failure fires the moment a charge bounces, and your account manager can reach out while the renewal is still fresh. Second, a cleaner churn log: Subscription Cancellation Scheduled and Subscription Cancellation let you record the intent and the actual exit as two separate moments, which is the window where a retention call still has a chance. Third, billing that follows the sales side: when a deal closes in another app, Create Customer then Create Subscription set up the account in Chargebee without a second pair of hands.

Now the limits. The integration has no action that deletes anything, no action that issues a refund, and no find-or-create shortcut on its searches. The triggers cover customers, cards, payment methods, invoices and subscriptions, and nothing else. When an action is missing, API Request (Beta) is the escape hatch, and it assumes you can read Chargebee's API documentation.

If you are weighing tools, the same app has a Chargebee n8n integration page and a Chargebee Make integration page, written with the same method.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Each one is explained here once, then used as is.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a Chargebee billing event.
Action
What the Zap does once it has started: the step that writes, sends or updates something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is counted in tasks.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier the moment the event happens. Chargebee only has instant triggers.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists, so the steps after it can use what it found.
Connection
Your Chargebee account linked to Zapier once, then reused by every step that touches Chargebee.
Cost

What a Chargebee Zap costs you

Listening costs nothing. A Chargebee event that starts your Zap is free; only the actions that follow are billed.

  • Trigger0 tasks
  • Action that works1 task each
  • Action that fails0 tasks
  • Free plan100 tasks a month, two steps per Zap
  • Filter or searchmulti-step Zap, paid plan

Every action that goes through counts as one task, and each one counts on its own: a three-action Zap eats three times more than a one-action Zap. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. Add a filter, a search or a second action and it becomes a multi-step Zap, which needs a paid plan. Chargebee is not a premium app, so it works from the free plan. The interval grid below only applies to polling triggers, and Chargebee has none.

Connect

Connect Chargebee to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. You need a Chargebee account first, plus access to the customers and subscriptions you want the Zap to touch.

  2. 02

    Pick Chargebee

    Type Chargebee in the search box of the dialog, select it, then click Add connection. A new tab opens on the Chargebee side, where the actual sign-in happens.

  3. 03

    Sign in and grant access

    Sign in to Chargebee in that tab and allow Zapier to use the account. The connection then appears in your list, and every Chargebee step of every Zap can reuse it.

First Zap

Your first Chargebee Zap

GoalGive every new Chargebee customer a subscription, but only for customers whose record carries an email.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Chargebee as the app and New Customer as the event. Then select the Chargebee connection you just created.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent customers of your account, so you map the next steps on a real record rather than a guess.

  3. 03

    Add a filter

    Click the plus icon, choose Filter, then set the field (Email), the rule and the value. Mind the rule type: a text rule only works on text. This step makes the Zap multi-step, so a paid plan.

  4. 04

    Add the action

    Add Chargebee again with Create Subscription, then map the customer from the trigger into the fields. On Catalog 2.0 this action needs that existing customer.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the subscription shows up in Chargebee as expected, click Publish to switch the Zap on.

Triggers

Chargebee triggers on Zapier

17 events start a Zap when something happens in Chargebee, and 17 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Card Deleted

Instant trigger

In Zapier“Triggers when a card is deleted.”

Removing a card from a customer account becomes a signal you can act on. The Zap starts with the customer's details in hand, so the next step knows who just lost a stored card.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer deletes the only card on file and your team wants to ask for a new one before the next renewal, rather than discovering it on a declined charge.
Watch out
a deleted card is not always a problem; customers swap cards all the time, so pair this with a check before you send a worried message.
2

Card Expiration

Instant trigger

In Zapier“Triggers when a credit card expires.”

This one starts the Zap when a stored credit card reaches its expiry. Instead of waiting for the renewal to bounce, you get the event as soon as Chargebee records it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want a polite reminder to go out to the customer, or a note to land with the account owner, so the card gets replaced before money is actually at stake.
Watch out
the card is already expired by the time the Zap runs, so this is a recovery flow, not an early warning.
3

Customer Details Updates

Instant trigger

In Zapier“Triggers when customer details such as first name, last name, email, billing address, etc., are updated.”

Any edit to a customer record in Chargebee (first name, last name, email, billing address and the like) kicks off the Zap with the updated values.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your CRM or support desk keeps its own copy of the customer and drifts out of sync every time someone corrects an email or an address in Chargebee.
Watch out
if a later step writes those details back into Chargebee with Update Customer, the Zap can set itself off again in a loop.
4

New Customer

Instant trigger

In Zapier“Triggers when a customer is created.”

Each customer created in Chargebee starts the Zap with the new record. It is the entry point of most onboarding flows.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a fresh account should appear in your CRM, a welcome sequence should start, or the customer needs a subscription set up right after creation.
Watch out
customers created before you publish the Zap are never picked up, so import the backlog separately.
5

New Invoice

Instant trigger

In Zapier“Triggers when a new invoice is generated(with line item support).”

When Chargebee generates an invoice, the Zap receives it with its line items. That gives your accounting or reporting tools each charge in detail, not just a total.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
finance wants every new invoice copied into a ledger or a spreadsheet the moment it exists, without exporting from Chargebee at month end.
Watch out
a generated invoice is not a paid invoice; pair it with New Payment if the next step is about collected money.
6

Payment Failure

Instant trigger

In Zapier“Triggers when a payment fails.”

A charge that does not go through fires this trigger. For a subscription business it is the signal worth acting on first.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the account manager or the customer success team should know about a declined payment right away and reach out with a human message.
Watch out
if your team already contacts customers about failed charges another way, make sure the Zap does not send a second message.
7

New Payment Method

Instant trigger

In Zapier“Triggers when a payment method is added.”

Adding a payment method to a customer account in Chargebee starts the Zap. Often it is the good news that follows a failed payment or an expired card.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want to close the loop on a recovery flow: tell the team the customer has a valid method again, and stop chasing them.
Watch out
a payment method being added does not mean the overdue invoice is paid; that is a separate event.
8

Payment Method Updates

Instant trigger

In Zapier“Triggers when a payment method is updated.”

An existing payment method changing in Chargebee starts the Zap. It sits next to New Payment Method but covers edits rather than additions.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your support tool shows billing status and should reflect the new details as soon as a customer updates their card or bank details.
Watch out
adding a card and editing one are two separate triggers; a Zap built on this one ignores new methods.
9

New Payment

Instant trigger

In Zapier“Triggers when a payment is collected successfully.”

A payment collected successfully starts the Zap. That is the moment money actually lands, which makes it the right trigger for anything tied to cash rather than invoices.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sales wants a message for each payment received, or a revenue sheet should get a new line every time a customer pays.
Watch out
on a busy account this trigger fires a lot, and each action that follows counts as a task.
10

Subscription Activation

Instant trigger

In Zapier“Triggers when a subscription is changed from Trial to Active state.”

A subscription moving from Trial to Active fires this trigger. It is the trial conversion, the moment a test user becomes a paying customer.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want to hand the account from the trial nurturing flow to customer success, or update the lifecycle stage in your CRM.
Watch out
subscriptions that start active without a trial never pass through this state change, so New Subscription covers them instead.
11

Subscription Cancellation Scheduled

Instant trigger

In Zapier“Triggers when a subscription is scheduled for cancellation.”

Here the Zap starts when a subscription is set to cancel later, not when it actually ends. The subscription has not ended yet, which leaves room to talk.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your retention team wants a heads-up while there is still time to offer a different plan or simply ask why.
Watch out
the actual cancellation fires a separate trigger later; do not count both as churn.
12

Subscription Cancellation

Instant trigger

In Zapier“Triggers when a subscription is cancelled.”

The subscription is now cancelled, and the Zap starts with the record. This is the real exit, the one to log in a churn report.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want to revoke access in another tool, update the customer stage in your CRM, or send a short exit survey.
Watch out
if the customer comes back, Subscription Reactivation fires; plan how your other tools undo what this Zap did.
13

Subscription Details Updates

Instant trigger

In Zapier“Triggers when subscription details such as custom fields, billing information, recurring items etc., are modified.”

Edits on a subscription (custom fields, billing information, recurring items and so on) start the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you track plan changes in a CRM or a revenue sheet and want them recorded as they happen, not reconstructed later.
Watch out
Update Subscription and Change Next Billing Date both write to the same place; a Zap that uses them after this trigger can loop.
14

New Subscription

Instant trigger

In Zapier“Triggers when a subscription is created.”

Every subscription created in Chargebee starts the Zap. It is the broadest view of new business on the billing side.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want a new line in your sales dashboard or a provisioning step in another tool each time a customer subscribes.
Watch out
if your Zap creates subscriptions with Create Subscription, it will fire this trigger too, so check for loops.
15

Subscription Pause

Instant trigger

In Zapier“Triggers when a subscription is paused.”

A subscription being paused starts the Zap. The customer has not left, but billing stops for a while.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want to suspend access somewhere else, or schedule a check-in with the customer before the pause ends.
Watch out
a pause triggered by your own Pause Subscription action fires this too.
16

Subscription Reactivation

Instant trigger

In Zapier“Triggers when a subscription is moved from Cancelled state to Active/In Trial/Non Renewing/Future state.”

A cancelled subscription that returns to Active, In Trial, Non Renewing or Future fires this trigger. That is a win-back, and worth knowing about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a returning customer should get their access back elsewhere and the CRM should stop treating them as churned.
Watch out
it is not the same event as resuming a paused subscription; that one has its own trigger.
17

Subscription Resumption

Instant trigger

In Zapier“Triggers when a paused subscription is resumed.”

When a paused subscription resumes, the Zap starts. Billing is running again and the customer is back in normal service.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you suspended access during the pause and want it switched back on in other tools without anyone remembering to do it.
Watch out
if you also listen to Subscription Reactivation, keep the two flows separate; they cover different exits from different states.
Actions

Chargebee actions on Zapier

Chargebee gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Change Next Billing Date

Action

In Zapier“Updates next billing date of a subscription.”

Moves the next billing date of a subscription. A narrow action, but it saves a trip into Chargebee for a frequent request.

When to use it
support grants a customer extra days and the renewal date should shift accordingly.
Watch out
the change hits the customer's next invoice, so test it on a test record first.
2

Create Customer

Action

In Zapier“Creates a new customer in Chargebee.”

Adds a new customer record to Chargebee from data another app holds, so billing starts from the same details sales already collected.

When to use it
a deal marked won in your CRM should exist in Chargebee too, without someone retyping the name and email.
3

Create Subscription

Action

In Zapier“Creates a new subscription. If you are on Catalog 1.0 of Chargebee, this action allows you to create a subscription and a customer in a single step. If you are on Catalog 2.0 of Chargebee, this action allows you to create a subscription for an existing customer”

Opens a subscription in Chargebee. How it behaves depends on your Chargebee catalog: on Catalog 1.0 it can create the subscription and the customer in one step, on Catalog 2.0 it attaches to a customer that already exists.

When to use it
signing a customer up to a plan right after their account is created.
Watch out
check which catalog your site runs on before mapping fields; on 2.0 a missing customer stops the step.
4

Pause Subscription

Action

In Zapier“Pauses a subscription in Chargebee.”

Puts a subscription on hold in Chargebee from a Zap, so billing stops without cancelling the customer.

When to use it
a pause request arrives through a form or a support ticket and should take effect without a billing admin.
5

Record Offline Payment for an Invoice

Action

In Zapier“Records an offline payment for unpaid invoices.”

Marks money received outside Chargebee, a bank transfer or a cheque, against an unpaid invoice.

When to use it
your bank or accounting tool confirms a transfer and the matching Chargebee invoice should be settled.
Watch out
it applies to unpaid invoices; you need the right invoice, which Fetch Subscription Invoice Details can find.
6

Resume Subscription

Action

In Zapier“Resumes a paused subscription in Chargebee.”

Restarts a paused subscription in Chargebee. It is the natural counterpart of Pause Subscription.

When to use it
the customer confirms they are back, through a form or a reply, and billing should pick up again.
Watch out
it only works on a subscription that is actually paused.
7

Update Customer

Action

In Zapier“Updates customer details in Chargebee.”

Changes the details of a customer already in Chargebee with values coming from another step.

When to use it
the customer corrects their billing email in your support tool and Chargebee should follow.
Watch out
pair it with Customer Details Updates and the Zap can retrigger itself.
8

Update Subscription

Action

In Zapier“Updates a subscription in Chargebee.”

Edits an existing subscription in Chargebee, for instance after a plan change decided in another tool.

When to use it
account managers record upgrades in the CRM and you want billing to follow without a manual edit.
Watch out
you need the subscription to target; a search step upstream usually provides it.
9

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to Chargebee using the connection you already set up. It covers what the other actions do not, at the price of reading Chargebee's API documentation.

When to use it
you need a Chargebee operation that has no ready-made action, one that none of the eight actions above covers.
Watch out
HTTP Method, URL and Stop on error are required, and the URL must point to a Chargebee domain.
Searches

Chargebee searches on Zapier

4 search steps look for data that already exists in Chargebee, so a later step can use it.

The four searches sit at the bottom of the action list in the editor, under the SEARCH heading. Each one fetches an existing customer, subscription or invoice so the next step can use it. None of them offers a find-or-create variant, so the create box below never appears for Chargebee. Three settings decide what happens when the result is not a clean single match.

1

Finds an Existing Customer

Search

In Zapier“Lookup an existing customer.”

Looks up a customer already in Chargebee and hands their record to the next steps. It is the usual first move before Update Customer or Create Subscription.

When to use it
a later step needs the Chargebee customer record, for example before Fetch Customer Subscription Details.
Watch out
whether it wants an exact value or a close one is up to Chargebee, so test with a real record.
2

Find Existing Subscription

Search

In Zapier“Lookup details of an existing subscription.”

Fetches the details of one subscription when you already know its identifier. The Subscription Id field is required.

When to use it
a ticket or a CRM record stores the subscription ID and the Zap needs the current status or plan.
Watch out
without an ID upstream this search cannot run; it does not search by customer name.
3

Fetch Subscription Invoice Details

Search

In Zapier“Get the Invoice details for a specific Subscription ID”

Brings back the invoice details of a given subscription. It needs a Subscription Id, and a choice of which invoice to keep when there are several.

When to use it
before Record Offline Payment for an Invoice, to land on the right unpaid invoice.
Watch out
the multiple-invoices choice is required; pick it deliberately rather than taking whatever comes first.
4

Fetch Customer Subscription Details

Search

In Zapier“Get the subscription details for a specific customer ID”

Returns the subscription details of a customer from their Customer Id, with a required choice for customers who hold several subscriptions.

When to use it
you know the customer and want their subscription before Update Subscription or Pause Subscription.
Watch out
without a Customer Id upstream this search cannot run; Finds an Existing Customer or a customer trigger can provide it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on without the data.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create. Chargebee's searches do not offer it, so you will not see this box here.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When a Chargebee Zap breaks

Most failures are not bugs. They come from how Zapier listens and from what Chargebee expects in each field.

Zapier publishes one help article for this app, How to get started with Chargebee on Zapier. Beyond it, the cases below are the general Zapier limits that apply to a billing tool. For a broken Zap that resists, the Zapier troubleshooting page goes further.

  • Nothing from before the Zap

    A Zap only reacts to events after it is switched on. Customers, invoices and payments that already existed are never picked up; moving that history is a separate job.
  • A Zap that feeds itself

    Listen to Subscription Details Updates and write with Update Subscription, and each write sets the Zap off again, eating tasks until you stop it.
  • A bulk import that stalls

    Importing many customers at once can send Zapier a burst of events. Its flood protection may hold them back.
  • A search with no ID

    Three of the four searches need a Subscription Id or a Customer Id. If no earlier step provides it, the search fails or finds nothing.
Need help

Need help automating Chargebee with Zapier?

A person reads every message.

FAQ

Chargebee Zapier integration: common questions

01Is the Chargebee Zapier integration free?
Yes, it works on the free plan because Chargebee is not a premium app. The free plan gives 100 tasks a month and unlimited Zaps, but every Zap is capped at two steps, one trigger and one action. As soon as you add a filter, a search or a second action, the Zap becomes multi-step and needs a paid plan. That matters here, since many useful Chargebee flows start with a search for a customer or a subscription. Prices change often, so check the current plans on Zapier before you commit.
02How many tasks does a Chargebee Zap use?
One task per action that succeeds, nothing for the trigger. A Chargebee event arriving costs zero, whether it is a new payment or a cancellation. If your Zap then updates a customer and pauses a subscription, that is two tasks for that run. A failed action is not counted. The thing to watch is volume: New Payment and New Invoice fire on every single occurrence, so on a busy account a Zap built on them can use a large share of your monthly tasks quickly. A few apps and actions use more than one task when they complete.
03Are Chargebee triggers real time on Zapier?
Yes, all 17 Chargebee triggers are instant. Chargebee calls Zapier as soon as the event happens, so the Zap starts right away. That holds on every plan, including the free one, because the interval grid (15 minutes on Free, down to 1 minute on Team and Enterprise) only applies to polling triggers, and Chargebee has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. This is the main reason Chargebee works well on Zapier for alerts such as a failed payment.
04What does it take to connect Chargebee to Zapier?
A Chargebee account, plus access to the customers and subscriptions you want the Zap to touch. In Zapier you open the Apps page, click + Add connection, pick Chargebee, then sign in to Chargebee in the tab that opens and grant access. The connection is created once and every Chargebee step in every Zap can reuse it afterwards. If several people build Zaps, it is worth agreeing on which Chargebee account the connection uses, since every action will act with that account's rights.
05Why does Create Subscription fail on Catalog 2.0?
Because its behaviour depends on your Chargebee catalog. On Catalog 1.0, the action can create the subscription and the customer in a single step. On Catalog 2.0, it only creates a subscription for a customer who already exists in Chargebee. So on 2.0 the Zap needs that customer first, either from a New Customer trigger, a Create Customer action, or a Finds an Existing Customer search earlier in the Zap. Check which catalog your Chargebee site uses before mapping the fields, and test the step on a real customer record.
06What if the Chargebee action you need does not exist on Zapier?
Use API Request (Beta), the advanced action of the integration. It sends a raw request to Chargebee with the connection you already set up, so there is no extra authentication. It needs three things: an HTTP method, a URL that points to a Chargebee domain, and a choice on whether the step stops on error. The catch is that you have to read Chargebee's API documentation to know what to send. If that is too technical, the general Zapier help or a specialist can set it up once for you.
07Zapier, Make or n8n for Chargebee?
It depends on your criteria, not on a single winner. On Zapier, Chargebee comes with 17 instant triggers, 9 actions and 4 searches, a guided editor, and a free plan limited to two-step Zaps. The questions to ask of each tool are the same: does it offer the exact Chargebee events and actions your flow needs, how does it count usage at your volume, and who on your team will maintain the automation. List the flows you plan to build first, then check each tool against that list rather than against a general ranking.