The platform stores mail account credentials per organization – either as a Mailtrap connection or as a generic SMTP credential. Project backends and other services can use them to send transactional or notification email (password resets, orders, internal alerts).
Two connection types
- Mailtrap (recommended): you only provide an API token (optionally a sender name/address). The platform handles sending via the Mailtrap Sending API and shows status, sending volume/plan, and your sending domains including DNS checks right in the connection’s detail view. You can also create new sending domains there.
- Email (SMTP): a generic SMTP account with host, port, username, password/API key, sender address, and sender name – for Mailtrap as an SMTP relay or other providers without a dedicated connection module.
Both types appear together in projects under the Mail account picker.
Typical flow (Mailtrap)
- Generate an API token at mailtrap.io (see Setting up email delivery with Mailtrap).
- In the Application Platform, under Connections → Mailtrap, create a new connection with the API token.
- Verify your sending domain – the connection’s detail view shows the required DNS records.
- Your generated project or backend reads the credentials from platform configuration and sends through Mailtrap.
Typical flow (generic SMTP)
- Create an account or API access with your email provider.
- In the Application Platform, under Connections → Email (SMTP), create an SMTP entry with the same values.
- Your generated project or backend reads the credentials from platform configuration and sends outbound mail through that relay.
Terminology
If you are unsure how SMTP relates to IMAP or POP3, read the short guide: SMTP, IMAP, and related protocols.
Security
- Prefer API keys/tokens or app passwords, not personal logins, whenever the provider supports it.
- Restrict provider permissions to sending only (no unnecessary mailbox access).