Connect Brevo to Mx Technologies

Both apps 66Brevo 31Mx Technologies 35

• Trigger
  Company Added

  Triggers when a company is created in Brevo.

• Trigger
  Company Updated

  Triggers when a company is updated in Brevo.

• Trigger
  Contact Added

  Triggers when a Brevo contact is added.

• Trigger
  Contact Subscribed to List (instant)

  Instant trigger — fires when a contact is added to a list (Brevo marketing webhook event listAddition). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Contact Unsubscribed

  Triggers when a contact unsubscribes from an email campaign in Brevo.

• Trigger
  Contact Updated (instant)

  Instant trigger — fires when a contact is updated (Brevo marketing webhook event contactUpdated). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Deal Added

  Triggers when a deal is created in Brevo.

• Trigger
  Deal Stage Updated

  Triggers when a deal's stage is updated in Brevo.

• Trigger
  Link Clicked

  Triggers when a Brevo contact clicks on any link in a Brevo email campaign.

• Trigger
  Marketing Email Delivered

  Triggers when a Brevo campaign marketing email is delivered.

• Trigger
  Marketing Email Hard Bounced

  Triggers when a Brevo campaign marketing email is hard bounced.

• Trigger
  Marketing Email Opened

  Triggers when a Brevo campaign marketing email is opened.

• Trigger
  New Campaign Status

  Triggers when the status of a Brevo campaign is updated.

• Trigger
  Transactional Email Delivered

  Triggers when a Brevo transactional email is delivered.

• Trigger
  Transactional Email Hard Bounced

  Triggers when a Brevo transactional email is hard bounced.

• Trigger
  Transactional Email Opened

  Triggers when a Brevo transactional email is opened.

• Action
  Add or Update Associations

  Adds or updates associations to companies, deals or contacts in Brevo.

• Action
  Add or Update Company

  Create a new company or update an existing one in Brevo.

• Action
  Add or Update Contact

  Creates or updates a contact. An attribute you map but leave EMPTY is IGNORED - the stored value is preserved, not deleted. Because of that, this action cannot CLEAR an attribute: to empty one, edit it in Brevo directly. Note an explicit null does not clear on Brevo either.

• Action
  Add or Update Deal

  Create a new deal or update an existing one in Brevo.

• Action
  Delete Company

  Deletes the selected company in Brevo, identified by its company ID.

• Action
  Delete Contact

  Deletes the selected contact in Brevo. The contact can be identified by its email address or its contact ID.

• Action
  Delete Deal

  Deletes the selected deal in Brevo, identified by its deal ID.

• Action
  Event Create

  Create event for selected contact.

• Action
  Find Company

  Finds companies in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Find Deal

  Finds deals in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Remove Associations

  Removes associations between companies, deals, or contacts in Brevo.

• Action
  Search Contact

  Check if a contact exists in Brevo and fetch the contact details. Contact can be found by email, mobile phone number, Brevo contact ID, external ID, Whatsapp ID and landline number.

• Action
  Send Transactional Email

  Sends an email from your Brevo account with HTML or plain text content.

• Action
  Send Transactional SMS

  Sends an transactional SMS from your Brevo account.

• Action
  Unsubscribe Contact

  Unsubscribe contact from the list(s) he belong to.

• Action
  Add account

  Creates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.

• Action
  Add budget

  Creates a budget for a category on an MX user.

• Action
  Add category

  Create a custom category for a user.

• Action
  Add goal

  Create a goal for a user.

• Action
  Add member

  Create a member (connection between a user and a financial institution) to start aggregation.

• Action
  Add transaction

  Creates a manual transaction on a manual account belonging to an MX user.

• Action
  Add user

  Creates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.

• Action
  Aggregate member

  Starts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.

• Action
  Delete account

  Delete a manually created account.

• Action
  Delete budget

  Deletes a budget belonging to an MX user.

• Action
  Delete category

  Delete a custom category.

• Action
  Delete goal

  Delete a goal.

• Action
  Delete member

  Delete a member connection.

• Action
  Delete user

  Delete a user.

• Action
  Get account

  Read an account's attributes.

• Action
  Get budget

  Retrieves a specific budget for an MX user.

• Action
  Get institution

  Read an institution's attributes.

• Action
  Get member

  Read a member's attributes and connection status.

• Action
  Get merchant

  Returns information about a particular merchant, such as its logo, name, and website.

• Action
  Get transaction

  Read a transaction's attributes.

• Action
  Get user

  Retrieves the attributes of a specific MX user.

• Action
  List accounts

  Lists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.

• Action
  List categories

  Lists all categories for an MX user, including default and custom categories.

• Action
  List goals

  Lists all goals for an MX user.

• Action
  List institutions

  Lists financial institutions available through MX, optionally filtered by name, country and supported product.

• Action
  List members

  List all members belonging to a user.

• Action
  List merchants

  Lists merchants in the MX system, optionally filtered by a name substring.

• Action
  List transactions

  List all transactions for a user.

• Action
  Update account

  Updates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.

• Action
  Update budget

  Update a specific budget.

• Action
  Update category

  Update a custom category.

• Action
  Update goal

  Updates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.

• Action
  Update member

  Updates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.

• Action
  Update transaction

  Update a transaction's category, description, or other editable attributes.

• Action
  Update user

  Update a user's attributes.

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