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

# Send Email

> Send an email from a workflow, at any step, including the last one.

The **Send Email** node sends an email when the workflow reaches it, then continues to the next node (if there is one). Place it **anywhere** in the workflow: partway through, on a specific branch, or as the final step.

***

## When to use it

* "Generate the report, email it to the team, then archive the file." (mid-flow)
* "Process the order, then email the customer a confirmation." (as the last step)
* "On the approved branch, email the customer; on the rejected branch, email the sales owner." (per branch)

It sends from exactly where you place it on the canvas. For "email me only when the workflow fails or succeeds" (without adding a node), use **workflow notification rules** (workflow Settings → General) instead.

***

## Configuration

| Field                | Description                                         | Templated |
| -------------------- | --------------------------------------------------- | --------- |
| **Label**            | Display name on the canvas                          | No        |
| **Recipients**       | Comma-separated email addresses.                    | Yes       |
| **Subject**          | The email subject.                                  | Yes       |
| **Body**             | The email body (plain text).                        | Yes       |
| **Reply-To**         | Optional. Defaults to the workflow owner.           | No        |
| **If sending fails** | `Fail the workflow` (default) or `Continue anyway`. | No        |

Recipients, subject and body support `{{ variables }}` resolved from **upstream nodes**, such as a trigger field (e.g. `{{ trigger.email }}`) or an earlier node's output variable (e.g. `{{ summary }}`). See [Passing Data Between Nodes](/workflow-editor/passing-data).

<Note>
  These are the same upstream variables every other node uses. Workflow-level metadata such as the workflow name or run status is **not** available inside a Send Email node; that information is only exposed to workflow notification rules (workflow **Settings → General**), which run after the workflow finishes. An unresolved `{{ … }}` is left blank.
</Note>

***

## Who you can email

* **Members of your organization** can always be emailed.
* **External addresses** must be on your organization's allowed list (platform **Settings → General → Email recipients**, managed by an organization owner). If a recipient isn't a member and isn't on the allowed list, that send is **denied**.
* Every email counts toward your plan's **monthly email allowance**. If the allowance is reached, further sends are denied until the next cycle.

***

## Send Email vs email connectors

The **Send Email** node sends from Spojit's built-in mail service, with no connection or external account needed. It's subject to your plan's monthly email allowance and the workspace email allowlist.

If you need to send from **your own email address or domain**, use one of the email connectors in a [Connector node](/workflow-editor/nodes/connector) instead:

* **[Resend](/connectors/integrations/resend)**: transactional email API with contact management and domain verification. Good for branded emails from your domain.
* **[SMTP](/connectors/integrations/smtp)**: send via any SMTP server (Gmail, Outlook, Amazon SES, SendGrid, etc.). Good when you already have an SMTP provider.

## If sending fails

A send can fail because a recipient isn't allowed, the monthly allowance is reached, or the mail system is unavailable. The **If sending fails** setting controls what happens:

* **Fail the workflow** (default): the run stops with an error, like any other failed step.
* **Continue anyway**: the failure is logged and the workflow proceeds to the next node. Use this when the email is a nice-to-have, not critical.