> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/communication-and-human-input/send-email.md).

# Send Email

Send a message through StackAI’s email service. Use it to deliver a workflow result or notify a recipient when a task completes.

## Send a workflow result

1. Enter **To**, **Subject**, and **Content**. Separate multiple recipient addresses with commas. Add **CC** or **BCC** only when needed.
2. For attachments, supply downloadable file URLs in **Attachments**. Review the recipient list, content, and files before running the action.
3. Run the action and check **Status** and **Message**. Use **Details** to inspect the sending result.

**Result:** The result reports whether the sending operation succeeded. It does not establish that the recipient read the message.

## Behavior and troubleshooting

This tool uses StackAI’s email service; it does not send from a connected personal mailbox. Use the relevant provider’s email action when the sender must be that mailbox. If a result is uncertain, check delivery before retrying to avoid duplicate messages.

## Inputs

| Field              | Parameter         | Description                                                               |
| ------------------ | ----------------- | ------------------------------------------------------------------------- |
| Subject (required) | `subject`         | The subject line of the email                                             |
| Content (required) | `content`         | The main content/body of the email (HTML supported)                       |
| To (required)      | `to`              | Email address(es) of the recipient(s), comma-separated.                   |
| CC                 | `cc`              | Email address(es) to CC, comma-separated.                                 |
| BCC                | `bcc`             | Email address(es) to BCC (hidden from other recipients), comma-separated. |
| Attachments        | `attachment_urls` | Downloadable URLs for the files to attach.                                |

## Outputs

| Field   | Parameter | Description                                               |
| ------- | --------- | --------------------------------------------------------- |
| Status  | `status`  | The status of the email sending operation (success/error) |
| Message | `message` | A descriptive message about the email sending result      |
| Details | `details` | The details of the sent email                             |

## Related guidance

[Human Input and Approval Controls](https://docs.stackai.com/technical-reference/interfaces-and-conversations/human-input-and-approval-controls.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/communication-and-human-input/send-email.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
