Pipedream Asana → n8n

Q: Does n8n have a Asana node?

Yes. 5 of the 6 Pipedream Asana actions listed here map to a native n8n node; 1 map to n8n's HTTP Request node with the Asana credential.

Q: Will my Pipedream Asana connection move to n8n?

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Asana credential in n8n (type asanaApi) and select it on the converted nodes.

Q: Are Pipedream Asana triggers supported in n8n?

2 of the 2 Pipedream Asana event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

Q: What happens to code steps that call the Asana API?

Code steps keep working through a compatibility layer, and tokens read via this. .$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

6 Pipedream Asana actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: asana.

Actions

Pipedream action	n8n	Fit	Notes
asana-create-task	Asana task → create	Check output	n8n otherProperties for task create only offers assignee, assignee_status, completed, due_on, liked, notes, projects. If any unmapped prop is set (tags, followers, html_notes, due_at, start_on, parent, assignee_section, custom_fields), use the HTTP Request…
asana-update-task	Asana task → update	Check output	PD also sent 'workspace' in the PUT body, which Asana ignores. 'project' is a required PD prop but unused by run(). If due_at, start_on, html_notes, assignee_section or custom_fields are set, use an HTTP Request PUT…
asana-create-subtask	Asana subtask → create	Check output	Both call POST /tasks/{task_gid}/subtasks. PD also sent projects:<project>, which n8n subtask create cannot. If project/tags/followers/html_notes/due_at/start_on matter, use an HTTP Request POST https://app.asana.com/api/1.0/tasks/<task_gid>/subtasks with…
asana-add-task-to-section	Http Request	Check output	This uses the HTTP fallback on purpose. The native Asana task:move does the same POST /sections/{section}/addTask but has a REQUIRED projectId parameter (used only to load the section list) that PD does not have, and it lacks insert_before/insert_after. If…
asana-create-task-comment	Asana taskComment → add	Direct	Both POST /tasks/{gid}/stories. Workflows saved with versions <1.0.0 also stored workspace/project props, which can be ignored.
asana-search-tasks	Asana task → getAll	Check output	n8n getAll is GET /tasks with the same query params. completed_since/modified_since are reformatted via moment in the workflow timezone (same instant). The n8n task:search op (/workspaces/{gid}/tasks/search, premium only) is NOT the equivalent of this action.

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
asana-new-task	Asana Trigger {{prop:project}}	Check output	Name the n8n trigger node without spaces (the node refuses webhook URLs containing %20). workspace is used for the GET /webhooks existence check. PD dedupes by task gid, n8n does not.
asana-task-updated-in-project	Asana Trigger {{prop:project}}	Check output	Asana sends one event per changed field, so n8n will produce more executions than PD's debounced stream.

Credentials

Create a Asana credential in n8n (type asanaApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a Asana node?+

Yes. 5 of the 6 Pipedream Asana actions listed here map to a native n8n node; 1 map to n8n's HTTP Request node with the Asana credential.

Will my Pipedream Asana connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Asana credential in n8n (type asanaApi) and select it on the converted nodes.

Are Pipedream Asana triggers supported in n8n?+

2 of the 2 Pipedream Asana event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the Asana API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Calendly ClickUp Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini Google Sheets All apps →