Choose which ticket to update.

Choose which organization to update. Looked up by ID.

Must be unique. Zendesk does not allow duplicate organizations with the same name.

In this field you can store any details about the organization. e.g. the address

In this field you can store any notes you have about the organization.

Comma-separated list of tags you want to apply to the new organization.

Comma-separated list of domain names to automatically associated with this organization (format: "zapier.com, google.com").

A unique external id, you can use this to associate organizations to an external record.

Options: "true" or "false". End users in this organization are able to see each others tickets.

Options: "true" or "false". End users in this organization are able to see each others comments on tickets.

Write a search string to determine how we'll look up the agent in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the organization in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the user in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the ticket in Zendesk. For more information, visit the Zendesk docs.

Note: the assignee must be in the default group (or specific group selected below) else an error will occur.

You can add emails of non-Zendesk users here as Collaborators.

Assign this ticket to a group.

To set the Requester, you must specify the Requester Name in this field AND the Requestor Email in the next field.

To set the Requester, you must specify the Requester Email in this field AND the Requestor Name in the previous field.

A comma separated list of tags.

Only available for tickets with a Type of "task."

If selected, this person will be set as the submitter of the ticket. Defaults to the Requester.

If selected, this will set the form to render for this ticket. Note: this is only applicable for Zendesk enterprise accounts.

Note: Only for Zendesk customers on plans with multi-brand support. More info here

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

Select a link from your campaign to track. It's not currently possible to trigger on all link clicks for a campaign with a single Zap.

If no (and by default) this trigger will only fire the first time a user clicks a link in your campaign.

To prevent timeout errors, please ensure the list of customers for this store does not exceed 3000.

If specified, will only trigger on orders created in this store. Otherwise, will default to all orders in your account.

To prevent timeouts, please ensure the list of subscribers in the segment/tag does not exceed 3000.

Select the audience you want to send the campaign to.

Select which segment or tag you want to send the campaign to. If no segment/tag is selected, the campaign will be sent to the entire audience selected above.

This snippet will appear in the inbox after the subject line.

Supports *|MERGETAGS|* for recipient name, such as *|FNAME|*, *|LNAME|*, *|FNAME|* *|LNAME|*, etc.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

The email address of the subscriber for the custom event. The email address must already be subscribed to the audience.

Must be 2-30 characters in length. Note: Letters, numbers, underscores, hyphens, and any spaces between are considered valid characters. Any invalid characters will be ignored.

Additional properties for this event (e.g. "User Type: Premium", "Preferred Communication: Email", etc). Note: Letters, numbers, underscores, hyphens, and any spaces between are considered valid characters. Any invalid characters in the first column only will be ignored.

The email address of the subscriber you want to unsubscribe from this audience.

Completely delete this contact from MailChimp? (No: just unsubscribe them)

A Custom Value is typically used here to pass in the Campaign ID from a "Create Campaign" or "Find Campaign" step. Learn more

The tag to which the subscriber will be added.

The email address of the person you want to add to this segment. Note: the email address must already be subscribed to the audience, or this will fail.

The name of the Campaign to find

The name of the Campaign to find

Select the audience you want to send the campaign to.

Select which segment or tag you want to send the campaign to. If no segment/tag is selected, the campaign will be sent to the entire audience selected above.

This snippet will appear in the inbox after the subject line.

Supports *|MERGETAGS|* for recipient name, such as *|FNAME|*, *|LNAME|*, *|FNAME|* *|LNAME|*, etc.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

Select either a template or provide HTML email content, you cannot provide both. If both fields are left blank, the campaign draft will have no content.

The email address of the Subscriber you want to find.

Limit your search to this specific Audience.

The email address of the subscriber you want to subscribe to this audience. Please don't type an email address in this field, instead this should use a value from a previous step in your Zap. Learn more here.

If yes, a confirmation email will be sent to the address before they appear on the chosen audience.

