Connect Reply to Front

Both apps 51Reply 23Front 28

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

  Adds an internal comment to a Front conversation.

• Action
  Add Contact Handle

  Adds a new handle (email, phone, social id, etc.) to an existing Front contact.

• Action
  Add Conversation Links

  Adds one or more links to a Front conversation, either existing links by id or external URLs (links are created as needed).

• Action
  Add Conversation Tags

  Adds one or more tags to a Front conversation.

• Action
  Assign or Unassign Conversation

  Assign or unassign a conversation to a teammate.

• Action
  Create Account

  Create a new account (company) in Front.

• Action
  Create Contact

  Creates a new contact in Front at the company level.

• Action
  Create Draft

  Creates a draft message that starts a new conversation in a Front channel.

• Action
  Create Draft Reply

  Creates a new draft as a reply to the last message in a Front conversation.

• Action
  Create Link

  Creates a new Link

• Action
  Find Account

  Finds a Front account by one of its domains or by its external ID.

• Action
  Find Contact

  Finds a Front contact by one of its handles (email address, phone number, social handle, etc.) and returns the matching contact.

• Action
  Find Conversation

  Returns up to 100 conversations matching a Front search query, most recently active first.

• Action
  Get Conversation

  Fetches a conversation by ID, with its status, assignee, tags, links and custom fields. An error occurs if the conversation is not found.

• Action
  Get Conversation Last Message

  Returns the most recent message in a Front conversation.

• Action
  Get Link

  Fetches a link by ID, with its name, type and external URL. An error occurs if the link is not found.

• Action
  Import Message

  Imports a message into a Front inbox without sending it through a channel, e.g. historical conversations or web form submissions.

• Action
  List Conversation Comments

  Returns the internal comments teammates have posted on a conversation, with each comment's body, author and time posted.

• Action
  List Link Conversations

  List the conversations linked to a specific Front link.

• Action
  Remove Contact Handle

  Removes a handle (email, phone, etc) from a Contact

• Action
  Remove Conversation Links

  Remove Links from a conversation.

• Action
  Remove Conversation Tags

  Remove Tags from a Conversation

• Action
  Send Message

  Sends a new message from a Front channel, starting a new conversation.

• Action
  Send Reply

  Replies to a conversation. This action is best used with a Front trigger. For example, auto-reply behavior could be setup by combining a "New Inbound Message" Front trigger with this action.

• Action
  Update Account

  Updates an existing account in Front.

• Action
  Update Contact

  Updates an existing Front contact's name, description, links, contact lists and custom fields. Fields left blank are not changed.

• Action
  Update Conversation

  Update the conversation status, assignee, inbox or tags.

• Action
  Update Link

  Update the name of a Link.

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