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"

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel. Note: This trigger only supports attachment information for messages generated by bots. If you need to retrieve attachment information from non-bots, see this help document.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Trigger on files created by a single user.

Trigger when files are shared with you. Please note that this will trigger on created files as well.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only triggers when this reaction is added to a message. Use the dropdown to select one of your team's custom emoji or select Use a Custom Value and enter the name of a standard emoji. Use this cheat sheet for reference and be sure not to include the colons. Note that you cannot use an emoji's alias in this field.

Only triggers on reactions added on messages in this public channel. Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Only triggers on reactions added by this user.

Toggle to send to multiple users.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Include a file to send along with your message. NOTE: Bot names/icons cannot be customized when sending a File.

If you want this to be part of a thread, you'll need the timestamp (Ts) of the parent message. For example: 1345232312616.1231232.

If you get the message from a trigger, select "use a custom value" from the dropdown and connect accordingly by selecting the Ts field.

Otherwise, add a search step and fetch the message you want.

If true, posts in the thread and channel. See here for more info. Ignored unless the message is part of a thread.

Fields left blank will be ignored.

Fields left blank will be ignored.

Fields left blank will be ignored.

Changing a user's email address will send an email to both the old and new addresses, and also post a slackbot to the user informing them of the change.

Update selected values on this user's profile. This argument may only be specified by team admins on paid teams. Defaults to your status, when blank.

Note: Zapier's Slack app supports a limited set of OAuth scopes/permissions, thus many of Slack's API endpoints aren't currently feasible.

API docs for Slack are located here https://api.slack.com/methods

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

Search is case-insensitive

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

We search the normalized name, so don't worry about accents

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

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.

ID of the conversation, e.g. cnv_abc123

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

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Choose yes to trigger when someone creates a new name for an existing emoji.

Linked mentions of this user will trigger the zap. Make sure to specify a value for one or both of username or a highlight word. Specifying both a username and a highlight word means that both the linked username and word need to be included in a message to trigger the zap.

Mentions of this word will trigger the zap. Case insensitive. Make sure to specify a value for one or both of username or a highlight word. Specifying both a username and a highlight word means that both the linked username and word need to be included in a message to trigger the zap.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

The actual reminder text that should be sent to yourself or a user. To include URLs, Slack uses this syntax.

Slack parses natural language like "in 15 minutes" or "every Thursday". Times are relative to when the Zap actually runs.

Pick a user to remind. If you pick no one, you will be reminded.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Include a file to send along with your message. NOTE: Bot names/icons cannot be customized when sending a File.

If you want this to be part of a thread, you'll need the timestamp (Ts) of the parent message. For example: 1345232312616.1231232.

If you get the message from a trigger, select "use a custom value" from the dropdown and connect accordingly by selecting the Ts field.

Otherwise, add a search step and fetch the message you want.

If true, posts in the thread and channel. See here for more info. Ignored unless the message is part of a thread.

Name for the channel to be created. Channel names are normalized by converting to lowercase, replacing any non-allowed characters with hyphens or underscore, and truncating to 80 characters.

Slack will auto-link @names and #channels where applicable.

Leave empty to clear.

Use any emoji that's available in your Slack team, with leading and trailing :.

If emoji is blank when text isn't, :speech_balloon: is used by default. If both text and emoji are empty, your status will be cleared.

Provide a specific date & time for this status to expire. Statuses will not expire by default.

You can also specify a duration for this status by entering in a value like in 60 minutes, for example. Check out other ways you can use this field here.

Search query to use for finding matching messages. See the Slack Search Documentation for more information on constructing a query.

Sort messages by their match strength or by their date. Default is score.

Sort matching messages in ascending or descending order. Default is descending.

Search is case-insensitive

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

The leading @ is optional

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true