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

# Send Email

> Send an email from a flow, from a published template or with your own subject and body

The Send email step sends one email. Prefer a [published template](https://docs.quiva.ai/essentials/account/email-sending.md#email-templates): the template owns the design and wording, and the step only supplies the data.

> [!NOTE]
>
> The step reports that the email was **accepted for sending**, not that it was delivered. A suppressed address, missing consent or an unverified sending domain can still refuse it after the step completes. Watch the outcome in [Email delivery](https://docs.quiva.ai/essentials/account/email-sending.md#email-delivery), or react to it with the [Email delivery trigger](https://docs.quiva.ai/flows/triggers/email-delivery.md).

## Fields

**template\_key** `string`

A published template, chosen from a dropdown. Choosing one hides the subject and body fields. If none are listed, create and publish one under **Account → Email sending → Email templates**, then reopen the step.

**data** `object`

Answers the template's tags, as an object or a path into the run's data. A tag the data does not answer refuses the send.

**subject** `string`

Only needed when you send without a template. Not required when `template_key` is set.

**class** `commercial | transactional`

**commercial** mail honours unsubscribes and the suppression list. **transactional** is for messages the person needs, such as a receipt or a notice.

**cc / bcc** `addresses`

Transactional mail only.

**attachments** `files`

Attach a file stored in a space with the file picker, or name one by bucket, key and optional file name. Map **Attachments**, or any one value, from an earlier step. Up to 6 MB in total. Files are read with the sender's own access, so a send attaches only what its sender could open, and a missing file refuses the send and names it. The step cannot upload files.

**idempotency\_key** `string`

A key you choose. A retry with the same key does not send the email twice.

**ref** `object`

Your own reference, such as an order id. It comes back on the delivery log row and on every [delivery event](https://docs.quiva.ai/flows/triggers/email-delivery.md), so you can tie an outcome to the run that sent it.

> [!TIP]
>
> Email sent by a run that an Email delivery trigger started starts no further flow and raises no task, so a failure handler cannot loop.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.