Overview

Tool Name

send_email_tools

Purpose

The send_email_tools suite integrates Snowflake’s SYSTEM$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
NameDefinitionFormat
to_addressesOne or more recipient addresses.String or List
subjectEmail subject line.String
message_bodyEmail body content.String
from_addressSender address to display.String
cc_addressesOne or more Cc recipients.String or List
bcc_addressesOne or more Bcc recipients.String or List
reply_toReply-to address.String
content_typeContent type, "text/plain" or "text/html".String
attachmentsFiles to attach, each { filename, content, content_type }.List of Objects
priorityDelivery priority: "high", "normal", "low".String
delivery_receiptRequest delivery receipt.Boolean
read_receiptRequest 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

  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. Attach any outputs your workflow produced.
  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.
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_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.