How do I approve email replies from Slack before they go out?
The built-in ways to bring Gmail into Slack or Google Chat share the email for discussion, and the reply is still written and sent from Gmail. Approving a drafted reply from chat takes a small system in between: it screens the email, posts the draft as a card, and sends one reply in the same thread when someone approves.
You know when a lead emails while you're between meetings? The reply waits until you're back at a desk, because a careful answer is hard to write on a phone. Approving a drafted reply from the chat you already have open is the usual fix, and it holds only if the handoff between Gmail and the chat holds. I built one and tested it on SignalNine's own inbox, and the tests below come from there.
The built-in options stop short of that. Slack's add-on for Gmail sends one email into a channel or a direct message. Google's Share in chat does the same for a Chat message, on work and school accounts. Neither help page describes answering the sender from chat, so the reply still happens in Gmail.
Inside Gmail, a delegate can send from your account and Gemini's Help me write can draft a reply, and in both cases whoever presses send is the approval. For a hold before sending, Google Workspace has admin quarantine, where outgoing mail that matches a compliance rule waits for an admin to release it.
The handoff
Seven steps sit between an email arriving and a reply going out, and the worst failures among them raise no error.
| Step | What does it | Where it breaks |
|---|---|---|
| Email arrives | Gmail, watched by the system | A follow-up sent to an address the system doesn't watch never arrives. |
| Screened | Plain rules, before any model call | With no screen, every newsletter costs a model call. Too strict a screen throws out a real lead. |
| Draft written | A model that first reads the earlier emails and the facts about the business | A draft from the last message alone misses what the lead already said, or promises a price nobody agreed. |
| Card in chat | Slack, Telegram or Google Chat | A card in a busy channel scrolls away, and if alerts share that chat, a broken chat can't report itself. |
| Approve, edit or reject | A named person, from the card | Anyone in the channel can press unless the system checks who pressed. |
| Sent once | The system, through Gmail, in the original thread | A second press or a retry sends a second email, and a reply sent as a new email lands outside the thread. |
| Logged | The system, at every step | Without a log, a dropped email looks the same as a handled one. |
Where it breaks
Double sends come first. People tap approve twice on a phone, or a workflow retries a failed step, and two copies of one reply look unprofessional. On SignalNine's own inbox on 2026-09-07, five approve presses in 2.2 seconds sent one email.
Wrong-thread replies come next. A reply that goes out as a new email, or from a different address than the one the lead wrote to, starts a second conversation, and the lead's next message can land where the system doesn't look. A draft that skips the earlier emails ignores what the lead already told you.
Junk is the cheap failure that adds up. If every email goes to a model first, each newsletter is a paid call. On my own inbox, junk and out-of-scope mail cost $0.00 on 2026-09-07, because the screen runs before any model call. The screen is meant to remove only obvious junk and leave the model to judge what's a lead, because a strict word list throws out the lead who phrases things differently.
Approvals that sit unseen are the failure nobody notices. Both n8n and Zapier let a wait expire: n8n can resume the workflow after a time limit, and Zapier's Skip and continue keeps the Zap running without a response. The step after the wait has to check for an approval before it sends, or an ignored card turns into an unapproved email.
The source-of-truth and dedupe rule
- The email thread is the record. The draft, the card and the approval point back to one conversation, and the reply goes out in that thread, from the address the lead wrote to.
- One approval sends one email. The first press moves the draft from ready to sending, so every later press finds nothing to send.
- One sendable draft per conversation. A new email on a conversation that already has a waiting card comes up as a warning that a reply is already waiting.
- Every press is recorded with who pressed it, including the ones that sent nothing.
In the inquiry desk I built, the rule of one sendable reply per conversation lives in the database, where a later edit to the workflow can't skip it, and the first press claims the draft before anything sends.
What stays human
The approval stays human, and so does anything the draft can't know. There, the draft has guardrails, like never making up a price, and a risky email, like an NDA request, gets flagged for a person to decide. A flagged draft takes a second press, on a question that names the flag.
Replying to the card revises the draft. Who may approve is a short list of named people you set once. n8n's Slack approvals can be limited that way, and anyone else who clicks gets a private notice while the workflow keeps waiting.
What I'd pick, per situation
| If you | I'd pick |
|---|---|
| Answer every lead yourself, mostly from Gmail | Stay in Gmail. Let Gemini draft if it helps, and your press on send is the approval. |
| Want a colleague's view before replying | Share the email into Slack or Google Chat, agree the answer there, and name one person who replies from Gmail. |
| Want to approve drafted replies from your phone | A chat approval loop with a screen, a draft, a card, one send per approval and a log. I set mine up on Telegram because it's always on my phone. |
| Already pay for Zapier and want a yes or no on each reply | Zapier's Human in the Loop, listed on its Professional, Team and Enterprise plans. It notifies by email or Slack, and a reviewer can edit the content. Each reviewer needs a Zapier account with the Zap shared to them. |
| Want the approval inside Slack, Telegram or Google Chat, with a record of who approved | A workflow in n8n, which can send a message to any of the three and wait for the response. In Slack it can record who responded and limit who may approve. |
| Need a certain kind of outgoing mail held for review across the company | Google Workspace admin quarantine. An admin releases each message, which suits compliance rules and slows everyday replies. |
A system in between is one more thing to look after. Mine logs every step, and its cards and alerts share one Telegram chat. When that chat broke, runs stalled and nothing reported it, which is the failure the table warns about.
Questions
Can I reply to an email from Slack?
Not with the add-ons as Slack and Google describe them. Both help pages cover sending an email into chat, and neither covers answering the sender from there. Replying from chat takes a workflow in between, built in a tool like n8n or Zapier.
Does Gmail have an approval step before a reply sends?
Not for everyday replies. A delegate can send from your account and Gemini can draft a reply, and in both cases whoever presses send is the approval. Workspace admins can hold outgoing mail that matches a compliance rule in quarantine until an admin releases it.
What happens if nobody approves the card?
That depends on how the wait ends. n8n can resume the workflow after a time limit, and Zapier lets you choose between ending the run and continuing without a response. Either way, the send step should check for an approval first, so an expired card sends nothing and goes back to a person.
Which chat app should approvals go to?
The one the approver already watches on their phone. Slack suits a team that works there all day, Google Chat suits a team on Google Workspace, and Telegram suits one person approving on the go.
Can two people approve the same reply?
Two people can press, and one email goes out. The first press locks the draft, and every press after it, from anyone, finds nothing to send. Keep the list of approvers short and record who pressed, so you can see who sent what.
- Slack Help Center, Send emails to Slack: a channel email address, the Gmail and Outlook add-ons, and forwarding to Slackbot, each sending an email into SlackREAD
- Google Workspace Marketplace, Slack for Gmail: shares an email, with a message and attachments, into a Slack channel or direct messageREAD
- Google Chat Help, Share in Chat from Gmail: work and school accounts on a computer share an email in a Chat messageREAD
- Gmail Help, Delegate and collaborate on email: a delegate can read, send and delete mail, and their address appears on what they sendREAD
- Gmail Help, Draft emails with Gemini in Gmail: Help me write drafts and refines a reply in the compose windowREAD
- Google Workspace Admin Help, Set up email quarantine: admins can hold incoming and outgoing mail that matches a rule until it's releasedREAD
- n8n docs, Approvals in Slack: buttons that record who responded, and a list of users allowed to approve while anyone else gets a private noticeREAD
- n8n docs, Telegram message operations: Send and Wait for Response, with approval buttons and a wait limit after which the workflow resumesREAD
- n8n docs, Google Chat integration: a Send and Wait for Response operationREAD
- Zapier Help, Request approval with Human in the Loop: approve, decline or edit, notices by email or Slack, Skip and continue or End run on timeout, on Professional, Team and Enterprise plans, and each reviewer needs a Zapier account with the Zap shared to themREAD
Related
- Human-in-the-loop approvalWhat human-in-the-loop approval means in an automation, which steps should wait for a person, and how an approval card makes sure an email sends once.
- Speed to leadSpeed to lead is the time between a lead reaching you and a real reply going back. Why it matters, an example, and how a system shortens it.
- Send-onceSend-once means one approval sends one email, however many times the button gets pressed. Why duplicates happen and how a system keeps the rule.
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- The lead-response bottleneck: how fast to answer a new leadHow fast to answer a new lead, why a slow reply hands the decision to someone else, and a system that drafts from your rules for a person to approve.
- How do I stop website form duplicates in HubSpot?Where the handoff from your website form to HubSpot makes duplicates or loses leads, which field is the key, what stays with a person, and what I'd pick.
- What do slow replies to leads cost you?Multiply your leads, the value of a won client, your close rate and your own estimate of leads lost to slow replies to see the revenue at risk.