FeaturedPersonal Productivity#Gmail#Gmail Send#Gmail Trigger#Support#Auto-reply#OAuth2

Gmail Support Acknowledgement Replies

Answer each new support email from the same Gmail account within a minute, with a short summary of the request, and skip newsletters and no-reply senders.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Gmail#Gmail Send#Gmail Trigger#Support#Auto-reply#OAuth2

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

5 nodes · Free & source-available

Gmail Support Acknowledgement Replies

A customer who writes to support wants to know the message arrived and was understood. This workflow answers every new support email from the Gmail account it arrived in, with no SMTP server or App Password. The Gmail Trigger watches the Primary tab, an LLM restates the request in one sentence and writes a short reply, and Gmail Send sends it back to the sender as Re: the original subject. Newsletters, notifications and no-reply senders get no answer.

What this workflow does

  1. SupportGmail starts one run for each new email in the Primary tab of the connected Gmail or Google Workspace account.
  2. DraftAcknowledgement returns JSON: automated is true for newsletters, notifications, bounces and no-reply senders, summary restates the request, and replyHtml is a short HTML reply that quotes the summary and says when the team will answer.
  3. NeedsReply lets only email from a person through.
  4. SendAcknowledgement replies from the same account with Gmail Send. Set From to a Send mail as alias such as support@your-company.com to answer from it; the alias chips under the field come from the account.
  5. AcknowledgementResult returns the summary and Gmail's message id, so every reply 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 the same credential on SupportGmail and SendAcknowledgement: gmail.modify reads and sends.
  3. Select an LLM credential on DraftAcknowledgement and change the response time in its instructions to the one your team promises.
  4. Optionally list your support alias under Only email sent to on SupportGmail and as From on SendAcknowledgement.

Gmail sends only as the account or one of its verified Send mail as addresses; any other From fails the node before sending. See the Gmail Send documentation for every field.

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