Resources · n8n integration

Chargebee n8n integrationAutomate Chargebee with n8n.

How much of your billing follow-up still happens by hand? The Chargebee n8n integration gives you a node with 5 operations across customers, invoices and subscriptions, plus a trigger that listens to 34 Chargebee events over a webhook. Built for ops and finance teams already running n8n.

Try the Chargebee integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What can the Chargebee n8n integration actually do?

Chargebee runs the recurring side of the business: customers, subscriptions, invoices, payments. n8n puts that billing activity on a canvas next to everything else you use. Two building blocks do the work. The Chargebee Trigger starts a workflow when something happens on your Chargebee site, and the Chargebee node runs 5 operations across 3 resources when a workflow needs to write or read something back.

Take dunning first. A failed charge fires payment_failed, and the workflow can post the account into a finance channel in Slack within seconds, then call the node to fetch the invoice PDF link so whoever picks it up already has the document in front of them. Nobody refreshes the Chargebee dashboard waiting for a card to bounce.

Reporting is the second pattern, and it runs on a schedule rather than on an event. The invoice.list operation returns invoices, a filter narrows them to the period you care about, and the rows land in Google Sheets for the monthly recap or go on to Xero for the accounting side. The same workflow can run every month without anyone opening an export screen.

Third, the lifecycle work around trials and signups. subscription_trial_ending lands 6 days before the trial period ends, which is enough runway to send a nudge, flag the account, or open a task for whoever owns it. On the other end, a signup captured outside Chargebee goes straight in through customer.create, with the email and company filled from the item that started the run.

Where the node stops, HTTP Request takes over. Anything outside those 5 catalog operations is a call you build yourself with the HTTP Request node, reusing the same Chargebee credential through its predefined authentication, so you are not juggling a second set of keys.

One practical note on scope: the trigger is the broad half of this integration and the node is the focused half. If your workflow mostly reacts, you will live in the trigger. If it mostly writes, you will chain the node with the tools around it. Our n8n review covers how that split plays out on bigger automations, and the n8n training walks through building one end to end.

Connect

How do you connect Chargebee to n8n?

  1. 01

    Generate an API key in Chargebee

    You need a Chargebee account first. Inside it, create an API key following Chargebee's own documentation on creating API keys. That key is the only supported authentication method for both the Chargebee node and the Chargebee Trigger, so one key covers everything you are about to build. Copy it somewhere safe before you leave the page.

  2. 02

    Create the credential in n8n

    Open the Credentials menu in n8n and add a Chargebee credential. It asks for two things. Account Name is your Chargebee site name, the subdomain only: if your site is https://n8n.chargebee.com, the Account Name is n8n. API Key is the key you just generated. Save it once and every Chargebee node in every workflow can pick it from the dropdown.

  3. 03

    Register the webhook URL in Chargebee

    The trigger needs Chargebee to call n8n. In your Chargebee dashboard, go to Settings, then Configure Chargebee, scroll down to Webhooks and select Add Webhook. Enter a Webhook Name and paste the Webhook URL from your n8n trigger node, then select Create. A webhook is simply a URL that Chargebee calls the moment something happens, which is why events reach n8n in seconds with no polling.

Triggers

What starts a workflow from Chargebee ?

Chargebee Trigger is the node that starts a workflow when something happens in Chargebee. It listens to 34 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Chargebee account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

card_added.*1
  • card_added.
    • card_added
card_deleted.*1
  • card_deleted.
    • card_deleted
card_expired.*1
  • card_expired.
    • card_expired
card_expiring.*1
  • card_expiring.
    • card_expiring
card_updated.*1
  • card_updated.
    • card_updated
customer_changed.*1
  • customer_changed.
    • customer_changed
customer_created.*1
  • customer_created.
    • customer_created
customer_deleted.*1
  • customer_deleted.
    • customer_deleted
invoice_created.*1
  • invoice_created.
    • invoice_created
