This repo currently powers our Zapier integration with a single action and trigger (New Task, Add Task). As part of our long-term automation roadmap, we want to:
-
Expand coverage to include more of Taskade's public API (projects, agents, automation).
-
Refactor code for reuse across platforms like Zapier, Make.com, n8n.io, Pipedream, etc.
-
Open source best practices so others can build their own Taskade integrations and contribute.
Goals
-
Modularize and abstract API request logic
-
Centralize auth + endpoint handling for multi-platform support
-
Build a shared integration schema layer (Zapier, Make.com, n8n-compatible)
-
Document clearly how to add new actions/triggers
-
Enable community forks, self-hosted agents, and 3rd-party marketplace support
🔁 Core Triggers (Poll or Webhook Based)
✅ Core Actions (Tasks Executed via API)
-
Create Project
-
Create Project from Template
-
Complete/Restore/Copy Project
-
Create Task
-
Complete/Uncomplete Task
-
Update Task
-
Assign User to Task
-
Set Due Date on Task
-
Add/Update Task Note
-
Create AI Agent
-
Add Project Knowledge to Agent
📦 Architecture Improvements
-
Create a reusable api-client.ts module for all outbound Taskade API calls
-
Use environment variables and standard OAuth2/bearer auth fallback
-
Define actions/, triggers/, and shared/ folders per Zapier conventions
-
Add metadata schema JSON for easy mapping into Make.com, n8n.io nodes
-
Implement unit tests with mock Taskade API calls
📖 Community Contribution Guide
🌍 Why This Matters
-
Many productivity platforms are becoming programmable.
-
Portability reduces lock-in to Zapier and expands access to automation.
-
Open-sourcing this unlocks developer and partner adoption of Taskade AI + automation.
-
Integrators (resellers, agencies, consultants) can embed Taskade actions in their own workflows.
🛠 Suggested Next Steps
-
Break apart monolithic Zapier logic into shared modules
-
Build a platform-agnostic schema for actions/triggers
-
Add CLI flags or build targets for Zapier, Make, n8n
-
Begin adding high-ROI API endpoints as Actions + Triggers
🧠 Resources
This repo currently powers our Zapier integration with a single action and trigger (New Task, Add Task). As part of our long-term automation roadmap, we want to:
Expand coverage to include more of Taskade's public API (projects, agents, automation).
Refactor code for reuse across platforms like Zapier, Make.com, n8n.io, Pipedream, etc.
Open source best practices so others can build their own Taskade integrations and contribute.
Goals
Modularize and abstract API request logic
Centralize auth + endpoint handling for multi-platform support
Build a shared integration schema layer (Zapier, Make.com, n8n-compatible)
Document clearly how to add new actions/triggers
Enable community forks, self-hosted agents, and 3rd-party marketplace support
🔁 Core Triggers (Poll or Webhook Based)
New Project Created
Project Marked Complete
Task Created
Task Completed
New Agent Created
Agent Conversation Started
✅ Core Actions (Tasks Executed via API)
Create Project
Create Project from Template
Complete/Restore/Copy Project
Create Task
Complete/Uncomplete Task
Update Task
Assign User to Task
Set Due Date on Task
Add/Update Task Note
Create AI Agent
Add Project Knowledge to Agent
📦 Architecture Improvements
Create a reusable
api-client.tsmodule for all outbound Taskade API callsUse environment variables and standard OAuth2/bearer auth fallback
Define
actions/,triggers/, andshared/folders per Zapier conventionsAdd metadata schema JSON for easy mapping into Make.com, n8n.io nodes
Implement unit tests with mock Taskade API calls
📖 Community Contribution Guide
Add a
CONTRIBUTING.mdwith:How to add new endpoints
How to test integrations locally (
zapier test)How to port to other platforms (Make.com JSON, n8n node format)
Example:
Create Taskacross all platforms🌍 Why This Matters
Many productivity platforms are becoming programmable.
Portability reduces lock-in to Zapier and expands access to automation.
Open-sourcing this unlocks developer and partner adoption of Taskade AI + automation.
Integrators (resellers, agencies, consultants) can embed Taskade actions in their own workflows.
🛠 Suggested Next Steps
Break apart monolithic Zapier logic into shared modules
Build a platform-agnostic schema for actions/triggers
Add CLI flags or build targets for Zapier, Make, n8n
Begin adding high-ROI API endpoints as Actions + Triggers
🧠 Resources
Taskade OpenAPI Spec (JSON)
Current GitHub Repo
Zapier Platform Docs
Make.com Custom App Docs
n8n Node Creation Guide