What does this automation do?
Two days after a task is opened the flow wakes up, reads it, and forks — still open means an agent, an owner and a channel post; already handled means a quiet note.
What can you do with it?
- Escalate on day two automatically instead of at the weekly review
- Skip the escalation entirely when someone already dealt with it
- Keep the escalation rule identical whoever is on shift
The Steps
This automation runs in 4 steps:
- When Taskade — Task Added
- Then Delay — wait 2 days
- Then Taskade — Get Task
- Then Branch — Still open: Ask Agent, Assign Task, Send Channel Message · Already handled: Add Comment
What makes this different from a Zapier-style flow?
The "Escalation Desk" step is not a one-off model call. It is a Taskade AI agent that knows your escalation rules, SLAs and on-call owners, remembers what it escalated and how it ended, 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 support and operations teams where things quietly go stale. Two days after a task is opened the flow wakes up, reads it, and forks — still open means an agent, an owner and a channel post; already handled means a quiet note.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "Task Added" from Taskade.
- Add a Delay step: Delay — wait 2 days.
- Add the action "Get Task" from Taskade.
- Add a Branch step: Branch — Still open: Ask Agent, Assign Task, Send Channel Message · Already handled: Add Comment.
- 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.