The Team that this Zap should be added to.

List of the inboxes the conversation must be in. Leave this empty if you would like to have this Zap trigger on all inboxes.

List of the inboxes the conversation is received in. Specifying no inboxes will trigger the event for every incoming message.

List of the inboxes the conversation is sent from. Specifying no inboxes will trigger the event for every outbound messages.

Handle of the contact (email address, phone number, twitter username, ...).

An optional unique identifier for this Account, usually from another data source like a CRM or internal system.

Email domain(s) of the account to be created (ex. acme.com). Contacts with matching email domains will be automatically associated with this account.

A mapping of the Custom Field name to value is expected. For example:
"Job title": "CEO". The custom field name must match an account custom field created in Front (case sensitive).

The ID of the team the contact should be associated to.

List of the contact's phone numbers. Each phone number must be in the format "+# (###) ###-####", with spaces after the country code and area code.

List of URLs (website, social media profile, ...).

List of the group names the contact belongs to. If a group doesn't exist in Front, it will automatically be created.

Custom attributes of the Account. A mapping of the Custom Field name to Custom Attribute is expected. For example:
"Job title": "CEO"

The conversation for which to post a comment.

The teammate who should be the author of this comment.

External URLs of the Links to add to the Conversation (e.g. `https://example.com/ORD-1234`). If a Link already exists with a matching URL, that Link will be added. If not, a new Link will automatically be created.

ID of the conversation to reply to. This value should start with "cnv_".

The teammate to assign the conversation to. Leave blank to unassign the conversation.

Channel for which the draft should be created.

Teammate on behalf of whom the draft will be created.

List of the recipient handles to draft the message to.

List of the recipient handles to cc on the draft.

List of the recipient handles to bcc on the draft.

Body of the message. Accepts plain text or HTML.

Whether to share the draft when creating it. If the draft is not shared, it will only be visible to the author. If it is shared, it will be visible to all teammates with access to the conversation.

The ID of the conversation to create a draft reply for. Should look like "cnv_1234"

The identifying URL of the Link, usually pointing to a task/item/loan/shipment etc. in an external system. E.g. `https://example.com/ORD-1234`

ID of the conversation, e.g. `cnv_abc123`

Inbox into which the message will be imported.

Can be an email address or a phone number.

List of the recipients the message has been sent to.

Set the format of the message body. The message body can be written in HTML or Markdown.

Unique identifier for the message.
**Duplicated external ID won't be imported**.

Select "Inbound" if the message is received or "Outbound" if the message is sent.

Teammate sending the message (Ignored if the message is inbound).

Whether or not the message should be directly archived once imported.

Select "Skip Rules" if you want Front to skip applying rules to this message, or "Apply Rules" if you want Front to apply rules to this message.

Messages with the same thread reference will be grouped in the same conversation.

Custom channel through which the message should be received.

Custom reference used to thread custom messages. If you omit this field, Front will thread by sender.

Custom object to store any additional metadata about the message.

IDs of the Links to remove from the Conversation (e.g. "top_123").

Channel through which the message will be sent.

List of the recipient handles to send the message to.

List of the recipient handles who will receive a copy of the message (for email messages only).

List of the recipient handles who will receive a blind copy of the message (for email only).

Specifying an author will send the message on behalf of this teammate.

Whether or not to archive the newly created conversation.

List of the tag names that will be added to the newly created conversation.

ID of the conversation to reply to. This value should start with "cnv_". Best if used with a Front message trigger.

List of the recipient handles who will receive this reply. By default Front will use the recipients of the last received message.

List of the recipient handles who will receive a copy of this reply. By default Front will use the cc'ed recipients of the last received message.

List of the recipient handles who will receive a blind copy of this reply.

Subject of the reply. By default, Front will reuse the subject of the conversation.

Channel through which the reply should be sent.
Mandatory only if the conversation has been imported with the API (no channels) or has been received on multiple channels.

List of the tag names that will be added to the conversation.

Whether or not to archive the conversation after sending the reply.

List of all the tags to apply to the conversation.

**This list will entirely replace the conversation tags** meaning that new tags will be added and missing ones will be removed.

New email domain(s) of the Account. All email domains that this account should have should be provided.

A mapping of the Custom Field name to value is expected. Only Custom Attributes that should be added or updated need to be included. The custom field name must match an account custom field created in Front (case sensitive).

For example:
"Job title": "CEO"

List of the group names the contact belongs to. If a group doesn't exist in Front, it will automatically be created. If the "Remove Contact From Every Group" option is checked, this field is ignored and the contact will not belong to any groups.

Checking this option will make sure the contact does not belong to any group. Checking this option will override the "Groups" field above.

Custom attributes of the Account. A mapping of the Custom Field name to Custom Attribute is expected. 
IMPORTANT NOTE:
ALL custom attributes that you wish to keep on the Contact must be provided. Any custom attributes that currently exist on the Contact that are not provided will be removed.

For example:
"Job title": "CEO"

Front is the shared inbox for teams that brings your email, communication channels, and apps into one platform for collaboration.

Front

Zendesk is a web-based help desk support tool that makes it simple to provide great customer support.

Zendesk

One of the most popular email services, Gmail keeps track of all your emails with threaded conversations, tags, and Google-powered search to find any message you need.

Gmail

Help Scout is the ideal small business help desk. You can deliver great email support and get setup in minutes, without any of the typical help desk complexities.

Help Scout

Intercom is the Engagement OS, an open channel between customer and business that is in the product, in the moment, and on their terms. We break down silos, unifying data and systems to create an ongoing dialogue, so companies can make the most of every opportunity.

Intercom

Hiver is a Gmail-based helpdesk that helps customer service teams easily access, assign and track customer emails on shared mailboxes.

Zapier Automation Platform

By role

By workflow

By company size

By role

Learn more

Get help

Front Integrations

Front Help & Support

How to get started with Front on Zapier

About Front

Related categories

Similar apps

Zendesk

Gmail

Help Scout

Get started for free