Docs / Strand / connectors/email
Tendrl Email Connector
Send emails from your Strand workflows using Tendrl's managed email service. No server setup is needed; just configure recipients, subject, and body.
Availability
Tendrl Email is a managed email service included with eligible plans. See tendrl.com/pricing for availability and monthly sending limits.
Connector Setup
Create a Tendrl Email connector from the Connectors page.
Configuration Fields
| Field | Required | Description |
|---|---|---|
| Name | Yes | Friendly name for this connector (e.g., "Order Notifications") |
| Description | No | Optional description for reference |
No additional configuration is needed; the email service is managed by Tendrl.
Node Configuration
Once the connector is created, drag a Connector node onto your workflow canvas and select your email connector. Configure the following fields:
To (required)
Recipient email addresses, comma-separated. Supports Jinja templates:
{{ payload.customer_email }}
Or multiple recipients:
[email protected], {{ payload.notify_email }}
Subject (required)
Email subject line. Supports Jinja templates:
Order #{{ payload.order_id }} Confirmation
Body - Text (optional)
Plain text email body. Supports Jinja templates:
Hello {{ payload.name }},
Your order #{{ payload.order_id }} has been confirmed.
Estimated delivery: {{ payload.delivery_date }}
Thank you for your purchase!
Body - HTML (optional)
HTML email body. If both text and HTML are provided, email clients that support HTML will display the HTML version. Supports Jinja templates:
<h1>Hello {{ payload.name }}</h1>
<p>Your order <strong>#{{ payload.order_id }}</strong> has been confirmed.</p>
<p>Estimated delivery: {{ payload.delivery_date }}</p>
CC (optional)
CC recipients, comma-separated. Supports Jinja templates.
BCC (optional)
BCC recipients, comma-separated. Supports Jinja templates.
Reply-To (optional)
Reply-to email address. Supports Jinja templates.
Output
The node outputs a success event:
{
"success": true,
"status": "sent",
"data": {
"message_id": "0100018e1234abcd-12345678-1234-1234-1234-123456789012-000000",
"to": ["[email protected]"],
"subject": "Order #12345 Confirmation"
},
"service": "email",
"operation": "send"
}
Access in subsequent nodes:
{{ steps.node_a1b2c3d4.output_payload.success }}- Whether email sent successfully{{ steps.node_a1b2c3d4.output_payload.data.message_id }}- Unique message ID{{ steps.node_a1b2c3d4.output_payload.data.to }}- Recipient list
Errors
| Error | Meaning |
|---|---|
| Tendrl Email is not available on your current plan | Your plan doesn't include email. See tendrl.com/pricing for eligible plans. |
| Monthly email limit reached | You've used all your emails for this month. The limit resets on the first of the next month. |
| At least one 'to' email address is required | No recipient specified in the To field. |
| Email subject is required | Subject line is empty. |
| Email body (text or HTML) is required | Both body fields are empty; provide at least one. |
| Email rejected | The email service rejected the message (invalid recipient, etc.) |
| Email sending rate limit exceeded | Too many emails sent too quickly. Will retry automatically. |
Usage Tracking
Email usage is tracked monthly and resets on the first day of each month. View your current usage in the Strand dashboard.
Tips
- Use HTML for rich emails: Include both text and HTML bodies for the best experience across email clients.
- Test with a single recipient first: Before sending to multiple recipients, test your template with one address.
- Jinja templates work everywhere: Subject, body, and recipients all support dynamic values from your event payload.
Limitations
- Attachments: Not currently supported.
- Incoming email: Not supported. Use API triggers to initiate workflows from email events.
- Custom sender address: The sender address is managed by Tendrl and cannot be changed per-connector.
Tendrl