| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
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:
| 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.
Prerequisites: Node ≥ 18, Yarn, Zapier CLI.
yarn install
yarn build # tsc -> lib/
yarn test # builds, then validates the app against Zapier's official schemaThe 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.
Deploying to the live Zapier app is a deliberate, manual step — never automatic on merge.
zapier logs
zapier logs --type=console
zapier logs --type=http --detailedSee the Zapier Integration Guide for end-user docs.
| Back | FazBrowse Home | New Git URL |