Email & SMS

Donotname automations can send emails and SMS messages as action steps. This guide covers how to configure SMTP for email and sms.to for text messages.

Email Setup

Configuring SMTP

Before sending emails, you need to configure an SMTP connection:

Go to Settings > Integrations > Email (SMTP)
Enter your SMTP server details:

Field	Description	Example
Host	SMTP server hostname	`smtp.gmail.com`
Port	SMTP port	`587` (TLS) or `465` (SSL)
Username	Login username	`notifications@yourcompany.com`
Password	Login password or app password	(stored securely)
From Name	Display name for sent emails	`Your Company`
From Email	Sender email address	`notifications@yourcompany.com`
Encryption	TLS or SSL	`TLS` (recommended)

Click "Test Connection" to verify the settings
Save the configuration

Common SMTP Providers

Gmail / Google Workspace:

Host: smtp.gmail.com
Port: 587
Encryption: TLS
You need to generate an "App Password" in your Google account security settings (regular password won't work with 2FA enabled)

Microsoft 365 / Outlook:

Host: smtp.office365.com
Port: 587
Encryption: TLS (STARTTLS)

Amazon SES:

Host: email-smtp.<region>.amazonaws.com
Port: 587
Encryption: TLS
Use IAM SMTP credentials (not your AWS access keys)

Sending Emails in Automations

Add a Send Email action to your automation:

Field	Description
To	Recipient(s) — use `{{record.Email}}` or a static address. Separate multiple with commas
CC	Carbon copy recipients (optional)
BCC	Blind carbon copy (optional)
Subject	Email subject line (supports template syntax)
Body	HTML or plain text body (supports template syntax)
Reply-To	Override reply address (optional)

HTML Email Templates

The email body supports full HTML, so you can create styled emails:

<div style="font-family: Arial, sans-serif; max-width: 600px; margin: 0 auto;">
  <div style="background: #2563eb; color: white; padding: 20px; text-align: center;">
    <h1 style="margin: 0;">Order Confirmation</h1>
  </div>
  <div style="padding: 20px; background: #f9fafb;">
    <p>Hi {{record.CustomerName|first_word}},</p>
    <p>Your order <strong>#{{record.OrderNumber}}</strong> has been confirmed.</p>

    <table style="width: 100%; border-collapse: collapse; margin: 16px 0;">
      <tr style="background: #e5e7eb;">
        <td style="padding: 8px; border: 1px solid #d1d5db;">Item</td>
        <td style="padding: 8px; border: 1px solid #d1d5db;">Amount</td>
      </tr>
      <tr>
        <td style="padding: 8px; border: 1px solid #d1d5db;">{{record.ProductName}}</td>
        <td style="padding: 8px; border: 1px solid #d1d5db;">{{record.Amount}} EUR</td>
      </tr>
    </table>

    {{if record.Notes is_not_empty}}
    <p><em>Notes: {{record.Notes}}</em></p>
    {{/if}}
  </div>
</div>

Email Tips

Use inline CSS — most email clients strip <style> tags, so always inline your styles
Test rendering — send test emails to yourself and check in Gmail, Outlook, and mobile
Keep images hosted — reference images via https:// URLs rather than embedding
Respect rate limits — most SMTP providers limit sends per minute/hour. Space out bulk sends

SMS Setup

Configuring sms.to

Donotname uses sms.to as the SMS provider:

Go to Settings > Integrations > SMS (sms.to)
Enter your sms.to API key
Set the Sender ID (the name or number that appears as the sender)
Save and test with a sample message

Sending SMS in Automations

Add a Send SMS action to your automation:

Field	Description
To	Phone number in international format (e.g., `+37060000000`). Use `{{record.Phone}}` for dynamic values
Message	Text content (supports template syntax). Max 160 chars for single SMS, longer messages are split
Sender ID	Override the default sender (optional)

SMS Example

Sveiki, {{record.Vardas|vocative_lt}}! Jūsų užsakymas #{{record.UzsakymoNr}} yra paruoštas atsiimti. Adresas: {{record.Adresas}}.

Unicode Support

SMS messages support full Unicode, which is essential for Lithuanian and other non-Latin alphabets. Keep in mind:

Standard SMS (GSM-7): 160 characters per segment — used for basic Latin characters
Unicode SMS (UCS-2): 70 characters per segment — used when the message contains Lithuanian characters (ą, č, ę, ė, į, š, ų, ū, ž) or other non-GSM characters
Multi-part messages: Longer messages are automatically split and reassembled on the recipient's phone
Cost: Unicode messages cost the same per segment, but each segment holds fewer characters, so a Unicode message may use more segments than a Latin-only equivalent

SMS Best Practices

Keep messages concise — SMS is meant to be short. Include only essential info and a link if more detail is needed
Include opt-out instructions where legally required
Use template syntax to personalize — {{record.Name|first_word}} keeps it friendly
Test with your own number before activating on real contacts
Check phone number format — the To field must be in international format with country code (e.g., +370 for Lithuania)