Email (SMTP)
Any mail server or provider that speaks SMTP: your own domain, Gmail with an app password, or a sending service like Postmark, Mailgun or Amazon SES.
CategoryEmail
Used byEmail node
Secret fields1
TestYes
Set it up
- From your provider, get the SMTP host, port, user name and password. Many call the password an app password or SMTP key.
- Add an Email (SMTP) integration with those, and the address mail should come from.
- Press Test, optionally with an address to send a test email to.
- Pick it in an Email node.
Fields
| Field | Required | What it is |
|---|---|---|
| Hosthost | Yes | The server's name, like smtp.example.com. |
| Portport | No | 587 by default. One of 25, 465, 587 or 2525. |
| Securitytls | No | STARTTLS (upgrades after connecting, usually 587) or Implicit TLS (from the start, usually 465). Picked from the port when left out. Mail is never sent unencrypted. |
| User nameuserName | No | Leave empty for a relay that doesn't ask you to sign in. |
| Passwordpassword | No | Needed when there's a user name. |
| From addressfromAddress | Yes | The address mail is sent as. Your provider must allow it. |
| From namefromName | No | Shown beside it, like Greenhouse. |
Secret fields are encrypted as soon as you save them and never shown again: the console shows their last four characters so you can tell which one is saved. Replace one to rotate it; workflows pick up the new one on their next step.
Test it
Connects, starts TLS and signs in. Give it an address and it also sends a test email there.
Problems you might see
| Code | Means |
|---|---|
INTEGRATION_AUTH_FAILED | The server refused the user name or password. |
INTEGRATION_TLS_FAILED | The TLS handshake failed. Check the port and security setting go together. |
INTEGRATION_UNREACHABLE | Nothing answered at that host and port. |
Codes starting INTEGRATION_ come from saving or testing. Every other integration code is on the error codes page.