Email

Coolify can send team notifications through a hosted email service, a team-specific SMTP server, or Resend. Self-hosted teams can also reuse the transactional email provider configured for the entire Coolify instance.

Open Notifications > Email to configure the channel.

Instance-wide email is self-hosted only

The Use system wide (transactional) email settings option appears only on self-hosted Coolify. It uses the sender and SMTP or Resend provider configured under Settings > Email for the Coolify instance.

Coolify Cloud shows Use Hosted Email Service instead. Cloud users do not configure the instance-wide provider.

Choose an email provider

The available choices depend on how you use Coolify:

ProviderAvailabilityWhat you need
Use Hosted Email ServiceCoolify CloudNo provider credentials.
Use system wide (transactional) email settingsSelf-hosted CoolifyA working email provider under Settings > Email.
SMTP ServerCoolify Cloud and self-hosted CoolifySMTP sender, host, port, encryption, and optional authentication details.
ResendCoolify Cloud and self-hosted CoolifyA sender name, sender address, and Resend API key.

A team can use only one email path at a time. The hosted and instance-wide options disable team-specific SMTP and Resend. Enabling team-specific SMTP disables Resend, and enabling Resend disables SMTP.

Before you start, prepare the values required by the option you plan to use:

  • For SMTP, copy the host, port, encryption method, username, and password from your email provider. Confirm that the provider permits the sender address you want to use.
  • For Resend, verify your sending domain or sender in Resend and create an API key.
  • For system-wide email, configure and test the instance provider first. This requires access to the self-hosted instance settings.

Use the hosted or system-wide provider

The dashboard shows the option for your Coolify deployment type. It does not show both options together.

Configure the instance provider

As an instance administrator, open Settings > Email. Enter the shared sender details, configure either SMTP or Resend, enable that provider, and save it.

Use Send Test Email on the instance settings page. Continue only after that test arrives. This confirms that the instance-wide provider works before a team tries to reuse it.

Reuse it for the team

Open Notifications > Email for the team and turn on Use system wide (transactional) email settings.

The team now uses the instance sender and provider credentials. It does not receive its own copy of those credentials, and team members cannot change them from the Notifications page.

Choose events and test the team channel

Select the events to send by email under Notification Settings. Then select Send Test Email, enter a recipient address you can access, and send the test.

Event selections and the test recipient remain specific to this team. Changing the instance-wide provider affects every team that reuses it.


Configure a team provider

Choose SMTP or Resend when this team should use its own email provider instead of the hosted or system-wide configuration.

Enter the connection details supplied by your SMTP provider.

  1. Open Notifications > Email.

  2. Enter From Name and a valid From Address.

  3. Under SMTP Server, enter the connection details supplied by your email provider:

    FieldValue
    HostSMTP hostname, such as smtp.example.com.
    PortProvider's SMTP port. Common values are 587, 465, and 25; Coolify accepts ports from 1 to 65535.
    EncryptionStartTLS, TLS/SSL, or None. Port 587 commonly uses StartTLS and port 465 commonly uses TLS/SSL, but follow your provider's instructions.
    SMTP UsernameAuthentication username, when required.
    SMTP PasswordAuthentication password, when required.
    TimeoutOptional send timeout in seconds.
  4. Check the values against your provider's documentation. A mismatched port and encryption option prevents Coolify from connecting.

  5. Select Save in the SMTP Server section.

  6. Turn on Enabled for SMTP. Coolify disables Resend when SMTP is enabled.

Do not use unencrypted SMTP over an untrusted network

Choose None only when your email provider explicitly requires it and the connection stays on a trusted network. Prefer an encrypted option supported by the provider.


Choose events and verify delivery

Under Notification Settings, select the events to send by email. See Notification events for the trigger behind each setting.

Select Send Test Email, enter a recipient address you can access, and send the test. Confirm that the message arrives. If it does not, check the provider's activity logs, sender verification, SMTP port access, and spam folder.


Troubleshoot email delivery

If the test email does not arrive:

  1. Confirm that the intended provider is enabled. SMTP, Resend, and the hosted or system-wide option are mutually exclusive.
  2. For SMTP, compare the host, port, and encryption method with the provider's current settings. Also confirm that the Coolify server can make outbound connections on that port.
  3. Check whether the provider requires the From Address or its domain to be verified.
  4. Check the provider's delivery or activity logs. An accepted request can still be rejected later because of sender policy or recipient filtering.
  5. Check the recipient's spam or junk folder.
  6. When using the self-hosted system-wide provider, send a test from Settings > Email. If that test also fails, fix the instance provider before troubleshooting the team channel.

On this page