notiflowsDocs
Channels & ProvidersEmail

SMTP

Configure any email provider via SMTP in Notiflows

SMTP is a universal adapter that lets you connect any email provider that supports standard SMTP credentials. Use this when your provider isn't natively supported, or when you want to use your own mail server.

Prerequisites

Before configuring SMTP in Notiflows, you need:

  1. SMTP server credentials from your email provider
  2. A verified sender address (if required by your provider)

Configuration

FieldRequiredDescription
HostYesSMTP server hostname (e.g., smtp.example.com)
PortYesSMTP port (typically 587 for TLS, 465 for SSL, 25 for unencrypted)
UsernameNoSMTP authentication username
PasswordNoSMTP authentication password
SSLNoEnable SSL connection (default: off)
TLSNoTLS mode: always, never, or if_available (default)
From EmailYesSender email address
From NameNoDisplay name shown to recipients

Common SMTP Settings

ProviderHostPortTLS
Gmailsmtp.gmail.com587Always
Outlook/Office 365smtp.office365.com587Always
Postmarksmtp.postmarkapp.com587Always
Mailgunsmtp.mailgun.org587Always
SendGridsmtp.sendgrid.net587Always
Amazon SESemail-smtp.{region}.amazonaws.com587Always

Set up in Notiflows

  1. Navigate to Channels in your project
  2. Click Create Channel
  3. Select Email as the channel type
  4. Select SMTP as the provider
  5. Enter your Host, Port, and authentication credentials
  6. Configure SSL/TLS based on your provider's requirements
  7. Enter your From Email and optionally a From Name
  8. Save the channel

Templates

Email templates support three content types:

  • Visual - Drag-and-drop editor for rich HTML emails
  • HTML - Raw HTML with full control
  • Plaintext - Simple text emails

Use Liquid templating for dynamic content:

Hi {{ recipient.first_name }},

{{ data.message }}

Available variable contexts:

  • recipient.* - Recipient user data (first_name, last_name, email, etc.)
  • actor.* - User who triggered the notification
  • data.* - Custom payload passed when triggering the notiflow

On this page