SMTP: Send Email
Send a plain text or HTML email via any SMTP server, with optional file attachment. Supports multiple recipients (comma-separated To, CC, BCC), Reply-To, HTML + plain text bodies. Attachment accepts a URL, a data URI (data:image/png;base64,...), or raw Base64 — so you can directly pass the result of nodes like QR Code Generator.
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Active workflows | 3 | 10 | 45 | Unlimited |
Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.
When to use this node #
Send a plain text or HTML email via any SMTP server, with optional file attachment. Supports multiple recipients (comma-separated To, CC, BCC), Reply-To, HTML + plain text bodies. Attachment accepts a URL, a data URI (data:image/png;base64,...), or raw Base64 — so you can directly pass the result of nodes like QR Code Generator.
Add SMTP: Send Email to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.
Before you begin #
Connect SMTP email in App Connections first. Select the intended account in this node; an account connected to a different service is not interchangeable. Available actions depend on the permissions granted to that connection.
Configure the fields #
| Field | What to enter |
|---|---|
| SMTP Mail Account | Connected SMTP mail account |
| To (Recipient) | Recipient email address. For multiple recipients use comma-separated values (e.g., a@example.com, b@example.com) |
| Subject | Email subject line |
| HTML Body (Optional) | Email body in HTML format (e.g., <h1>Hello</h1><p>Message here</p>). Leave empty to send plain text only. |
| Plain Text Body (Optional) | Email body in plain text format. Used as fallback when HTML is not supported by recipient email client. |
| Attachment (Optional) | File to attach. Accepts: a full URL (https://...), a data URI (data:image/png;base64,...), or raw Base64 content. You can pass the result variable of nodes like QR Code Generator directly here. Leave empty for no attachment. |
| Attachment Filename (Optional) | Display name for the attachment (e.g., qrcode.png, report.pdf). Leave empty to auto-detect from URL or MIME type. |
| Attachment MIME Type (Optional) | MIME content type (e.g., image/png, application/pdf). Leave empty to auto-detect. |
| CC (Optional) | Carbon Copy recipients. Comma-separated email addresses (e.g., cc1@example.com, cc2@example.com) |
| BCC (Optional) | Blind Carbon Copy recipients. Comma-separated email addresses. Recipients cannot see each other. |
| Reply-To (Optional) | Email address that replies will be sent to. Leave empty to use the From address. |
Use the result #
Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.
| Output | Meaning / label |
|---|---|
success |
Success Status (true/false) |
messageId |
Message ID |
accepted |
Accepted Recipients |
rejected |
Rejected Recipients |
error |
Error Message |
Connect the next step #
Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.
Test it in a workflow #
- Configure this node with a small, recognizable test input or a test resource.
- Check the variables from preceding steps and the connection selected in the inspector.
- Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
- Open Workflow Activity and check the outcome before enabling wider use.
If something goes wrong #
- Reconnect the account if authorization has expired, then verify its permissions on the specific resource.
- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the troubleshooting guide for a symptom-by-symptom checklist.
Related guides #
Catalog coverage #
This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.