These guides show how to build on Taskade. Get events, embed agents, move apps, call the API from TypeScript, and run agents on their own.
Page type: Concept. Use it to pick the page that fits your task.
Overview
The API reference defines each call. These guides show how the parts of one workspace work together.
MEMORY INTELLIGENCE EXECUTION
────── ──────────── ─────────
Projects Agents Automations
Tasks Agent knowledge Webhooks out
Media Long-term memory Bundles in/out
Long-term memory Frontier AI models Published apps
│ │ │
└────────────────────┴──────────────────────┘
│
one workspace, one token
What each guide covers
Find your question in the middle column, then open the guide.
| Guide | Answers | Page type |
|---|---|---|
| Webhooks | How do I get told when something changes? | How-to |
| Bundles & App Kits | How do I move a whole app or workspace somewhere else? | How-to |
| Embed a Public AI Agent | How do I add an agent to my website? | How-to |
| TypeScript SDK | How do I call the API from TypeScript without an SDK install? | How-to |
| SDK Cookbook | What do production integration patterns look like? | How-to |
| Long-Term Memory | Where does an agent's memory live, and can I edit it? | Concept |
| Autonomous Agents | How do agents run work without a person in the loop? | Concept |
Webhook events
Taskade sends these events to a registered webhook. Registration needs the Pro plan or above.
| Event | Fires when |
|---|---|
task.due |
A task reaches its due date |
task.assigned |
A task is assigned to someone |
comment.created |
A comment is added |
project.created |
A project is created |
project.assigned |
A project is assigned |
project.joined |
Someone joins a project |
Taskade signs each delivery with HMAC-SHA256 and sends three headers: X-Taskade-Signature (the raw body), X-Taskade-Timestamp (unix seconds), and X-Taskade-Signature-V2 (<timestamp>.<raw body>). Check X-Taskade-Signature-V2, and reject a timestamp more than 5 minutes old. A copy that arrives inside those 5 minutes still passes, so skip a delivery that you already processed. See Validate delivery signatures.
If Taskade cannot make the signature, it skips the delivery. Taskade never sends an unsigned delivery.
Important: The payload has no event-name envelope. Find the event from the payload shape. Branch on required fields, not on a type field that does not exist.
Next steps
- Quickstart: make your first API call.
- TypeScript SDK: call the API from TypeScript with
fetch. - Webhooks: get an event when your data changes.
- Autonomous Agents: run agents from automations and teams.
- Embed a Public AI Agent: put an agent on your website.