Taskade Integrations

The public source-of-truth for Taskade actions & triggers across automation platforms — starting with the official Zapier integration, built entirely on the Taskade public API.

Building a Taskade integration for another platform (n8n, Activepieces, Make, Pipedream, or your own)? Everything here runs against the documented public API — copy freely. Live OpenAPI specs:

• v1 REST API: https://www.taskade.com/api/v1 — spec
• v2 Action API: https://www.taskade.com/api/v2 — spec

Packages

• packages/n8n-nodes-taskade — official n8n community node for Taskade, built in this repo

Zapier app capabilities

Type	Key	What it does
Trigger	task_due	Fires when a task is due (instant/webhook)
Action	create_task	Create a task — with due date, assignee; content > 2000 chars auto-chunks into sibling tasks
Action	complete_task	Mark a task complete, or reopen it
Action	update_task	Update a task's content
Action	delete_task	Delete a task
Action	move_task	Reorder/reparent a task within a project
Action	create_project	Create a project from Markdown
Action	create_project_from_template	Create a project from a template
Action	run_agent	Prompt a Taskade AI agent, get its response (v2 promptAgent)
Action	custom_api_call	Authenticated request to any Taskade API endpoint
Search	find_task	Find a task in a project by text
Search	find_project	Find a project by name

Hidden dropdown helpers (not user-facing): get_all_spaces, get_all_projects, get_all_blocks, get_all_assignable_members, get_all_tasks, get_all_project_templates.

Auth: OAuth2 (www.taskade.com/oauth2/*). The API also supports Personal Access Tokens (Authorization: Bearer tskdp_…) for other platforms.

Note: the task_due trigger currently uses Taskade-internal webhook routes. A public webhook-subscription API (POST /api/v2/subscribeWebhook) is in progress — once live, event triggers become portable to any platform.

Development

Prerequisites: Node ≥ 18, Yarn, Zapier CLI.

yarn install
yarn build        # tsc -> lib/
yarn test         # builds, then validates the app against Zapier's official schema

The test suite validates the full app definition with zapier-platform-schema's validateAppDefinition — the same check zapier validate runs — so schema regressions fail in CI before they reach a deploy.

Release

1. Bump version in package.json
2. yarn build && zapier build && zapier push

Deploying to the live Zapier app is a deliberate, manual step — never automatic on merge.

Logs

zapier logs
zapier logs --type=console
zapier logs --type=http --detailed

Roadmap

• Platform-agnostic operation manifest + per-platform codegen — the existing n8n node and future targets (Activepieces, Make, Pipedream) rendered from one source
• Portable event triggers once the public webhook-subscription API ships

See the Zapier Integration Guide for end-user docs.

Related repos

• Taskade Docs — source for docs.taskade.com
• Taskade MCP — official MCP server (@taskade/mcp-server on npm)
• Taskade — platform home, including the Genesis AI app builder