invoice_deleted.*1
  • invoice_deleted.
    • invoice_deleted
invoice_generated.*1
  • invoice_generated.
    • invoice_generated
invoice_updated.*1
  • invoice_updated.
    • invoice_updated
payment_failed.*1
  • payment_failed.
    • payment_failed
payment_initiated.*1
  • payment_initiated.
    • payment_initiated
payment_refunded.*1
  • payment_refunded.
    • payment_refunded
payment_succeeded.*1
  • payment_succeeded.
    • payment_succeeded
refund_initiated.*1
  • refund_initiated.
    • refund_initiated
subscription_activated.*1
  • subscription_activated.
    • subscription_activated
subscription_cancellation_scheduled.*1
  • subscription_cancellation_scheduled.
    • subscription_cancellation_scheduled
subscription_cancelled.*1
  • subscription_cancelled.
    • subscription_cancelled
subscription_cancelling.*1
  • subscription_cancelling.
    • subscription_cancelling
subscription_changed.*1
  • subscription_changed.
    • subscription_changed
subscription_created.*1
  • subscription_created.
    • subscription_created
subscription_deleted.*1
  • subscription_deleted.
    • subscription_deleted
subscription_reactivated.*1
  • subscription_reactivated.
    • subscription_reactivated
subscription_renewal_reminder.*1
  • subscription_renewal_reminder.
    • subscription_renewal_reminder
subscription_renewed.*1
  • subscription_renewed.
    • subscription_renewed
subscription_scheduled_cancellation_removed.*1
  • subscription_scheduled_cancellation_removed.
    • subscription_scheduled_cancellation_removed
subscription_shipping_address_updated.*1
  • subscription_shipping_address_updated.
    • subscription_shipping_address_updated
subscription_started.*1
  • subscription_started.
    • subscription_started
subscription_trial_ending.*1
  • subscription_trial_ending.
    • subscription_trial_ending
transaction_created.*1
  • transaction_created.
    • transaction_created
transaction_deleted.*1
  • transaction_deleted.
    • transaction_deleted
transaction_updated.*1
  • transaction_updated.
    • transaction_updated

The trigger also accepts * (any event). Handy for logging, dangerous in production.

Configuration notes

01Set up the Chargebee TriggerThe Chargebee Trigger (version 1) starts a workflow when Chargebee events occur. There is one thing to configure and it is the event list.

The Chargebee Trigger (version 1) starts a workflow when Chargebee events occur. There is one thing to configure and it is the event list.

Key parameters

  • Events: the list of Chargebee events this workflow reacts to. All 34 events are in the dropdown, grouped by the object they belong to, and you tick as many as the workflow needs.
  • Events set to *: the wildcard, meaning every event Chargebee sends. Useful when you want one workflow to catch everything and sort it downstream, less useful when you want a tight, readable canvas.
When to use it
pick the specific events for anything customer-facing, where a wrong branch sends a wrong email. Keep the wildcard for logging and for the exploratory phase, when you still want to see what your Chargebee site actually emits during a normal week.
02React to subscription eventsSubscriptions carry the largest share of the 34 events, which matches how much of a billing platform's life happens on the subscription object.

Subscriptions carry the largest share of the 34 events, which matches how much of a billing platform's life happens on the subscription object.

Key parameters

  • Events, state changes: subscription_created, subscription_started when a future subscription gets going, subscription_activated after the move from trial to active, subscription_changed on recurring items, subscription_renewed, subscription_reactivated, subscription_deleted, and subscription_shipping_address_updated.
  • Events, the cancellation path: subscription_cancellation_scheduled, subscription_cancelling 6 days before the scheduled date, subscription_cancelled, and subscription_scheduled_cancellation_removed when someone changes their mind.
  • Events, the two heads-up events: subscription_trial_ending 6 days before the trial ends and subscription_renewal_reminder 3 days before renewal.
