Overview
Tool Name
Purpose
The send_email_tools suite integrates Snowflake’sSYSTEM$SEND_EMAIL so your workflows can deliver timely notifications, reports, and alerts to stakeholders in plain text or HTML, with optional attachments.
Key Features & Functions
Send Messages
Deliver plain text or HTML emails from automated workflows and tasks.
Attach Files
Include generated reports, logs, and documents as attachments.
Route & Track
Address To, Cc, and Bcc, and request delivery or read receipts when supported.
Template & Automate
Use templated subjects and bodies to standardize recurring communications.
Keep subjects short and specific. Add a clear call to action in the first line of the body to improve response rates.
Input Parameters for Each Function
send_email
Parameters
| Name | Definition | Format |
|---|---|---|
| to_addresses | One or more recipient addresses. | String or List |
| subject | Email subject line. | String |
| message_body | Email body content. | String |
| from_address | Sender address to display. | String |
| cc_addresses | One or more Cc recipients. | String or List |
| bcc_addresses | One or more Bcc recipients. | String or List |
| reply_to | Reply-to address. | String |
| content_type | Content type, "text/plain" or "text/html". | String |
| attachments | Files to attach, each { filename, content, content_type }. | List of Objects |
| priority | Delivery priority: "high", "normal", "low". | String |
| delivery_receipt | Request delivery receipt. | Boolean |
| read_receipt | Request read receipt. | Boolean |
When sending HTML, ensure your markup degrades gracefully for clients that display plain text only. Consider including a brief plain-text summary at the top.
Use Cases
- Automated Reports Send query results and dashboard snapshots to executives or partners.
- Milestones & Completions Notify teams when missions or todos finish, including links to assets.
- Data Quality & Health Alerts Raise incidents when thresholds are breached or pipelines fail.
- Artifact Sharing Distribute generated PDFs, CSVs, or logs from recent runs.
- Workflow Notifications Inform owners of approvals required or next steps in a process.
- Scheduled Briefings Deliver daily or weekly summaries to stakeholders.
- Status Updates Provide concise project progress notes with attached evidence.
Workflow/How It Works
- Compose recipients, subject, and body.
- Decide format (
text/plainortext/html). - Attach any outputs your workflow produced.
- Send via
send_email; capture the message id from the response. - 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.
Do not embed secrets or credentials in email bodies or attachments. Email may be forwarded or stored outside your control.
Configuration Details
- Snowflake email integration must be configured and permitted for your account.
- Addresses must follow RFC 5322 formatting.
- Use
content_typethat matches your body content. - Keep attachment sizes within Snowflake and mail system limits.
- Receipts depend on recipient client support and policies.
Limitations or Notes
- Delivery depends on Snowflake service availability and recipient server policies.
- Large attachments can delay or block delivery due to size thresholds.
- Bulk sends may be rate limited or throttled.
- HTML rendering varies by client; test critical layouts.
- 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.