Skip to main content
The email output node sends workflow results to one or more email addresses. It is a terminal node. Nothing connects after it. Use it to deliver extracted data, reports, or notifications directly to inboxes.

​
Configuration

​
Body template rendering

The body template supports your own HTML markup alongside {{...}} placeholders. When the email renders, values substituted from documents and step outputs are HTML-encoded: any markup inside a document’s extracted data appears in the email as literal text rather than being rendered. Only the markup you write in the template itself renders as HTML. Every email also includes an automatically generated plain-text version alongside the HTML, which improves deliverability and accessibility.

​
Retries and re-sends

Each send is recorded in the same delivery ledger the Callback and connector nodes use, before the message goes out. A platform retry of a step whose email already left does not send it again, and retrying or re-running a run whose scope includes an email that already went out is refused until you confirm the re-send.
An email cannot be checked at the destination the way a connector record can. If an attempt loses its outcome (for example the worker stops after handing the message to the mail service), the next attempt waits out the in-flight window and then sends again. In that rare case the recipients may receive the email twice.

​
Test mode behavior

When the workflow is in Test mode, the email node does not send the email. Instead, the run output shows a preview with:
  • The recipient list
  • The rendered subject
  • The rendered email body
  • The attachment names that would be sent
Use test mode to verify email content and attachment mapping before you enable real outputs.

​
Inputs and outputs

Allowed inputs: Every action node except filter, split and classify, including the connector nodes (Business Central and QuickBooks in any operation, and callback), and the sub-workflow trigger. Filter, split and classify select pages rather than produce a result to send, so put the node that produces the data between them and the email. Output: Terminal node, no downstream connections. Sends an email to the configured recipients.

Build your first workflow

Tutorial using email output to deliver results

Callback output

Deliver results via webhook instead

Email trigger

Accept documents via email

Transform action

Transform data before sending via email