Email

Send email via Gmail or Outlook with subject, HTML body, and new vs reply threading.

The Email action sends an outbound email on PlatformType.email (Gmail or Outlook behind one mailbox channel). Use it for automation replies and follow-ups in the same inbox thread model as the Pingmee email composer.

When to use

Reply to an inbound email conversation from a bot.
Start a new email thread (compose-style) from a workflow.
Send a follow-up that continues a prior Email node’s thread.

Configuration

Field	What it does	When to use
Send from	Mailbox platform the agent can access (`emailFromPlatformId` / workflow platform).	Always — pick which connected mailbox sends.
Send as	`New email` or `Reply to thread` (`emailSendMode`).	New starts a thread (`forceNewThread`). Reply continues the conversation thread or a bound upstream `threadId`.
Thread (reply mode)	Bind `emailReplyThreadId` to an upstream Email node’s `threadId` output.	When a later Email node must reply to a specific earlier send. Leave empty to use the current conversation thread.
Subject	Email subject; use Add Variable for `{{n}}` slots bound like the body.	Required clarity for new threads. Optional on reply (empty keeps `Re: …` threading).
Body	HTML source with preview; `{{n}}` placeholders bind to workflow variables.	Always — rich email content.
Description	Optional canvas note.	Team documentation.

New vs reply

New email — does not attach In-Reply-To / prior conversation headers. Use a clear subject.
Reply to thread — EmailManager attaches reply headers from the conversation or from the bound upstream threadId / rfcMessageId.

Runtime outputs

After a successful send, the Email node execution output exposes:

threadId
rfcMessageId
message_generated_id

Downstream Email nodes can bind Thread to threadId for follow-ups.

Variables

Subject and body support numbered placeholders via Add Variable / the body insert control. Bind each slot from upstream nodes. See Variables.

Flow behavior

Input: Conversation context (mailbox + customer / thread key).
Output: Default edge to the next node. Wait-for-response is off by default for email.
Platform: Not LoginPlatform.email (user login) and not a CRM contact email field.