Eight Asana steps work with tasks and projects:
- Asana · Create a task — Adds a task to a project, or a subtask under a task.
- Asana · Update a task — Changes a task's name, notes, assignee, due date or custom fields.
- Asana · Complete a task — Marks a task complete.
- Asana · Add a comment — Comments on a task.
- Asana · Find tasks — A project's tasks, or a person's, by whether they are done and when they changed.
- Asana · Add a task to a project — Puts a task in another project, in a section if you choose one.
- Asana · Attach a file — Attaches a file from an earlier step to a task.
- Asana · Create a project — A new project in a team, blank or from a template.
Every step except Find tasks is tagged Changes data.
Who can do this
Workspace Admins and Editors, on every plan. Viewers see the steps' settings but cannot change them.
Before you start
An Asana connection in this workspace — see Connect Asana.
Steps
Create a task:
- Select + where the step should go. In the step picker, open Apps, select Asana, then Create a task. Or search Asana.
- In Connection, choose your Asana connection.
- In Workspace, choose the Asana workspace — Consulace · Organisation.
- In Project, choose the project — Client onboarding. Empty: the task is the assignee's own, in no project. Sections and custom fields need one.
- In Name, type the task's name — Onboard Northwind Logistics.
- Optional:
- Notes — the task's description.
- Assignee — someone in the workspace, Asha Raghunathan · asha@consulace.com. Or an email from an earlier step.
- Due — A day, or a day and a time — 2026-10-09T11:30:00Z.
- Section — one of the project's sections.
- Tags — Separate several with commas. Tags the workspace does not have yet are made.
- Custom fields — the project's own fields, each with its type: text, number, choice, choices, date or people. Read from the project. A choice by its option's name, several separated with commas; people by email. Only those you fill in are set.
- Parent task — Only to make a subtask: the parent task's id or address.
- Followers — Emails or user ids, separated with commas.
- Select Run this step to try it. This adds a real task.
Update a task:
- In Task, the task's id — The task's id or address. Usually the
idfrom the step that created or found it. - Fill in only what should change — Name (Empty fields are left as they are.), Notes, Assignee, Due.
- To pick the assignee from a list, choose the Workspace first — Only to choose the assignee or project from a list.
- To set custom fields, choose the Project — Only to set custom fields — they are the project's own. — then fill them in under Custom fields. Read from the project. Only those you fill in change.
Complete a task, Add a comment, Attach a file:
- In Task, the task's id or address.
- For Add a comment, type the Comment — Kickoff moved to Tuesday.
- For Attach a file, choose the File — A file from an earlier step. — and optionally a Name — Optional — the file's own name otherwise.
Find tasks:
- Choose the Workspace.
- Choose a Project, an Assignee (Or an email, or me.), or both — A project, an assignee, or both.
- Under Show, choose All (the default), Not done or Done.
- Optional: in Changed since, a date — 2026-10-01.
- In Most tasks, how many at most — Up to 1,000. It starts at 100.
Add a task to a project:
- In Task, the task's id or address.
- Choose the Workspace and the Project — and a Section, to place it there.
Create a project:
- Choose the Workspace, and in Team the team it belongs to — An organisation needs one; a plain workspace has none.
- Type the project's Name — Northwind Logistics onboarding — and optional Notes.
- Optional: in Template, a project template — Optional — a blank project otherwise.
Every list offers Use a value above it, to give an id or email from an earlier step instead; Choose from the list goes back.
Output
| Step | What it gives |
|---|---|
| Create a task, Update a task, Complete a task, Add a task to a project | The task — id, name, notes, url, assignee, assigneeEmail, dueDate, completed, completedAt, createdAt, projects, section, tags, and each custom field by its name. |
| Find tasks | count, tasks (each with the keys above) and first. |
| Add a comment | The comment's id, taskId and text. |
| Attach a file | The attachment's id, name, url and taskId. |
| Create a project | The project's id, name and url. |
dueDate is a day — 2026-10-09 — or a time in UTC when the task has one. projects and tags are lists of names. A custom field comes out by its type: a number as a number, a choice by its name, several choices or people as lists of names.
Good to know
- Find tasks gives one item, with
count, the list oftasksand thefirst. When nothing matches, the run goes down When nothing is found instead, withfoundset to false — see When a Find step finds nothing. - Asana finds tasks by project or by assignee. With both, Bizomate takes the project's tasks and keeps the assignee's.
- Custom fields come from the project. After you add one in Asana, select Refresh on Custom fields to see it. A formula field is Asana's to work out, and is not offered.
- A task can be in several projects. Add a task to a project adds it to another without taking it out of the first.
- Completing is not deleting. Update a task cannot mark a task incomplete again — do that in Asana.
- A project from a template is made at once, and Asana fills it from the template in the background — its tasks may take a few seconds to appear.
- Each item runs the step once. Ten items add ten tasks.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Task “…” is not an Asana id — the long number in its address. | Task came out as something else. | Check the value it reads — an id, or a task's address. |
| Nothing to change — give a name, notes, an assignee, a due date or a custom field. | Update a task has nothing filled in. | Fill in what should change. |
| Choose the project the section is in. | A Section is chosen without a Project. | Choose the project. |
| Choose the project — custom fields are the project's own. | Custom fields are filled in with no Project. | Choose the project. |
| Choose a project or an assignee — Asana finds tasks by one of them. | Find tasks has neither. | Choose one. |
| Due “next week” is not a date — 2026-10-09, or 2026-10-09T11:30:00Z with a time. | Due is not a date. | Give a date, or a date and time. |
| Changed since “…” is not a date — 2026-10-01, or 2026-10-01T09:00:00Z. | Changed since is not a date. | Give a date. |
| Priority has no option “Urgent”. Its options: High, Medium, Low. | The value is not one of the field's options. | Use one of the options it names. |
| The project has no custom field named “Stage”. Refresh the fields and choose again. | The field was renamed or removed in Asana. | Select Refresh on Custom fields. |
| Nothing to pick — "This project has no sections. Leave Section empty, or add one in Asana." | The project has no sections. | Leave Section empty. |
| "Asana refused: Not Authorized. Check the connection's details on Connections." | The token was deleted. | Make a new token and select Replace token on the connection. |
| "Asana refused: …" | The account cannot reach that project or task, or Asana would not take a value — an assignee outside the workspace, say. Asana's own words follow. | Fix what it names. |
| "Could not reach Asana: …" or "Asana did not answer within 30 seconds." | Asana could not be reached, or was asked too often. | The step can try again — see Make a step try again when it fails. |