What does this automation do?
A message in a Slack channel is read by an agent that decides which of your existing automations should run, starts it, and reports back in the thread.
What can you do with it?
- Ask for an outcome in Slack instead of hunting for the right flow
- Let one agent choose and start the automation that fits
- Get the result posted back where the request was made
- Turn a pile of separate automations into one front door
The Steps
This automation runs in 4 steps:
- When Slack — New Message
- Then Taskade AI — Ask Agent ("Orchestration Lead")
- Then Taskade — Run Automation
- Then Slack — Send Channel Message
What makes this different from a Zapier-style flow?
The "Orchestration Lead" step is not a one-off model call. It is a Taskade AI agent that knows which automation owns each kind of request, remembers which flows resolved which requests, 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 with more automations than anyone can remember. A message in a Slack channel is read by an agent that decides which of your existing automations should run, starts it, and reports back in the thread.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Message" from Slack.
- Add the action "Ask Agent" from Taskade AI. Point it at an agent called "Orchestration Lead".
- Add the action "Run Automation" from Taskade.
- 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.
