Please specify a project, tag, or workspace of the task that you are duplicating.

The name of the new task.

One or more fields to be included in the duplicated task

If you choose an Organization, you must specify a team. A team is used to group related projects and people together.

Add the task to this Section within the Project. This can only be used when one Project is selected above.

You can format the description using markdown syntax:
# Heading 1
## Heading 2

**bold text**
*italicized text*
~~strikethrough~~
> blockquote

Ordered List
1. First item
2. Second item
3. Third item

Unordered List
- First item
- Second item
- Third item

Code: `code`
Link: [title](https://www.example.com)

Note: Only the above syntax items will generate rich text in a task description.

Default false. If you have issues with XML errors, set this to true to resolve those.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due At. Ignores time.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due On. Considers time.

Can only be set if the Assignee is also set.

Either search for an existing task, or "Use a Custom Value" and select the "Task ID" if the task was created by a previous step in this Zap.

Cannot be used if Due At field is filled in.

Cannot be used if Due On field is filled in.

Can only be set if the Assignee is also set.

The name of the project to find (exact match first, fuzzy match second).

Specify one or more projects to search for an existing task.

The name of the task to find (exact match first, fuzzy match second).

Paginated results are only available if workspace is selected.

The existing project that contains the task to be found.

The name of the task to find (exact match first, fuzzy match second).

Add the task to this Section within the Project. This can only be used when one Project is selected above.

You can format the description using markdown syntax:
# Heading 1
## Heading 2

**bold text**
*italicized text*
~~strikethrough~~
> blockquote

Ordered List
1. First item
2. Second item
3. Third item

Unordered List
- First item
- Second item
- Third item

Code: `code`
Link: [title](https://www.example.com)

Note: Only the above syntax items will generate rich text in a task description.

Default false. If you have issues with XML errors, set this to true to resolve those.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due At. Ignores time.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due On. Considers time.

Can only be set if the Assignee is also set.

This is the last, long number in the address bar when you view a Task or in the Task Link you can copy.

Add the task to this Section within the Project. This can only be used when one Project is selected above.

You can format the description using markdown syntax:
# Heading 1
## Heading 2

**bold text**
*italicized text*
~~strikethrough~~
> blockquote

Ordered List
1. First item
2. Second item
3. Third item

Unordered List
- First item
- Second item
- Third item

Code: `code`
Link: [title](https://www.example.com)

Note: Only the above syntax items will generate rich text in a task description.

Default false. If you have issues with XML errors, set this to true to resolve those.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due At. Ignores time.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due On. Considers time.

Can only be set if the Assignee is also set.

Pick which type of object you want to watch for new items of (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Pick which type of object you want to watch for updated records of (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

The Content Document ID of a file that has been uploaded to a library in Salesforce CRM Content or Salesforce Files

Specifies whether this file is available to all users, internal users, or shared users.

Pick the type of object you want to attach the file to (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Defaults to false if left blank.

Pick the type of object if you want to attach the file to (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

API docs for Salesforce are located here https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm

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.

Pick which type of object you want to search for. You can only search for multiple records which are all the same object type.

Select the format of search results to be returned. If multiple search values are provided, the choice will be applied to each search value.

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

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

You need to choose a project before you can choose a task.

You must have a custom template saved in a Workspace or Team. https://asana.com/guide/help/premium/custom-templates

Specify which project.

Specify which task.

Specify your text.

Workspace must be specified to get dropdown selections in the Task, Project and Section list below. Not required if you will be using custom values to set the fields below.

Task to be moved to a project's section. The dropdown here will only include tasks that are assigned to you, but you can use this action with any task in the workspace selected above by specifying a "Custom Value" for this task field..

Project to which to move the task. Tasks can only be moved to projects in the same workspace..

Section to which to move the task. Task will be moved to the bottom of the section. If section is not specified for a list-type project, the task will be moved to the no section area of the project. If the section is not specified for a board-type project, the task will be added to the first column of the board.

API docs for Asana are located here https://asana.com/developers/api-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 existing project that contains the task to be found.

The name of the section to find (exact match first, fuzzy match second).

This is the last, long number in the address bar when you view a Task or in the Task Link you can copy.

The name of the project to find (exact match first, fuzzy match second).

If you choose an Organization, you must specify a team. A team is used to group related projects and people together.

Specify one or more projects to search for an existing task.

The name of the task to find (exact match first, fuzzy match second).

Add the task to this Section within the Project. This can only be used when one Project is selected above.

You can format the description using markdown syntax:
# Heading 1
## Heading 2

**bold text**
*italicized text*
~~strikethrough~~
> blockquote

Ordered List
1. First item
2. Second item
3. Third item

Unordered List
- First item
- Second item
- Third item

Code: `code`
Link: [title](https://www.example.com)

Note: Only the above syntax items will generate rich text in a task description.

Default false. If you have issues with XML errors, set this to true to resolve those.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due At. Ignores time.

You can use human readable dates like: "tomorrow" or "next week Tuesday". Cannot be used with Due On. Considers time.

Can only be set if the Assignee is also set.

This trigger works on Salesforce objects with less than 104,000 records. If the "Field Updated to" is specified, the limit applies to only the records with the value specified. Check how many records you have in your account by following the steps under Viewing Storage Usage. You can also setup a Zap with the New Outbound Message trigger to workaround this limit.

Pick which type of object you want to watch for changes on.

Select which campaign to add contact. If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

Select which campaign to add lead. If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

If using the Search for this field, click "Refresh Fields" below to make sure all fields are available to you.

Pick which type of object you want to create (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the lead you'd like to update. Use Custom Value to select a lead from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to update (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly)

Search for or select the record you'd like to update. Use Custom Value to select a record from a previous step. If using the Search, click "Refresh Fields" below to update the available input fields.

Pick which type of object you want to search for.

Pick which type of object you want to search for.

Enter a SOQL WHERE clause. See our help docs for Tips and Examples.

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