Connect Reply to Mx Technologies

Both apps 58Reply 23Mx Technologies 35

• Trigger
  Inbox Category Set for Reply

  Triggers when an email reply in Reply is given an inbox category, automatically or by a user.

• Trigger
  New Email Opened

  Triggers when a contact opens a tracked email sent from Reply.

• Trigger
  New Emails Sent

  Triggers when Reply sends an email from a sequence step.

• Trigger
  New Link Clicked

  Triggers when a recipient clicks a tracked link in an email sent from Reply.

• Trigger
  New Person Bounce

  Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server.

• Trigger
  New Person Opt Out

  Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).

• Trigger
  Prospect Finished

  Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.

• Action
  Add contact list

  Creates a new contact list in Reply, optionally shared with your team.

• Action
  Add note to contact

  Adds a note to a contact's timeline in Reply.

• Action
  Add sequence

  Creates a new sequence in Reply with its steps, schedule, sending accounts and settings.

• Action
  Create\Update Person

  Creates a Reply contact, or updates the existing contact with the same email address.

• Action
  Delete contact

  Deletes a contact from your Reply account.

• Action
  Find contacts by criteria

  Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.

• Action
  Get contact

  Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.

• Action
  Get sequence

  Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.

• Action
  List contact lists

  Returns the contact lists you own plus those shared with your team, optionally filtered by name.

• Action
  List contacts

  Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.

• Action
  List inbox categories

  Returns the inbox categories you can file conversations under.

• Action
  List Sequence Contacts

  Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.

• Action
  List sequences

  Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.

• Action
  Mark as Finished

  Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.

• Action
  Remove Person From Campaign

  Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.

• Action
  Send Test Webhook Event

  Sends a test event from an existing Reply webhook subscription to its configured URL.

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