What does this automation do?
Your monitoring posts an alert to the flow URL, and an agent that knows your services decides whether this is a wake-someone alert or a morning one.
What can you do with it?
- Accept alerts from any system that can post to a URL
- Wake someone only for the alerts that warrant it
- Queue the rest where they will be read, not lost
The Steps
This automation runs in 3 steps:
- When Webhook Received
- Then Taskade AI — Ask an agent ("Ops Watch")
- Then Branch — Page someone now: Send Channel Message, Send SMS, Add Task · Log it for the morning: Add Task
What makes this different from a Zapier-style flow?
The "Ops Watch" step is not a one-off model call. It is a Taskade AI agent that knows your service map, runbooks and past incidents, remembers which alerts turned out to be noise, 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 platform teams tired of paging on noise. Your monitoring posts an alert to the flow URL, and an agent that knows your services decides whether this is a wake-someone alert or a morning one.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the "Webhook Received" trigger.
- Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Ops Watch".
- Add a Branch step: Branch — Page someone now: Send Channel Message, Send SMS, Add Task · Log it for the morning: Add Task.
- 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.