New Chargebee subscriptions posted in Slack
Each new Chargebee subscription is posted to your Slack channel with the customer, plan, billing period, trial or active status and MRR.
Combine Chargebee + Slack and move subscription data into channels where your team already talks. Just ask Letaido's AI agent and watch it do the work.
Use this Chargebee Slack integration for signups, failed payments, cancels, weekly digests and customer lookups.
Each new Chargebee subscription is posted to your Slack channel with the customer, plan, billing period, trial or active status and MRR.
When a Chargebee payment fails or a subscription is cancelled, Letaido posts the customer, plan, amount due or cancel reason to your retention channel.
Every Monday, Letaido posts last week's new and cancelled Chargebee subscriptions to Slack, with MRR per currency, the largest new subscriptions and cancel reasons.
Mention @Letaido with a customer's email and it replies in the thread with their Chargebee plan, status, next billing date and last 3 invoices.
Chargebee's own Slack app posts the alerts you tick. Leta runs the jobs you describe.
| Option | New subscription alerts | Failed payments and cancels | Weekly signups digest | Look up a customer from Slack |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | |
| Chargebee for Slack | Yes | Yes | Partly | No |
| Zapier | Yes | Yes | Partly | Partly |
| Option | What starts it | Good at | Keep in mind |
|---|---|---|---|
| Letaido AI agent | A Chargebee event (new subscription, failed payment, cancellation), a mention of @Letaido in Slack, a weekly schedule, or you asking | Posts you word yourself: new subscriptions with plan and MRR, at-risk customers with the card error or cancel reason, a Monday digest of signups and cancels, and customer answers in a thread | Every job on this page only reads Chargebee, so retries, dunning and refunds stay in Chargebee. Chargebee event jobs need a webhook in Chargebee. Invite the Letaido bot to each channel |
| Chargebee for Slack | Chargebee events you tick in its notification preferences, such as a customer signing up, a payment failing or an invoice sent for the first time | Alerts for sign ups, trial conversions, payment updates and cancellations in one channel, plus an optional daily metrics report for the day before | Built by Chargebee and available on all Chargebee plans. Only the team owner or an admin can set it up. You pick events, not the wording, and its docs describe notifications only, not lookups |
| Zapier | A Chargebee trigger such as New Subscription, Payment Failure or Subscription Cancellation, or a Slack trigger such as New Mention | One Slack message per event from a template you fill with Chargebee fields, for example its "Send Slack messages for new ChargeBee subscriptions" template | You build and look after each Zap. A digest or a lookup needs extra steps, such as its Finds an Existing Customer search. Each successful Slack message uses one Zapier task |
A job can start when a new Chargebee subscription is created or a Chargebee payment fails or a subscription is cancelled or someone mentions @Letaido in Slack, like “New Chargebee subscriptions posted in Slack”.
Saved as an automation, like “Weekly signups and cancellations in Slack”: every Monday at 9am.
Ask in chat; Leta picks from 86 actions.
Slack events Letaido can react to · Chargebee events Letaido can react to
Allow all read operations once per app; approve each kind of write once.
Cancel subscription · Update customer · Create subscription for customer · Send invoice email
Set channel topic · Make file public · Get thread messages · Revoke file public
Yes. Chargebee's own Slack app posts the events you tick, such as sign ups, failed payments and cancellations, to one channel. With Letaido, its AI agent Leta runs the jobs around that: posts you word yourself, a weekly digest and customer lookups from Slack.
Paste your Chargebee site name and API key, then create the Slack app from Letaido's manifest. Invite the Letaido bot to each channel it posts in, then describe the job in chat or paste a prompt from a job on this page.
Yes. Jobs that start from a Chargebee event need a webhook in Chargebee that points to the URL Letaido gives you. The weekly digest runs on a schedule instead, every Monday at 9am.
Leta posts the customer, plan, amount due, the card error and the next retry date to #retention, or 'Next retry not provided' when the event has none. Chargebee is only read, so its own retries and dunning emails carry on as before.
Yes. Mention @Letaido with the customer's email and it replies in the thread with their plan, status, next billing date and last 3 invoices. Keep the app_mention event on in your Slack app.
Yes. Zapier has templates such as "Send Slack messages for new ChargeBee subscriptions", and each successful Slack message uses one Zapier task. There you build and look after each Zap; with Leta you describe the job, and a digest or a lookup is one request.
No. Every job on this page only reads Chargebee and writes to Slack.
Yes. Allow all read operations once per app; approve each kind of write once.
Connect Chargebee and Slack, then ask for a job like "Post new Chargebee subscriptions to Slack". Leta gets it done the moment something happens, or the moment you ask.
Get Letaido