n8n: publish n8n-nodes-taskade to npm + submit for n8n Cloud verification

[johnxie]

The n8n community node shipped in #16 (packages/n8n-nodes-taskade/) — this tracks the path from merged code to n8n users.

Status

Node code	✅ Merged (#16) — Task (7 ops), Project (3 ops), AI Agent (Prompt via v2 promptAgent), usableAsTool for n8n AI agents
Verified-node compliance	✅ Zero runtime deps · MIT · keyword n8n-community-node-package · provenance publish workflow (publish-n8n.yml)
npm name n8n-nodes-taskade	✅ Verified free — unclaimed until step 2 below

Remaining steps (in order)

• 1. Add NPM_TOKEN repo secret — npmjs.com → Access Tokens → granular token with publish scope (maintainer task)
• 2. Swap the placeholder icon (nodes/Taskade/taskade.svg) for the official Taskade brand SVG — required before verification submission
• 3. Publish: git tag n8n-v0.1.0 && git push --tags → the workflow publishes to npm with provenance (mandatory for verified nodes since 2026-05-01)
• 4. Smoke-test install on a self-hosted n8n: Settings → Community Nodes → Install → n8n-nodes-taskade (credential test hits GET /api/v1/workspaces with a tskdp_ Personal Access Token)
• 5. Submit for verification at the n8n Creator Portal → verified status surfaces the node in the panel on n8n Cloud for all users + the n8n.io integrations directory

Out of scope (tracked separately)

• Trigger node (e.g. Task Due) — blocked on Taskade's public webhook-subscription API (in review); the action node ships without it by design
• Additional AI-agent actions (create/update agent, knowledge) — tracked in Add Missing AI Agent + Automation Actions and Triggers for Zapier, Make.com, n8n, and Beyond #10

Contributing

PRs welcome against packages/n8n-nodes-taskade/ in this repo. npm install && npm run build inside the package; n8n's node-building docs apply.

[johnxie]

cc @deanzaka @xw-2307 something on backlog for some time to consider