Tendrl

Tendrl Email Connector

Direction: Write Only | Type: email

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 has a fair-use cap of 1,000 sends per account per month on every plan, including Free. Each message counts as one send, however many recipients it has, and approval notifications sent through a Tendrl Email connector count too. To send more, use the SMTP Email connector with your own email account.

Who You Can Email#

Tendrl Email sends from Tendrl's own address, so it is for notifying your own team, not your customers. Every recipient (To, CC, BCC) and the Reply-To address must be one of:

If the account owner's email is at a public provider (Gmail, Outlook.com, Yahoo, iCloud, an internet provider's mail, or a disposable address service), there is no organization domain, and Tendrl Email can only send to account members.

Each message can have at most 10 recipients across To, CC and BCC. To email anyone else (customers, partners, more recipients), use the SMTP Email connector with your own Gmail, Microsoft 365, or SMTP server.

Every Tendrl Email message ends with a short line saying which account's workflow sent it.

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. Each must be at your organization's domain or belong to an account member (see Who You Can Email). Supports Jinja templates:

code

{{ payload.oncall_email }}

Or multiple recipients:

code

ops@yourcompany.com, {{ payload.notify_email }}

Subject (required)#

Email subject line. Supports Jinja templates:

code

Order #{{ payload.order_id }} Confirmation

Body - Text (optional)#

Plain text email body. Supports Jinja templates:

code

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:

html

<h1>Hello {{ payload.name | e }}</h1>
<p>Your order <strong>#{{ payload.order_id | e }}</strong> has been confirmed.</p>
<p>Estimated delivery: {{ payload.delivery_date | e }}</p>
Escape values you didn't write

Payload values are inserted into the HTML exactly as they arrive. If a value can come from outside your control (a form, a webhook, a device, an AI step), add the e filter so any HTML in it shows as text instead of being rendered: {{ payload.name | e }}. Your own markup in the template is never changed.

CC (optional)#

CC recipients, comma-separated. Same rule as To. Supports Jinja templates.

BCC (optional)#

BCC recipients, comma-separated. Same rule as To. Supports Jinja templates.

Reply-To (optional)#

Reply-to email address. Same rule as To. Supports Jinja templates.

Output#

The node outputs a success event:

json

{
  "success": true,
  "status": "sent",
  "data": {
    "to": ["ops@yourcompany.com"],
    "subject": "Order #12345 Confirmation"
  },
  "service": "email",
  "operation": "send"
}

Access in subsequent nodes:

Errors#

Error Meaning
Monthly Tendrl Email limit reached (1,000) The account has used its 1,000 sends for this month. The message gives the date the count resets. To send more before then, use an SMTP connector with your own email account.
Tendrl Email is not enabled for this account Tendrl couldn't confirm the account's sending allowance, so nothing was sent. Retry shortly, or use an SMTP connector. Contact support if it keeps happening.
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.
Tendrl Email can only send to your organization's domain (...) or members of your account. Not allowed: ... A recipient or the Reply-To address is outside your organization's domain and isn't an account member. Use an SMTP connector for those addresses.
Tendrl Email can only send to members of your account. Not allowed: ... The account owner's email is at a public provider, so only account members can be emailed. Use an SMTP connector for anyone else.
Tendrl Email can send to at most 10 recipients per message To, CC and BCC together list more than 10 addresses. Split the send, or use an SMTP connector.
Tendrl Email couldn't confirm which addresses this account may email Tendrl couldn't look up your account's members, so nothing was sent. Retry shortly.
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#

Sends are counted per account for each monthly billing period, and the count resets when the next period starts. The Strand Usage page shows how many of your 1,000 sends you've used; a warning appears at 80% with the reset date.

Tips#

Limitations#

← Back to Strand docs