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.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Filter to checkins that change one or more files under the specified path (it should start with $/[Project]).

String that must be found within the comment.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Only trigger if this field was changed by the update to the work item.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project where work item will be created.

Work item type.

Work item title.

The area of the product with which this work item is associated.

The iteration within which this work item will be associated.

The person currently owning the work item.

Work item description.

API docs for Google Forms are located here https://developers.google.com/forms/api/reference/rest

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.

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.

Build definition to trigger on.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Project containing the build definition.

Build definition to trigger a new build on.

Must be a project administrator for the specified project in order to create a Zap.

A specific work item number (for example, "123") or a string containing a work item number in the format "#123" (for example, "Link to #123 please").

URL of the link to be added to the work item.

Comment for the link. This comment is associated with the link, and is not added as a comment on the work item itself.