> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ingestly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email

> Send pipeline results via email.

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

| Field           | Type            | Required | Description                                                                       |
| --------------- | --------------- | -------- | --------------------------------------------------------------------------------- |
| **Recipients**  | string\[]       | Yes      | Email addresses to receive the results                                            |
| **Subject**     | string          | No       | Custom email subject line. Defaults to a generated subject with the pipeline name |
| **Body**        | template editor | No       | Custom email body template                                                        |
| **Attachments** | list            | No       | Files to attach from the pipeline using JSON path references                      |

### 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

<Tip>Use test mode to verify email content and attachment mapping before you enable real outputs.</Tip>

## 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.

## Related

<CardGroup cols={2}>
  <Card title="Build your first pipeline" icon="hammer" href="/guides/build-first-pipeline">
    Tutorial using email output to deliver results
  </Card>

  <Card title="Callback output" icon="webhook" href="/nodes/callback">
    Deliver results via webhook instead
  </Card>

  <Card title="Email trigger" icon="envelope" href="/nodes/email-trigger">
    Accept documents via email
  </Card>

  <Card title="Transform action" icon="arrows-rotate" href="/nodes/transform">
    Transform data before sending via email
  </Card>
</CardGroup>