What does this automation do?
An incident webhook calls an MCP tool for the configured context, then posts the result to the response channel and opens a task.
What can you do with it?
- Pull supporting context without switching between interfaces
- Post the returned details where responders are working
- Open a Taskade task to own the follow-up
The Steps
This automation runs in 4 steps:
- When HTTP — Webhook Received
- Then MCP Client — Call Tool
- Then Slack — Send Channel Message
- Then Taskade — Add Task
Who is this automation for?
Built for on-call teams gathering context as soon as an incident event arrives. An incident webhook calls an MCP tool for the configured context, then posts the result to the response channel and opens a task.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "Webhook Received" from HTTP.
- Add the action "Call Tool" from MCP Client.
- Add the action "Send Channel Message" from Slack.
- Add the action "Add Task" from Taskade.
- Enable the toggle in the top-right corner to activate the automation.
Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps for you.