Updated payments in Chargebee — Deleting members in crowd.dev

The scenario catches updates to payments in Chargebee and deletes members in crowd.dev. Runs on its own, no manual copying.

  • A cancelled or refunded payment in Chargebee removes the person from crowd.dev right away.
  • Nobody keeps access they stopped paying for.
  • You don't clean non-payers out of the database by hand.

How it works

To keep Chargebee and crowd.dev in sync, connect them with a ready-made scenario — changes flow automatically.

  1. Starts when: Stripe
  2. Then: Bitwarden

You can launch this Chargebee + crowd.dev integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.