Create Asana tasks from workflows

When feedback needs someone to follow up, a workflow can add an Asana task for it — in the project you choose, with a name, notes and a due date built from what Polzy knows. If the workflow also created a Polzy action, the action follows the task and closes itself once the task is completed. At the end of this guide you will have Asana connected and a workflow adding tasks.

Before you start

You need:

• A workspace on Business, and the Admin role in it.
• Integrations and Workflows switched on for the workspace, under Settings → General → What this workspace does.
• An Asana account that is a member of the projects you will use. Tasks are created as this account, so a dedicated one keeps them from being tied to one person.
• A personal access token for that account (below).

Create a personal access token

1. In Asana, open the developer console: your profile photo, then My Settings → Apps → Manage Developer Apps, or app.asana.com/0/my-apps.
2. Choose + Create new token and name it Polzy.
3. Choose Create token.
4. Copy the token. Asana shows it only once.

Asana explains tokens in Asana: Personal access token.

Connect Asana to Polzy

1. In the sidebar, under Automate, open Integrations and choose the Available tab.
2. Find Asana and choose Connect.
3. Paste the token into Personal access token.
4. Choose Test connection. Polzy answers Connected as and the account's name.
5. Choose Connect.

Integration

Connect Asana

Keys are encrypted and only used on your behalf.

1 of 1 required

Credentials

Personal access tokenRequired

In Asana, open the developer console (My settings → Apps → Developer apps) and create a personal access token.

Connected as Kenji Sato

Encrypted at restCancelTest connectionConnect

The token is stored encrypted. Once connected, Asana's row under Integrations offers Configure scope to replace the token, and Manage for its page.

Add a task from a workflow

1. Open Workflows and the workflow, or start a new one.
2. Under Connectors in Installed steps, drag Create an Asana task · Asana onto the canvas, after the step it should follow. A row with a lock means Asana is not connected yet, or needs attention.
3. Under Project, choose the project. The list shows the projects the token can see that are not archived — with the Asana workspace's name beside each when there are several.
4. Write the Task name. Type {{ to insert a value from the run, such as the action's title.
5. If you like, write Notes.
6. If you like, set Due in (days): the task is due that many days after the step runs, counted in your workspace's time zone.

Installed steps

Drag onto the canvas, or click to add

Connectors

Create a Jira issue · Jira

Create a Linear issue · Linear

Create an Asana task · Asana

Create an Asana task · AsanaConnector action

Connector

Asana

Action

Create an Asana task

Details

ProjectRequired

Customer follow-ups

Task nameRequired

Notes

Due in (days)

The step leaves the task's ID as {{connector.taskId}} and its address as {{connector.url}}. A Test run walks the workflow without adding the task; only a real run creates one. Workflows explains triggers and steps.

Close the action when the task is completed

When Create an Asana task runs after Create action item in the same workflow run, the task is linked to that action:

• Tracked in. The action's panel shows the task, linked to Asana, and whether it is open or completed.
• Closed by Asana. Polzy asks Asana about the task at most every 10 minutes. When it is completed, the action moves to Done.
• Status only. Comments and other changes stay in Asana. An action closed in Polzy first is not asked about again.

What Polzy sends to Asana

Only what the step says: the project, the task's name, its notes and its due date, with the values you insert. Nothing else about the answer or the person leaves Polzy. An anonymous answer has no person, so values such as the respondent's email are empty; what someone wrote is sent only once it has been read for safety. Single answers are not held back by the privacy floor, so think about who can read the project before you put people's own words in a task.

Troubleshooting

• Asana refused the credentials (401). The token is wrong, or was deleted. Make a new one, choose Configure scope on Asana's row under Integrations, paste it, and Save. A run that meets this marks Asana Needs attention.
• Asana refused the credentials (403). The account may not add tasks to that project. Add it to the project in Asana.
• Asana answered 404. The project was deleted, or the account is no longer a member.
• This step names no project or The task has no name. Fill in the step's Project and Task name.
• The Project list is a plain box, or misses a project. The token sees no projects, the project is archived, or it is in a workspace beyond the first ten the account belongs to. The list shows up to 100 projects per Asana workspace.
• The action does not close. The Asana step did not run after Create action item in the same run, the task is not completed, or the connection needs attention — checks pause until it is fixed.

Good to know

• One connection, every project. Each step picks its project from what the token can see.
• Who is the creator? The account the token belongs to.
• Can a step add the same task twice? No. A step that is run again after a crash reuses what it created the first time.

Useful links

• Asana: Personal access token