Chargebee

Overview

The Chargebee connector receives webhooks from your site and turns each event into a typed event with the subscription, customer and invoice attached. Deliveries are protected with basic auth, and every event appears in the trace of the run it started.

Revenue teams use it to start a dunning sequence in Intercom when a payment fails, to update the account owner in HubSpot on cancellation and to load new invoices into Snowflake each day.

Event coverage

• subscription_created, subscription_renewed and subscription_cancelled

• payment_succeeded, payment_failed and payment_refunded

• invoice_generated and credit_note_created

How webhooks work

Chargebee posts each event to a Tessel URL in your workspace region. Tessel checks the credentials, validates the payload against the schema for your API version and starts the matching workflow. Events for one subscription are processed in order.

{
  "id": "ev_16BHbhF4s42tO2lK",
  "event_type": "payment_failed",
  "api_version": "v2",
  "content": {
    "subscription": { "id": "sub_AzZ8kY", "resource_version": 1728205440123 },
    "transaction": { "amount": 4900, "error_code": "card_declined" }
  }
}

{
  "id": "ev_16BHbhF4s42tO2lK",
  "event_type": "payment_failed",
  "api_version": "v2",
  "content": {
    "subscription": { "id": "sub_AzZ8kY", "resource_version": 1728205440123 },
    "transaction": { "amount": 4900, "error_code": "card_declined" }
  }
}

{
  "id": "ev_16BHbhF4s42tO2lK",
  "event_type": "payment_failed",
  "api_version": "v2",
  "content": {
    "subscription": { "id": "sub_AzZ8kY", "resource_version": 1728205440123 },
    "transaction": { "amount": 4900, "error_code": "card_declined" }
  }
}

Event ordering

Chargebee can deliver events out of order after a retry. Tessel compares resource_version on each record and skips any event older than one it has already processed.

Permissions needed

Create an API key for Tessel in Chargebee settings. It needs read access to customers, subscriptions and invoices. A full-access key is only required for subscription updates and credit notes.

• A Read-Only Key with access to all resources, for triggers and lookups

• A Full-Access Key only if a workflow writes back

• Basic auth credentials on the webhook, stored in your region