What does this automation do?
React to a message and the whole thread is pulled, written up as an issue by an agent, filed, and the ticket link posted back into the channel.
What can you do with it?
- Capture the "this should be a ticket" moment where it happens
- File the issue with the thread’s context, not one line of it
- Close the loop by posting the ticket back to the people discussing it
The Steps
This automation runs in 5 steps:
- When Slack — New Reaction
- Then Slack — Fetch Channel Messages
- Then Taskade AI — Ask an agent ("Ticket Writer")
- Then Jira — Create Issue
- Then Slack — Send Channel Message
What makes this different from a Zapier-style flow?
The "Ticket Writer" step is not a one-off model call. It is a Taskade AI agent that knows your board, your components and how your team words an issue, remembers the threads it has already turned into tickets, 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 whose bugs are first reported in a channel. React to a message and the whole thread is pulled, written up as an issue by an agent, filed, and the ticket link posted back into the channel.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Reaction" from Slack.
- Add the action "Fetch Channel Messages" from Slack.
- Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Ticket Writer".
- Add the action "Create Issue" from Jira.
- Add the action "Send Channel Message" from Slack.
- 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.