FeaturedPersonal Productivity#Gmail#Gmail Trigger#Support#Email Triage#Slack#OAuth2

Gmail Support Triage

Classify each new email in your Gmail Primary tab, alert Slack about urgent ones, and mark every handled email as read.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Gmail#Gmail Trigger#Support#Email Triage#Slack#OAuth2

Click a node to select it — same as the Heym editor; the panel shows its settings.

5 nodes · Free & source-available

Gmail Support Triage

Keep a shared Gmail support address under control without reading every message first. The Gmail Trigger watches the Primary tab of the connected Gmail or Google Workspace account, an LLM sorts each new email by topic and urgency, urgent ones go to Slack straight away, and Heym marks every email as read once its run has started, so the inbox shows only what nobody has looked at.

What this workflow does

  1. SupportGmail starts one run for each new email in the Primary tab. Promotions, Social and the other tabs are left out, and so are Spam and Trash.
  2. TriageEmail returns JSON with a category, an urgency, a one-line summary and a short suggestedReply.
  3. IsUrgent checks whether the urgency is high.
  4. AlertSupport posts urgent emails to your Slack channel with the sender, subject, summary and suggested reply.
  5. TriageResult returns the classification for every other email, so it shows in Execution History.

Setup

  1. Enable the Gmail API in your Google Cloud project, create a Web application OAuth client and register https://your-heym-domain/api/credentials/gmail/oauth/callback as an authorized redirect URI.
  2. In Heym Credentials, create Gmail (OAuth2), enter the Client ID and Client Secret, click Connect and sign in with the support mailbox. Select it on SupportGmail.
  3. To react only to mail sent to your support alias, add it under Only email sent to on SupportGmail, for example support@your-company.com. A Send mail as alias or a plus address works the same way.
  4. Select an LLM credential on TriageEmail and a Slack credential on AlertSupport.
  5. Keep After the run starts on Mark as read, or choose Mark as read and archive for an inbox-zero routine. Heym never deletes mail permanently; Delete moves it to Trash.

The first poll records where the mailbox is and does not replay older email. See the Gmail Trigger documentation for mailboxes, labels, aliases and the after-run actions.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3Press Cmd+V / Ctrl+V — nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime▲
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym