Send E-Mail (old)
Deprecated. For new workflows use Send email: several recipients with Cc/Bcc, formatted text with signature, attachments, replies in the thread of a received email and drafts. Existing workflows with this step keep working; in the editor the step is marked Deprecated.
Send an outgoing email via SMTP.
What it does
Connects to an SMTP server you configure (your company's mail server, a transactional service like SendGrid, or a generic provider), sends one email, and continues with the next step. The body and subject can be assembled by previous steps and pulled from memory.
What you configure
| Field | What it controls | Required | Notes |
|---|---|---|---|
| SMTP host | Address of the SMTP server. | required | Example: smtp.example.com or smtp.sendgrid.net. |
| SMTP port | Port number. | required | Typically 587 (STARTTLS) or 465 (TLS). |
| SMTP user | Login for the SMTP server. | required | Stored as a secured value. |
| SMTP password | Password / API key. | required | Stored as a secured value. |
| From | Sender address. | required | Must be allowed by your SMTP server. Many providers reject mismatches. |
| To | Recipient address. | required | A single address. Use a previous step to compute it from memory. |
| Subject | The subject line. | required | Can be a literal value or a value pulled from memory. |
| Body | The message body. | required | Plain text. For HTML, write the markup directly; the platform sends what you provide. |
📷 SCREENSHOT: The Send E-Mail step with the SMTP fields collapsed and the From/To/Subject/Body fields visible.
Example scenario
Daily digest. A workflow runs on a cron schedule, builds a summary with an LLM, and ends with a Send E-Mail step that delivers the summary to a fixed distribution address.
Recommendations
- ✅ Use a dedicated SMTP account for the AI Kit. This makes it easy to spot which mails were sent by automations.
- ✅ Set the From address to one your SMTP provider has authenticated (SPF/DKIM). Otherwise the mail lands in spam.
- ✅ Keep the Subject short and informative. End-users often filter on it.
- ⚠️ This integration sends one mail per execution. To send to multiple recipients, build a step that produces a list and run a sub-workflow per recipient, or use the To field with a comma-separated list if your SMTP server supports it.
- ⚠️ HTML mails work, but every mail client renders them differently. Plain text is more robust.
- ❌ Do not include large attachments. This integration does not support file attachments. Use a link to a file instead.
- ❌ Do not store SMTP credentials in plain memory keys. Always use the secured-field types.
What to do next
- For incoming mail: E-Mail Inbox Watcher.
- For text generated by AI before sending: AI action.