Skip to main content
The email output node sends pipeline 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.

​
Test mode behavior

When the pipeline 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: Any action node that produces a result payload (extract, review, validation, transform, merge, parse, HTTP, loop, variable, store, prompt). Filter and split are not among them: they emit page groups, not 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 pipeline

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