Connect Chargebee to MoEngage

Both apps 26Chargebee 18MoEngage 8

• Trigger
  New Payment Method

  Triggers when a payment method is added.

• Trigger
  Payment Method Updates

  Triggers when a payment method is updated.

• Action
  Cancel Subscription

  Cancels a Chargebee subscription immediately, at the end of the term, or on a specific date.

• Action
  Change Next Billing Date

  Updates next billing date of a subscription.

• Action
  Create Customer

  Creates a customer in Chargebee, optionally with a billing address and a payment source (card, bank account, payment method token or payment intent).

• Action
  Create Subscription

  Creates a new subscription for an existing Chargebee customer from one or more item prices, and returns the subscription along with the customer, card and any invoice it generated.

• Action
  Delete Customer Card

  Deletes the card on file for a customer. Chargebee turns off auto collection for the customer and fires a card_deleted event. Succeeds without error when the customer has no card.

• Action
  Fetch Customer Subscription Details

  Retrieves a subscription by ID, along with the customer who owns it and their card on file.

• Action
  Fetch Subscription Invoice Details

  Fetches the invoices raised for one subscription, most recent first by default, with optional filters on status, dates and more.

• Action
  Find Existing Subscription

  Returns up to 100 subscriptions that match all of the specified criteria, such as subscription ID, customer ID, plan item or status.

• Action
  Finds an Existing Customer

  Finds customers whose details exactly match the criteria you supply (email, name, company, phone, ID and more). Returns up to 100 matches and the first match on its own.

• Action
  Get Invoice

  Retrieves a single Chargebee invoice by its ID.

• Action
  List Invoices

  Returns all invoices in the Chargebee site.

• Action
  Reactivate Subscription

  Restores a cancelled subscription to active, or to trial when a trial end is given.

• Action
  Record Offline Payment for an Invoice

  Records a payment received outside Chargebee (cash, check, bank transfer, etc.) against an invoice. The invoice must be in payment_due, posted or not_paid status.

• Action
  Update Card Payment Source

  Changes the cardholder name, expiry date or billing address on a customer's saved card.

• Action
  Update Customer

  Updates the details of an existing Chargebee customer, including custom fields. Billing address and VAT number are changed through Chargebee's separate billing-info update, not this action.

• Action
  Update Subscription

  Updates a subscription in Chargebee.

• Action
  Add or Remove User From Cohort (Audience)

  Adds users to, or removes users from, a partner-synced custom segment (cohort) in MoEngage. Only users who already exist in MoEngage are matched; no new users are created.

• Action
  Create or update device

  Creates a new device for an existing MoEngage user, or updates the properties of one of that user's devices. MoEngage accepts the request and processes it shortly afterwards.

• Action
  Create or Update User

  Creates a new MoEngage user or updates the attributes of an existing user.

• Action
  Delete users

  Requests permanent deletion of one MoEngage user, identified by customer ID or MoEngage ID. The user stays active for a 24-hour buffer period and cannot be retrieved once deleted.

• Action
  Fetch Campaign Report

  Downloads a generated MoEngage campaign report file by its file name. Reports can be downloaded for 7 days after they are generated.

• Action
  Find users

  Returns the MoEngage user profiles that match the Customer IDs or MoEngage IDs you specify, and lists any IDs that were not found.

• Action
  Import User Event

  Records one or more events a user performed, with their attributes and times, on the user's MoEngage profile. Creates the user if needed.

• Action
  Merge users

  Merges duplicate MoEngage user profiles by moving each merged user's data into the retained user. MoEngage cannot undo a merge, so check the user IDs before running it.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.