If no, the Zap will skip/halt this step if the subscriber exists, otherwise overwrites data sent.

Determines what changes to make to the subscriber's groups/interests.

• Add Only The group(s) specified below will be added to the subscriber's existing groups/interests.
• Replace All All of the subscriber's existing groups will be cleared, and replaced with the groups selected below.
• Replace Matching Clears any existing group selections only for the groups specified below. Learn more here.

This should be a two letter language code (ISO639-1) See here for the list of language codes.

The tag(s) to which the subscriber will be added. Tags will be added to any existing tags on existing subscribers.

Choose which ticket to update.

A list of tags to add to the ticket.

Choose which ticket to update.

Note: the assignee must be in the default group (or specific group selected below) else an error will occur.

Assign this ticket to a group.

A comma separated list of tags.

If selected, this person will be set as the submitter of the ticket. Defaults to the Requester.

Write a search string to determine how we'll look up the group in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the ticket in Zendesk. For more information, visit the Zendesk docs.

Write a search string to determine how we'll look up the organization in Zendesk. For more information, visit the Zendesk docs.

Must be unique. Zendesk does not allow duplicate organizations with the same name.

In this field you can store any details about the organization. e.g. the address

In this field you can store any notes you have about the organization.

Comma-separated list of tags you want to apply to the new organization.

Comma-separated list of domain names to automatically associated with this organization (format: "zapier.com, google.com").

A unique external id, you can use this to associate organizations to an external record.

End users in this organization are able to see each others tickets.

End users in this organization are able to see each others comments on tickets.

Write a search string to determine how we'll look up the user in Zendesk. For more information, visit the Zendesk docs.

Must be unique. Zendesk does not allow duplicate users with the same email address.

In this field you can store any notes you have about the user.

Phone number for this user (format: +1 (555) 123-4567).

Comma-separated list of tags you want to apply to the new user.

Can be one of the following: "end-user", "agent", or "admin". Defaults to "end-user" if set and not one of those values.

Assign this user to an organization.

A unique external id, you can use this to associate organizations to an external record.

Specify if you know this user is who they say they are?

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

If no (and by default) this trigger will only fire the first time a user opens an email.

When samples are pulled in the next step for this trigger, the GROUPINGS data will be static, dummy data ("Example Group Category 1"). Use the example Group values to setup your Zap, and the data should reflect appropriately when the Zap runs.

When samples are pulled in the next step for this trigger, the GROUPINGS data will be static, dummy data ("Example Group Category 1"). Use the example Group values to setup your Zap, and the data should reflect appropriately when the Zap runs.

Examples: Conference Lead, Influencer, or Donor (Tag length is limited to 100 characters).

The email address of the subscriber you want to subscribe to this audience. Please don't type an email address in this field, instead this should use a value from a previous step in your Zap. Learn more here.

If yes, a confirmation email will be sent to the address before they appear on the chosen audience.

If no, the Zap will skip/halt this step if the subscriber exists, otherwise overwrites data sent.

Determines what changes to make to the subscriber's groups/interests.

• Add Only The group(s) specified below will be added to the subscriber's existing groups/interests.
• Replace All All of the subscriber's existing groups will be cleared, and replaced with the groups selected below.
• Replace Matching Clears any existing group selections only for the groups specified below. Learn more here.

This should be a two letter language code (ISO639-1) See here for the list of language codes.

The tag(s) to which the subscriber will be added. Tags will be added to any existing tags on existing subscribers.

The email address of the person you want to remove from this tag. Note: the email address must already be subscribed to the audience, or this will fail.

The email address of the subscriber you want to add a note to. The email address must already be subscribed to the audience.

The content of the note. Note length is limited to 1,000 characters.

API docs for Mailchimp are located here https://mailchimp.com/developer/reference/

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.

The email address of the Subscriber you want to find.

Limit your search to this specific Audience.

Examples: Conference Lead, Influencer, or Donor (Tag length is limited to 100 characters).