What does this automation do?
Most status changes are routine and stop here. A move into Blocked is read, explained, and emailed to the person who can unblock it.
What can you do with it?
- Hear about a blocker the day it happens, not at standup
- Get the reason with the alert instead of a status name
- Ignore the ninety percent of status changes that need nobody
The Steps
This automation runs in 4 steps:
- When ClickUp — Task Status Updated
- Then Filter — continue only when the status moved into Blocked
- Then Taskade AI — Ask an agent ("Blocker Analyst")
- Then Taskade — Send an email
What makes this different from a Zapier-style flow?
The "Blocker Analyst" step is not a one-off model call. It is a Taskade AI agent that knows your dependencies, your environments and who owns each system, remembers what unblocked the same kind of ticket before, 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 delivery managers and team leads. Most status changes are routine and stop here. A move into Blocked is read, explained, and emailed to the person who can unblock it.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "Task Status Updated" from ClickUp.
- Add a Filter step: Filter — continue only when the status moved into Blocked.
- Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Blocker Analyst".
- Add the action "Send an email" 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.