Pipedream Asana steps in n8n

Asana workflows on Pipedream turn requests into tasks (from a form, email or Slack) and react when tasks are created or completed. n8n has a native Asana node and a webhook Asana Trigger; the main difference is that the trigger is generic and you filter events yourself.

The n8n side

Asana node (n8n-nodes-base.asana):

Resource	Operations
Project	Create, Delete, Get, Get All, Update
Subtask	Create, Get All
Task	Create, Delete, Get, Get All, Move, Search, Update
Task Comment	Add, Remove
Task Project	Add, Remove
Task Tag	Add, Remove
User	Get, Get All

Asana Trigger: one event, New Asana event, for a Resource (project or task ID) in a Workspace. Asana sends batches of events (added, changed, removed) and n8n passes them on.

What maps where

Pipedream (app asana)	In n8n	Status
Create Task	Task → Create	manual
Update Task	Task → Update	manual
Create Subtask	Subtask → Create	manual
Create Task Comment	Task Comment → Add	manual
Search Tasks, Find Task by ID	Task → Search / Get	manual
Add Task To Section	Task → Move (to section)	manual
Create Project	Project → Create	manual
New Task (Instant), New Task Updated In Project (Instant)	Asana Trigger on the project + filter on action	manual
New Completed Task (Instant)	Asana Trigger + Task → Get + If completed	manual
New Task Assigned in Project (Instant), New Story Added To Project (Instant)	Asana Trigger + filter on change.field / resource type	manual

The converter has no Asana mapping yet. Each step arrives as a placeholder with its props in a comment, the trigger as a Manual Trigger naming the source, and the report lists the Asana credential.

Asana credentials in n8n

• Access token: My Settings → Apps → Developer apps → Personal access token.
• OAuth2: on n8n Cloud connect in the browser; self-hosted needs an app in the Asana developer console with n8n's redirect URL.

Filtering trigger events

Pipedream's sources were narrow (only completed tasks, only new stories). n8n's trigger gives you everything on the project. Typical filter after the trigger:

• New task: resource.resource_type = task and action = added.
• Completed: action = changed, change.field = completed, then Task → Get to confirm completed = true.

Typical migration: form request to task

Pipedream: Typeform New Submission → Asana Create Task (project, assignee, due date). n8n: Typeform Trigger → Asana → Task → Create (Workspace, Name, Projects, Assignee, Due On). Test with one submission and check the section the task lands in.

Asana migration pitfalls

• Rate limits. 150 requests per minute on free domains, 1,500 on paid, plus at most 50 concurrent GETs and 15 concurrent writes; 429 comes with Retry-After.
• Webhook heartbeats. Asana sends empty heartbeat events; filter out items with no events.
• Duplicate webhooks. Pipedream's sources registered their own webhooks. Disable the Pipedream workflows so both do not fire.
• GIDs are strings. Keep project and task IDs as text; long numbers lose precision in JavaScript.

How to move your Asana workflows

1. Export the workflows from Pipedream.
2. Upload on /convert; the free report lists every Asana step with its props.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Trello, ClickUp, monday.com.