Overview
Outgoing webhooks let Taskade tell your own tools when something happens. The moment a comment is posted, a task is assigned, or a project changes, Taskade sends a signed message straight to a web address you choose.
TL;DR: Turn on outgoing webhooks in Settings, API and Taskade pushes a signed message to your own service whenever a comment is posted, a task is assigned, or a project is created, updated, or removed. This is outbound (Taskade to your tool). To go the other way and trigger an automation from an outside event, use incoming webhooks instead.
This is the outbound direction. Taskade is the sender, and your tool is the listener. For a no-setup version of the same idea inside Taskade, you can also forward events with an automation.
See How an Event Travels
Picture a single event leaving Taskade and arriving at your tool. Something happens in your workspace, Taskade signs a small message, and your service receives it and reacts.
The whole trip takes a moment. Your tool does not have to ask Taskade for updates. Taskade comes to it.
Set Up an Outgoing Webhook
Open Settings, then API, and find the Outgoing Webhooks panel. Paste the web address where your tool listens, pick the events you care about, and save. Taskade gives you a signing secret so your service can confirm each message is genuinely from you.
┌────────────────────────────────────────────────────────────────┐
│ Settings › API › Outgoing Webhooks │
├────────────────────────────────────────────────────────────────┤
│ Endpoint URL │
│ [ https://your-tool.com/hooks/taskade ] │
│ │
│ Send an event when... │
│ [x] Comment posted │
│ [x] Task assigned │
│ [x] Project created │
│ [x] Project updated │
│ [ ] Project removed │
│ │
│ Signing secret whsec_•••••••••••••••• Copy · Rotate │
│ [ Save webhook ] │
└────────────────────────────────────────────────────────────────┘
Tick only the events you need. Your tool starts receiving messages right away, with no polling and no extra software in between.
Pick the Events You Want
Choose which moments send a message. Each event fires the instant the action happens in your workspace, so your tool stays in step with Taskade.
| Event | When it fires |
|---|---|
| Comment posted | Someone adds a comment on a task or project |
| Task assigned | A task is handed to a teammate |
| Project created | A new project is added to the workspace |
| Project updated | A project's details or contents change |
| Project removed | A project is deleted from the workspace |
These five cover the project lifecycle. Pair "task assigned" with a chat app to ping the right person, or use "project created" to spin up a matching record in your own system.
Trust Every Message with the Signing Secret
Each outgoing webhook carries a signature built from your signing secret. Your service checks that signature before it acts. If it matches, the message is genuinely from your workspace. If it does not, your tool can safely ignore it.
- Keep the signing secret private, the same way you would a password.
- Have your service confirm the signature on every message before acting.
- Rotate the secret any time from the same panel if you ever need a fresh one.
A "signed" message simply means your tool can trust the request really came from you, with nothing for you to build by hand.
Outgoing vs. Incoming Webhooks
Taskade supports webhooks in both directions, and it helps to keep them straight. Outgoing webhooks send news out. Incoming webhooks bring news in to start an automation.
| Outgoing webhooks (this guide) | Incoming webhooks | |
|---|---|---|
| Direction | Taskade to your tool | Your tool to Taskade |
| Taskade's role | Sender | Receiver |
| What starts it | A comment, assignment, or project change | A request from an outside service |
| What happens next | Your service receives and acts | An automation runs in Taskade |
| Where to set it up | Settings, API | Inside an automation |
Use outgoing webhooks to tell the rest of your stack what just happened in Taskade. Use incoming webhooks to let the rest of your stack kick off work inside Taskade. Many teams wire up both for a clean round trip.
Related guides
- Incoming Webhooks: Let an outside event trigger an automation inside Taskade
- Taskade Developer API: Read and write your workspace with the REST API and tokens
- Public API Reference: Browse every endpoint for workspaces, projects, and agents
- Hosted MCP Server: Give AI assistants live, secure access to your workspace
- Automations Execution: Chain triggers and actions to move work automatically