Connect Stax to MoEngage

Both apps 26Stax 18MoEngage 8

• Trigger
  List Payment

  Triggers when a new payment transaction is recorded in Stax.

• Action
  Capture payment

  Captures funds from a pre-authorized Stax transaction, turning the pre-authorization into a completed charge. Returns the updated transaction.

• Action
  Create Customer

  Creates a customer record on the Stax merchant account and returns the new customer.

• Action
  Create Item

  Creates an item in the merchant's Stax catalog and returns the new catalog item.

• Action
  Create Scheduled Invoice

  Creates a scheduled invoice that automatically generates invoices for a customer on a one-time or recurring schedule, with optional autopay. Returns the new schedule.

• Action
  Delete Catalog Item

  Deletes a catalog item from Stax.

• Action
  Delete payment method

  Deletes a customer's saved payment method in Stax and returns the deleted payment method.

• Action
  Delete Scheduled Invoice

  Deletes a recurring invoice schedule so it stops generating invoices.

• Action
  Find Customers

  Searches your Stax customers by name, email, company, phone, address or other details and returns the matching customers.

• Action
  Find Invoices

  Returns the invoices on the Stax merchant account that match the search criteria you supply, such as keywords, customer name, company, email, price, schedule or payment method.

• Action
  Find Items

  Searches the merchant's catalog for items matching a name, code, price or other criteria and returns the matching items.

• Action
  Find Payment Methods

  Returns all saved payment methods (cards and bank accounts) for a Stax customer.

• Action
  Find Payments

  Returns the payments and other transactions on the merchant account that match the search criteria, such as keywords, customer, date range, amount, type or status.

• Action
  Make a Payment

  Charges a customer's saved payment method for the amount you specify, or places a pre-authorization to capture later. Returns the resulting transaction.

• Action
  Refund payment

  Refunds all or part of a settled Stax payment transaction back to the customer.

• Action
  Update customer

  Updates an existing customer's contact details, address, notes and options in Stax, and returns the updated customer.

• Action
  Update invoice

  Updates an existing unpaid invoice's customer, amounts, line items, memos and payment options, and returns the updated invoice. Fully paid invoices cannot be edited.

• Action
  Void payment

  Voids a payment transaction in Stax before it settles, cancelling the charge.

• 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.