Use cases
a save workflow that fires on the scheduled cancellation rather than on the cancellation itself, so the conversation with the customer happens while the subscription is still alive and still billable.
03React to invoice and payment eventsMoney moving is the other half of the picture, and it splits into 4 invoice events and 5 events on payments and refunds.

Money moving is the other half of the picture, and it splits into 4 invoice events and 5 events on payments and refunds.

Key parameters

  • Events, invoices: invoice_generated when a new invoice is generated, invoice_updated when the billing or shipping address changes, when the invoice is voided, or when the amount due moves because a payment was applied or removed, plus invoice_created and invoice_deleted.
  • Events, payments: payment_succeeded on collection, payment_failed when a card charge fails, payment_initiated for a direct debit payment, payment_refunded, and refund_initiated for a refund started via direct debit.
When to use it
invoice_created only fires in metered billing, on a pending invoice that still has usage charges to add, and only when the Notify for Pending Invoices option is on. For the everyday case, invoice_generated is the one you want.
04React to card eventsCards get their own group of 5 events, and they are the quietest useful ones on the list because they let you fix a payment problem before it becomes a failed charge.

Cards get their own group of 5 events, and they are the quietest useful ones on the list because they let you fix a payment problem before it becomes a failed charge.

Key parameters

  • Events, the early warning: card_expiring fires 30 days before the expiry date, which is the window you have to ask for new details without any drama.
  • Events, after the fact: card_expired once the date has passed, and card_deleted when a card is removed from a customer.
  • Events, housekeeping: card_added and card_updated, handy for confirming to a customer that their new card is on file.
Use cases
a reminder sequence built on card_expiring, stopped by card_updated arriving for the same customer, is the cheapest churn reduction in this list.
05React to customer and transaction eventsTwo smaller groups close the count: 3 events on the customer record and 3 on transactions.

Two smaller groups close the count: 3 events on the customer record and 3 on transactions.

Key parameters

  • Events, customers: customer_created, customer_changed on any change to the record, and customer_deleted. These are the ones to mirror into a CRM or a directory so billing and sales see the same names.
  • Events, transactions: transaction_created when a transaction is recorded, transaction_deleted, and transaction_updated, which also covers a transaction being removed, an excess payment applied to an invoice, or a change to the capturable amount.
Use cases
transaction events feed a running ledger far better than invoice events do, because they describe what actually happened to the money rather than what was billed. Send them to a sheet, or straight into ERPNext if that is where your accounting lives.
Actions

What can the Chargebee node do?

The Chargebee node exposes 5 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateDeleteCancelListPDF Invoice URL
Customer✓
Invoice✓✓
Subscription✓✓

Customer

1 operation
01

Create a customer

customer.create

What you see in n8n

Notes & use cases

Adds a customer to Chargebee and hands the created record back to the workflow, so a signup captured elsewhere lands in billing without retyping.

Key parameters

  • Email: the customer email address, normally mapped from the item that started the run.
  • User ID: your own identifier for the customer. Leave it empty and Chargebee generates one for you.
  • First Name, Last Name, Phone and Company: the naming details that show up on invoices and in the customer list.
  • Custom Properties: sets values that are not in the predefined list, such as a plan code or an account owner.
Use cases
a self-serve form creates the customer, and the same run announces the new account to the team.

Invoice

2 operations
02

List an invoice

invoice.list

What you see in n8n

Notes & use cases

Returns invoices from your Chargebee site as items, which is what turns a monthly export chore into a workflow that runs itself.

Key parameters

  • Max Results: how many invoices come back, kept under 100 by the node. Plan a loop if you need a longer period rather than pushing the number up.
  • Filters: narrows which invoices are returned. Without one you get whatever the site hands over first, which is rarely the set you meant.
Use cases
a scheduled run pulls the invoices of the closing month, appends them to a spreadsheet, and the finance review starts from a sheet that is already filled in.
03

Get URL for the invoice PDF

invoice.pdfUrl

What you see in n8n

Notes & use cases

