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

# Send Email

Send a transactional email via Resend from the b3os.org domain. Supports HTML and plain text bodies, CC, BCC, and reply-to. Ideal for: workflow notifications, alert emails, user confirmations, automated reports.

Catalog action Messaging

Send a transactional email via Resend from the b3os.org domain. Supports HTML and plain text bodies, CC, BCC, and reply-to. Ideal for: workflow notifications, alert emails, user confirmations, automated reports.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `send-email` |
| Category | Messaging |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `messaging`, `email`, `notification`, `alert`, `write` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `to` | `string` | Yes | Recipient email address |
| `subject` | `string` | Yes | Email subject line |
| `html` | `string` | No | HTML body of the email |
| `text` | `string` | No | Plain text body of the email |
| `from` | `string` | No | Sender address \(e.g. 'You &lt;you@yourdomain.com&gt;'\). When using your own Resend connector, set this to an address on your verified domain. When omitted with the default B3OS connector, uses an org-specific address \(b3os_&#123;orgId&#125;@b3os.org\). |
| `replyTo` | `string` | No | Reply-to email address |
| `cc` | `string` | No | CC recipients \(comma-separated email addresses\) |
| `bcc` | `string` | No | BCC recipients \(comma-separated email addresses\) |
| `$organizationID` | `string` | No | Injected by the workflow engine — the organization ID of the running workflow. Do not set manually. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | `string` | Yes | Resend email ID |
| `status` | `string` | Yes | - |

## Examples

**Workflow node**

```json
{
  "type": "send-email",
  "payload": {
    "to": "example-to",
    "subject": "example-subject",
    "html": "example-html"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/send-email/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "to": "example-to",
    "subject": "example-subject",
    "html": "example-html"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.