What does this automation do?
An agent reads what the ticket actually asks for and sends it down the engineering path, the design path, or back for more detail.
What can you do with it?
- Sort mixed intake without a manual first-pass read
- Route by what the ticket means, not by the label someone picked
- Send incomplete tickets back before they reach a sprint
The Steps
This automation runs in 3 steps:
- When ClickUp — New Task
- Then Taskade AI — Ask an agent ("Intake Router")
- Then Branch — Engineering: Add Task, Assign Task · Design: Add Task · Needs more detail: Create Task Comment
What makes this different from a Zapier-style flow?
The "Intake Router" step is not a one-off model call. It is a Taskade AI agent that knows your teams, their areas and what a complete request looks like, remembers how similar tickets were routed 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 teams sharing one intake list across several functions. An agent reads what the ticket actually asks for and sends it down the engineering path, the design path, or back for more detail.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Task" from ClickUp.
- Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Intake Router".
- Add a Branch step: Branch — Engineering: Add Task, Assign Task · Design: Add Task · Needs more detail: Create Task 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.