Hands back the URL of an invoice PDF. That link is what makes a billing notification useful instead of merely informative.

Key parameters

  • Invoice ID: the identifier of the invoice you want, and it is required, so an empty value stops the node. It usually comes from the previous node as an expression such as {{ $json.id }}, the n8n syntax for reading a field off the incoming item.
Use cases
a payment reminder that carries the document link, so the customer does not have to log in to find out what they are being reminded about.

Subscription

2 operations
04

Cancel a subscription

subscription.cancel

What you see in n8n

Notes & use cases

Cancels a subscription, either right away or at the end of the current term. The choice between those two is the whole point of this operation.

Key parameters

  • Subscription ID: required, the identifier of the subscription to cancel. An empty value blocks the node before it calls Chargebee.
  • Schedule End of Term: off, the cancellation happens directly. On, it is scheduled for the end of the term, which is what a customer who has already paid for the period expects.
Use cases
a cancellation request from a support tool goes through with the end of term option on, and the churn log is written in the same run.
05

Delete a subscription

subscription.delete

What you see in n8n

Notes & use cases

Removes a subscription from Chargebee rather than ending its billing cycle, which makes it a very different tool from the cancel operation above.

Key parameters

  • Subscription ID: required, the identifier of the subscription to delete. The node expects the identifier, not the customer name or the plan label, so read it from the item that triggered the workflow.
Use cases
a cleanup workflow that picks up subscriptions created by a broken form submission and removes them, with the removal posted to a channel so the record of what was deleted lives outside Chargebee too.
Need help

Need help automating Chargebee with n8n?

A person reads every message.

FAQ

Chargebee and n8n, the questions that come next

01Is the Chargebee n8n integration free?
Yes on the n8n side. Both the Chargebee node and the Chargebee Trigger ship with n8n, so there is nothing to install and no add-on to buy. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, which means you can prototype on one and move it to the other. What your Chargebee account itself costs is a separate question and depends on your plan with Chargebee, so check that with them rather than with us.
02Which credentials does Chargebee need in n8n?
One API key, and that is the only supported authentication method here. The credential asks for an Account Name and an API Key. Account Name is your Chargebee site name, the subdomain on its own: for a site at https://n8n.chargebee.com, the Account Name is n8n. The API Key comes from Chargebee's interface, following their documentation on creating an API key. The same credential authenticates the Chargebee node and the Chargebee Trigger, and once it is saved in the Credentials menu, every workflow you build can select it from the node's dropdown without re-entering anything.
03What are the limits of the Chargebee node in n8n?
Two things to keep in mind. The node covers 5 operations across 3 resources: creating a customer, listing invoices, getting an invoice PDF URL, cancelling a subscription and deleting a subscription. Anything else you need from the Chargebee API goes through the HTTP Request node, which calls any endpoint and reuses the same Chargebee credential through its predefined authentication, so you are not managing separate keys. Second, the List operation caps Max Results under 100, so a long reporting period is better handled by several filtered runs than by one big call.
04Does the Chargebee Trigger work in real time?
Yes. The Chargebee Trigger works over a webhook, which is a URL that Chargebee calls the moment an event happens, so each event reaches n8n within seconds and nothing is polled on a timer. You register that URL yourself in Chargebee, under Settings, then Configure Chargebee, then Webhooks, using the Add Webhook button. From there you tick the events you care about in the trigger's Events parameter, out of the 34 available, or use the wildcard to receive all of them. The workflow has to be active for the webhook to reach it.
05n8n or Make for Chargebee?
It depends on four things, and price is only one of them. Hosting: n8n runs on your own server or on n8n Cloud, while Make is hosted only, with no self-hosting option. Data control follows from that, which matters when the workflow carries invoices and customer records. Cost model: Make bills per operation, so a busy Chargebee site with 34 event types can get expensive as volume grows. Visual logic: both give you a canvas, and the honest answer is that the one your team reads faster is the one to pick. Try the same workflow on both before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations