# Send an email from a workflow

> Use the Send Email action to send an email template or a Simple Email you write in the step, with recipients, values and attachments from the workflow.

Source: https://tadabase.com/docs/workflows/communication-actions  
Status: Verified Nov 17, 2026. Checked against the current product

The **Send Email** action sends an email each time the workflow reaches it, for example a confirmation to a customer when a job is booked. You can send one of your email templates, or write a **Simple Email** right in the step.

To send record data to another system instead of a person, use [Trigger Webhook](https://tadabase.com/docs/workflows/send-data-with-trigger-webhook).

## Choose what to send

Add a step, click **Add Action**, then under **Communication** choose **Send Email**. Under **Email source**, pick one of two kinds:

| Email source | Use it when |
| --- | --- |
| An email template (listed by name) | The same email is sent from several places, or someone else maintains the wording. Change the template once and every workflow that uses it changes too. See [Create and reuse email templates](https://tadabase.com/docs/integrations/sending-emails-and-email-templates). |
| **Simple Email** (Map fields and send) | The email belongs to this workflow only. You set the recipients and write the message in the step. |

![The Send Email step in the side panel with Simple Email chosen, showing the Subject, Send To and Content cards](https://tadabase.com/docs-shots/workflows-send-email-panel.webp)

## Write a Simple Email

Each part of a Simple Email is a card. Fields marked with a star are required.

| Card | What to put |
| --- | --- |
| **Subject** * | The subject line. Type it, or take it from a field or an earlier step. |
| **Send To** * | One or more recipients. Click **Add Recipient** for each. A recipient can be a typed address, an email field of the record, the logged-in user's email or a value from an earlier step. |
| **Cc**, **Bcc**, **Reply To** | Optional. Click **Add Cc**, **Add Bcc** or **Add Reply To** for each address. |
| **From Name**, **From Email** | Optional. The sender's name and address the recipient sees. |
| **Content** * | The message. Type it, and press **/** or click **+** to insert a field at the cursor. Click a value you inserted to change its source or give it a **Fallback when blank**. |
| **Email Layout** | Optional, when your plan has email layouts. Wraps the message in one of your layouts. See [Brand your emails with an email layout](https://tadabase.com/docs/integrations/brand-your-emails-with-an-email-layout). |
| **Attachments** | Optional. Click **Add Attachment** and pick a file (see below). |

## Send an email template

1. **Pick the template** Under **Email source**, pick the template by name. The template already holds the recipients, subject and message.
2. **Fill the parameters** If the template has parameters, **Template Parameters** lists them. Give each one a value. A parameter without a value shows **Value required**.
3. **Override if needed (optional)** Under **Overrides (optional)**, set a different **Subject**, **From Name** or **From Email** for this step only.

An **Attachments** section appears when your app allows attachments in email templates and the chosen template allows them.

## Attach files

**Select attachment...** lists the files the step can send:

- File and image fields of the workflow's record, and fields that hold a file's web address.
- Inside a loop, the same kinds of fields of the record the loop is on.
- A file made by an earlier step: **Create PDF Form**, **Create PDF Page**, **Export to CSV** or **Export to JSON**. See [Create a PDF from a workflow](https://tadabase.com/docs/workflows/document-actions).

If nothing can be attached, the section says **No attachment sources are available.**

## Delivery and limits

- Emails go out through your app's email settings, either Tadabase's mail service or your own SMTP server. See [Ways to send email from your app](https://tadabase.com/docs/integrations/emails-and-smtp-overview).
- Each email counts toward your plan's email allowance. When it is used up, the step fails with `Email limit reached.`
- If every To, Cc and Bcc recipient is blank for a record, nothing is sent and the step says so in its history.
- A step marked as sent means the mail server accepted the email. Whether it reaches the inbox depends on the email provider and the recipient's server.

## Check that it worked

Open the step's **History** tab, or the workflow's run history, to see each email's recipients, subject, attachments and result. See [Workflow history and logs](https://tadabase.com/docs/workflows/workflow-history-and-logs). Your app's [email logs](https://tadabase.com/docs/settings/email-logs) list sent emails too.

Later steps can branch on the email's **Sent** and **Delivery State** values, for example to try another address when sending fails. See [Conditions and branches](https://tadabase.com/docs/workflows/conditions-and-branches).
