What does this automation do?
Inbound support mail is split three ways at the door — an outage wakes an agent and the channel, a billing question gets an owner, and everything else is filed.
What can you do with it?
- Treat an outage differently from a password reset, automatically
- Give billing questions a named owner the moment they arrive
- Keep the routine mail out of the escalation path entirely
The Steps
This automation runs in 2 steps:
- When Gmail — New Email
- Then Branch — Outage or data loss: Ask Agent, Send Channel Message, Add Task · Billing question: Add Task, Assign Task · Everything else: Add Task
What makes this different from a Zapier-style flow?
The "Support Triage" step is not a one-off model call. It is a Taskade AI agent that knows your help center, SLAs and past incidents, remembers every ticket it has already triaged, 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 support teams working one shared inbox for very different problems. Inbound support mail is split three ways at the door — an outage wakes an agent and the channel, a billing question gets an owner, and everything else is filed.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Email" from Gmail.
- Add a Branch step: Branch — Outage or data loss: Ask Agent, Send Channel Message, Add Task · Billing question: Add Task, Assign Task · Everything else: Add Task.
- 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.