What does this automation do?
When a ticket changes status, its whole comment history is pulled, condensed to what was decided, and filed as a task for whoever picks it up.
What can you do with it?
- Get the decision without reading the whole thread
- Carry the context forward when a ticket changes hands
- Keep the summary as a task rather than a fortieth comment
The Steps
This automation runs in 4 steps:
- When ClickUp — Task Status Updated
- Then ClickUp — Get Task Comments
- Then Taskade AI — Ask Agent ("Thread Reader")
- Then Taskade — Add Task
What makes this different from a Zapier-style flow?
The "Thread Reader" step is not a one-off model call. It is a Taskade AI agent that knows your project vocabulary and who the people in the thread are, remembers the decisions it has already summarized on this project, 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 anyone inheriting a ticket with forty comments on it. When a ticket changes status, its whole comment history is pulled, condensed to what was decided, and filed as a task for whoever picks it up.
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 the action "Get Task Comments" from ClickUp.
- Add the action "Ask Agent" from Taskade AI. Point it at an agent called "Thread Reader".
- 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.