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

# Send Email Tools

> Send notifications, reports, and alerts from within your workflows.

## **Overview**

### **Tool Name**

```json theme={null}
send_email_tools
```

### **Purpose**

The **send\_email\_tools** suite integrates Snowflake's `SYSTEM$SEND_EMAIL` so workflows can deliver timely notifications, reports, and alerts in plain text or HTML.

### **Key Features & Functions**

<Steps>
  <Step title="Send Messages" icon="paper-plane">
    Deliver plain text or HTML emails from automated workflows and tasks.
  </Step>

  <Step title="Embed Artifact Links" icon="paperclip">
    Reference generated artifacts in the body using artifact markdown links (attachments are not supported).
  </Step>

  <Step title="Route & Track" icon="users">
    Route outbound notifications by recipient list and preserve metadata such as purpose and thread context.
  </Step>

  <Step title="Template & Automate" icon="gears">
    Use templated subjects and bodies to standardize recurring communications.
  </Step>
</Steps>

<Tip>
  Keep subjects short and specific. Add a clear call to action in the first line of the body to improve response rates.
</Tip>

## **Input Parameters for Each Function**

### **`send_email`**

**Parameters**

| **Name** | **Definition** | **Format** |
| - | - | :-: |
| **to\_addr\_list** | Recipient list (single email string or comma-separated list). | String |
| **subject** | Email subject line. | String |
| **body** | Email body content. | String |
| **bot\_id** | Required bot identifier for metadata and linkback context. | String |
| **mime\_type** | Body MIME type: `"text/plain"` or `"text/html"` (defaults to `"text/html"`). | String |
| **thread\_id** | Optional thread identifier for context linking. | String |
| **purpose** | Optional short purpose/intent metadata stored with the sent email. | String |
| **include\_genesis\_logo** | Whether to include the Genesis logo in generated HTML output. | Boolean |
| **save\_as\_artifact** | Whether to store the outgoing email payload/metadata as an artifact. | Boolean |

<Note>
  Attachments are not supported by `send_email`. Use artifact markdown links (for example `[Chart][artifact:/<artifact_id>]`) in the body when you need to reference generated files.
</Note>

## **Use Cases**

1. **Automated Reports**
   Send query results and dashboard snapshots to executives or partners.
2. **Milestones & Completions**
   Notify teams when missions or todos finish, including links to assets.
3. **Data Quality & Health Alerts**
   Raise incidents when thresholds are breached or pipelines fail.
4. **Artifact Sharing**
   Distribute generated PDFs, CSVs, or logs from recent runs.
5. **Workflow Notifications**
   Inform owners of approvals required or next steps in a process.
6. **Scheduled Briefings**
   Deliver daily or weekly summaries to stakeholders.
7. **Status Updates**
   Provide concise project progress notes with attached evidence.

## **Workflow/How It Works**

1. **Compose** recipients, subject, and body.
2. **Decide format** (`text/plain` or `text/html`).
3. **Embed artifact links** for generated outputs when needed (instead of attachments).
4. **Send** via `send_email`; capture the message id from the response.
5. **Handle responses** by logging success, failures, and any delivery notices.

## **Integration Relevance**

* **data\_connector\_tools** to export query results that become attachments.
* **project\_manager\_tools** to trigger milestone or status notifications.
* **file\_manager\_tools** to fetch files for attachment and link inclusion.
* **artifact\_manager\_tools** to reference generated outputs by id.
* **google\_drive\_tools** to include shared links alongside attachments.

<Warning>
  Do not embed secrets or credentials in email bodies or attachments. Email may be forwarded or stored outside your control.
</Warning>

## **Configuration Details**

* Snowflake email integration must be configured and permitted for your account.
* Addresses must follow RFC 5322 formatting.
* Use `content_type` that matches your body content.
* Keep attachment sizes within Snowflake and mail system limits.
* Receipts depend on recipient client support and policies.

## **Limitations or Notes**

1. Delivery depends on Snowflake service availability and recipient server policies.
2. Large attachments can delay or block delivery due to size thresholds.
3. Bulk sends may be rate limited or throttled.
4. HTML rendering varies by client; test critical layouts.
5. International delivery can introduce latency and compliance checks.

## **Output**

* **Send Confirmation**
  Message id, timestamp, and accepted recipients.
* **Recipient Status**
  Lists of delivered and failed addresses, when available.
* **Delivery Details**
  System response metadata and any bounce information.
* **Attachment Result**
  Confirmation that each attachment was processed.
* **Errors**
  Clear messages for invalid addresses, content issues, or system failures.