Asana n8n integrationAutomate Asana with n8n.

Adds a new project to an Asana workspace and returns its project ID, ready to receive tasks later in the same run.

• Name: the project name, often built from an expression such as {{ $json.company }} so every new account gets its own board.
• Workspace Name or ID: the workspace to create the project in, chosen from the dropdown or passed as an ID through an expression.
• Additional Fields: four optional extras, including Privacy Setting (private, private_to_team, public_to_workspace), Due On in YYYY-MM-DD format, Notes and Color.

Removes a project from Asana. Only one identifier is asked for, which is why this operation usually sits at the end of a cleanup branch rather than in the middle of a flow.

• Project ID: the project to delete. Nothing else is requested, so the safety check belongs upstream, in an IF node that confirms you are pointing at the disposable board.

Reads one project and returns its fields. This is how a workflow checks a name, a set of notes or a due date before deciding what to do next.

• Project ID: the project to read, commonly taken from the trigger with {{ $json.resource }} or from an earlier list operation.

Lists the projects of a workspace. It earns its place when the workflow knows the workspace but not yet the ID of the board it needs to work on.

• Workspace Name or ID: required, the workspace to list projects from.
• Return All: on, n8n walks the API pages and brings back every project; off, it stops at the number set in Limit.
• Additional Fields: Archived narrows the answer to projects whose archived field matches, and Teams Name or ID restricts it to one team.

Changes an existing project without touching its tasks. Worth noting: the workspace is required here on top of the ID, which is not the case for the read operations.

• Workspace Name or ID and Project ID: both required to target the project.
• Update Fields: seven fields live here, including Name, Notes, Owner, Due On, Color, Privacy Setting and Team Name or ID. Leave the collection empty and the call changes nothing at all.

Hangs a subtask under an existing task, so a checklist lives inside the parent instead of crowding the project view.

• Parent Task ID and Name: the task to operate on, and the name of the subtask to create.
• Additional Fields: seven options, among them Assignee Name or ID, Due On, Notes, Completed and Assignee Status (inbox, today, upcoming, later), which only works if an assignee is set.

Returns the subtasks attached to one parent task. The natural use is counting what is still open before letting a workflow close the parent.

• Parent Task ID: the task whose subtasks you want.
• Return All and Limit: the usual pair, all the subtasks or a capped number of them.
• Options: Field Names or IDs chooses the fields to return, which keeps the payload small, and Pretty asks Asana for readable output.

The busiest operation of the node. It creates a task in a workspace and returns the task ID that the comment, tag and project operations then reuse.

• Workspace Name or ID and Name: where the task goes, and what it is called.
• Additional Fields: eight options, including Assignee Name or ID, Due On, Notes, Project Names or IDs and Completed. Filing the task at creation time saves a second call.

Erases a task for good. There is no undo on the n8n side, so this one belongs behind a filter that has already confirmed the target.

• Task ID: the ID of the task to delete, usually carried over from a search or a list operation rather than typed in by hand.

Fetches a single task with its fields. Plenty of workflows call it right after the trigger, to turn a bare resource ID into something a human message can use.

• Task ID: the ID of the task to get the data of, typically {{ $json.resource }} when the value comes from the trigger.

No parameter is required here, and that is exactly the trap: with nothing set, the call reaches far wider than anyone intended.

• Return All and Limit: every match, or a capped number.
• Filters: eight of them, including Project Name or ID, Section Name or ID, Completed Since and Modified Since. Two are linked: Assignee Name or ID requires Workspace Name or ID, and the reverse is true as well.

Sends a task into a section of a project. That is how a card changes column on a board without any of its other fields being rewritten.

• Task ID, Project Name or ID and Section Name or ID: all three are required. The section list is drawn from the project you picked, so choose the project first.

Looks for tasks inside one workspace using text. Different from the list operation: here Asana matches the words in the name or in the notes.

• Workspace Name or ID: required, the workspace the search runs in.
• Filters: Text is the string to look for in name or notes, and Completed keeps or excludes tasks already marked done.

Edits a task in place. Only the ID is required, and everything you actually want to change sits in the optional collection.

• Task ID: the task to update the data of.
• Additional Fields: eight fields, including Completed, Name for the new name of the task, Due On, Assignee Name or ID, Notes and Project Names or IDs.

Posts a comment on a task. It is the cheapest way to leave an audit trail where the work lives, rather than in a log nobody opens.

• Task ID and Text: the task to comment on, and the plain text of the comment.
• Is Text HTML: tells the node whether the body is HTML or simple text.
• Additional Fields: Pinned keeps the comment at the top of the thread.

Deletes one comment from a thread. Watch the identifier it expects: the comment ID, not the task ID, so keep the value returned when the comment was added.

• Comment ID: the ID of the comment to be removed. Storing it in the same run, or in a small table, is what makes the cleanup possible later.

Files an existing task into a project without creating anything new. A task can belong to several projects at the same time in Asana, which is what makes this useful.

• Task ID and Project Name or ID: the task to file, and where it goes.
• Additional Fields: Insert After and Insert Before take a task in the project to position against, and Section drops the task at the bottom of a section.

Pulls a task out of a project while the task itself stays alive in the workspace. Nothing is deleted, only the link between the two.

• Task ID and Project Name or ID: the task, and the project it should leave.

Puts a tag on a task. In Asana, tags are how you filter across projects, which a project field alone cannot do.

• Task ID: the task to add the tag to.
• Tags Name or ID: the tag to apply, chosen from the list or given as an ID through an expression.

The mirror operation: it strips a tag off a task. Same two identifiers, opposite effect on the filtered views.

• Task ID and Tags Name or ID: the task, and the tag that should come off.

Returns one Asana user. The identifier it accepts is unusually flexible, which saves a lookup in most workflows.

• User ID: an email address, the globally unique identifier for the user, or the keyword me to mean the account behind the credential making the request.

Lists the members of a workspace with their names and IDs. That list is what lets a workflow assign work without any identifier written in hard.

• Workspace Name or ID: required, the workspace to get users in.