What does this automation do?
An alert webhook wakes a response team — one agent assesses, one writes the customer update, one starts the postmortem — and posts to the channel.
What can you do with it?
- Get an assessment and a customer update in the first minute
- Start the postmortem while the incident is still live
- Keep incident handling identical whoever is on call
The Steps
This automation runs in 4 steps:
- When HTTP — Webhook Received
- Then Taskade AI — Ask an agent team ("Incident Room")
- Then Slack — Send Channel Message
- Then Taskade — Add Task
What makes this different from a Zapier-style flow?
The "Incident Room" step is not a one-off model call. It is a Taskade AI agent team — Responder, Comms Lead, Postmortem Writer — that knows your runbooks, service map and past incidents, remembers every incident it has worked, so every run builds on the last one instead of starting from an empty prompt.
A stateless "ask the model" step forgets everything the moment it returns. An agent keeps its knowledge and its memory between runs, carries its own tools, and can be handed work by other automations.
Who is this automation for?
Built for engineering and operations teams on call. An alert webhook wakes a response team — one agent assesses, one writes the customer update, one starts the postmortem — and posts to the channel.
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 "Ask an agent team" from Taskade AI. Point it at an agent called "Incident Room".
- 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, and the agent for you.