Skip to main content
By default, automation emails are sent from Teable’s built-in mail service. While this works for basic notifications, you may want to send emails from your own domain for branding, deliverability, or compliance reasons. Custom SMTP configuration lets you do exactly that. When you configure a custom SMTP server, all emails sent by that action come from your own mail server and your own sender address — recipients see your domain, not Teable’s.

​
When to use custom SMTP

  • Send emails from your company domain (e.g., noreply@yourcompany.com or support@yourcompany.com) so recipients recognize the sender.
  • Improve deliverability. Emails from your own domain with proper SPF, DKIM, and DMARC records are less likely to land in spam.
  • Meet compliance requirements. Some industries require that automated emails originate from an organization-controlled domain.
  • Use your existing email infrastructure. Route emails through your company’s mail server for logging, archival, or security scanning.
  • Higher sending limits. Teable’s built-in service has rate limits. Your own SMTP server may support higher throughput.

​
Configuration

In the Send Email action, click the transport configuration option to set up a custom SMTP server:

​
How to set it up

  1. Open your automation and go to the Send Email action.
  2. Click the transport configuration option (gear icon or link near the sender settings).
  3. Enter your SMTP server details:
    • Host: Your email provider’s SMTP server address.
    • Port: Use 465 for SSL/TLS or 587 for STARTTLS. If unsure, try 465 first.
    • Username: Your email account or SMTP username.
    • Password: Your email password or, for providers like Gmail, an app-specific password.
  4. Set the From Address — this is what recipients see as the sender.
  5. Click Test to verify the connection. Teable will attempt to send a test email through your SMTP server.
  6. If the test succeeds, save the configuration. All emails from this action will now use your SMTP server.

​
Common SMTP settings by provider

​
Common errors and fixes

When a run fails to send, open the workflow’s Run history and check the output of the Send Email step. For a custom SMTP server, the step reports the rejection your mail server returned: its reply code, the SMTP command that failed, the rejected recipients, and the host. Match that against the causes below.

​
Tips

  • Test before going live. Always send a test email after configuring SMTP to confirm everything works.
  • Use app-specific passwords for Gmail, Yahoo, and other providers that support two-factor authentication. Your regular account password will not work if 2FA is enabled.
  • Set up SPF, DKIM, and DMARC on your domain’s DNS records to improve email deliverability and prevent your emails from being flagged as spam.
  • Keep credentials secure. SMTP passwords are stored encrypted in Teable, but avoid sharing automation configurations with sensitive credentials.
  • Monitor delivery. If emails stop arriving, check your SMTP provider’s dashboard for bounced messages, rate limit warnings, or account issues.
For Gmail, use an App Password instead of your account password. See Set up Gmail IMAP for how to create one.
Last modified on August 8, 2026