Reply to Email
Send a reply in an existing Gmail thread.
Type
google.gmail.reply_emailListed only when a matching connected service is enabled.
Reply to Email sends a message on an existing Gmail thread. It loads the last non-draft message (or a specific Message ID), sets reply headers (In-Reply-To, References), and keeps the same threadId.
If To is empty, Reply uses From (or another party) on that message. Reply all includes the other To and Cc addresses except the connected mailbox. If Subject is empty, the subject becomes Re: plus the last subject (or stays as-is if it already starts with Re:).
Configure
| Setting | Description |
|---|---|
| Thread ID | Gmail thread id (required) |
| Message ID (optional) | Reply to this message instead of the last non-draft in the thread |
| Reply mode | Reply (default) or Reply all |
| Body | Reply body (required). Match Content type. Liquid supported |
| Subject (optional) | Override subject. Empty uses Re: on the last message |
| To (optional) | Override recipient. Empty uses the last message’s From / Reply-To |
| Cc (optional) | Carbon-copy addresses |
| Bcc (optional) | Blind carbon-copy addresses |
| Attachments (optional) | Workspace file(s) to attach |
| Content type | Plain text (default) or HTML |
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection |
| Out (source) | Continues after Gmail accepts the reply |
Pipe schema
The next block reads this on the data pipe (pipe.value):
| Key | Type | Description |
|---|---|---|
id | text | Gmail message id of the reply |
threadId | text | Same thread id |
labelIds | list | Labels on the sent reply |
Use case
- After Mail Received, reply with
args.message.threadIdwithout opening Mail Chat. - Keep a support row’s Gmail Thread value and reply later from a scheduled workflow.