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

Short description.

List of the contact's email addresses.

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.

Picture of the contact.

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

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

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.

Subject of the draft message.

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.

Channel for which the draft should be created.

Channel through which the message will be sent.

Sender's name.

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

Subject of the message.

Body of the message. Accepts plain text or HTML.

File to attach to the message.

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.

List of Tag IDs.

ID of the Account to be updated.

New name of the Account

New description of the Account

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"

Inbox to move the conversation to.

Teammate to assign the conversation to.

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.

Email domain of the Account

External ID of the Account

ID of the Account to be retrieved

Email domain of the Account

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

ID of the Account to be retrieved

Name of the Account to be created

Description of the Account to be created

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

Query results must have a unique id field so we can deduplicate records properly! Otherwise we will make a best guess. You must also include desired ordering and limiting in the query.

Note: This query must run in less than 30 seconds and it is recommended that you return no more than 5,000 rows

Usually something auto-incremented like id. Must be unique. Column names that contain a space must be enclosed within brackets [ ].

Usually something like date_updated or last_modified. This should ideally be a datetime column that is set to the current datetime whenever a row is updated.

Trigger on changes to cells in this column only. Leave blank if you want to trigger on changes to cells in all columns.

You should include desired ordering and limiting (usually to 1 record) in the query.

This query must run in less than ~30 seconds.

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.

Subject of the draft message

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.

A display name for this LInk

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

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

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.

Body of the reply.

File to attach to the message.

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.

List of Tag IDs.

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

Short description about the contact.

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

Picture of the contact.

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"

New name of the Link.

Email or phone number of contact.

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

Email or phone number of contact.

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

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

Short description.

List of the contact's email addresses.

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.

Picture of the contact.

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

We expect at least one unique (and usually autoincrement) primary key column so we can deduplicate records properly! Otherwise we will make a best guess on a random column to use to deduplicate.

Highly recommended! Usually you want the results to be most recent first so we can skim off only new results, so choose something like date_created or your autoincrement id. Column names that contain a space must be enclosed within brackets [ ].

We default to what the primary key is on the table as the unique key to deduplicate on. If you prefer another field, select it here.