Connect Bento to MoEngage

Both apps 32Bento 24MoEngage 8

• Trigger
  New Tag

  Triggers when a new tag is created on your Bento site.

• Action
  Add broadcast

  Creates a broadcast email draft in Bento, optionally scheduled and approved for sending to tagged or segmented subscribers.

• Action
  Create Field

  Creates a custom subscriber field on your Bento site.

• Action
  Create or Update User

  Creates a Bento subscriber, or updates the name of an existing one, by email address.

• Action
  Create or Update User and Apply Tag

  Creates or updates a Bento subscriber by email and applies one or more tags, without triggering Flows.

• Action
  Create or Update User and Apply Tag (Trigger Flows)

  Applies a tag to a Bento subscriber (creating them if needed) through an event, so any Flows listening for that tag start.

• Action
  Create Tag

  Creates a tag on your Bento site.

• Action
  Delete tag

  Discards a tag in Bento by name (running it on an already-discarded tag restores it).

• Action
  Fetch Site Metrics

  Returns your Bento site's user, subscriber and unsubscriber counts.

• Action
  Fetch Subscriber

  Returns a Bento subscriber's details, tags and custom fields by email address.

• Action
  Get email template

  Returns one email template, including its name, subject and HTML content.

• Action
  Get segment

  Returns one segment, including its name, description and filter definition.

• Action
  Import subscribers

  Queues up to 1,000 subscribers for import or update in Bento. Imports do not trigger automations.

• Action
  List Broadcasts

  Returns one page of Bento broadcasts with the chosen status, including their send stats.

• Action
  List Fields

  Returns every custom subscriber field on your Bento site.

• Action
  List segments

  Returns all segments in your Bento site.

• Action
  List sequences

  Returns the sequences on your Bento site, including each sequence's email templates.

• Action
  List Tags

  Returns every tag on your Bento site.

• Action
  List workflows

  Returns all workflows on the Bento site, with their name, status and email templates.

• Action
  Remove Tag from Subscriber

  Removes a tag from a Bento subscriber by email.

• Action
  Track Subscribe Event

  Subscribes or unsubscribes a Bento subscriber by email.

• Action
  Update email template

  Updates the subject, HTML content, or editor type of a Bento email template.

• Action
  Update Subscriber Field

  Sets one custom field value on a Bento subscriber.

• Action
  Validate Email

  Checks whether an email address looks valid and deliverable.

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