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 Email service > Use system-wide 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:

Provider	Availability	What you need
Use hosted email service	Coolify Cloud	No provider credentials.
Use system-wide settings	Self-hosted Coolify	A working email provider under Settings > Email.
SMTP server	Coolify Cloud and self-hosted Coolify	SMTP sender, host, port, encryption, and optional authentication details.
Resend	Coolify Cloud and self-hosted Coolify	A 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 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 set Email service to Use system-wide 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 events. Then select Send test, 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.

Open Notifications > Email and set Email service to Use team email settings.
Enter From name and a valid From address. Both are required. If either is empty, saving fails with an error such as From Address is required. (and 1 more error).

Under SMTP server, enter the connection details supplied by your email provider:

Field	Value
Host	SMTP hostname, such as `smtp.example.com`.
Port	Provider's SMTP port. Common values are `587`, `465`, and `25`; Coolify accepts ports from `1` to `65535`.
Encryption	`StartTLS`, `TLS/SSL`, or `None`. Port `587` commonly uses StartTLS and port `465` commonly uses TLS/SSL, but follow your provider's instructions.
SMTP username	Authentication username, when required.
SMTP password	Authentication password, when required.
Timeout	Optional send timeout in seconds.
EHLO domain	Optional fully qualified domain Coolify sends in the SMTP `EHLO` command, such as `coolify.example.com`. Leave it empty to use the system default.

Check the values against your provider's documentation. A mismatched port and encryption option prevents Coolify from connecting.
Select Save changes in the SMTP server section.
Set SMTP delivery to Enabled and select Save changes. 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 events, select the events to send by email. See Notification events for the trigger behind each setting.

Select Send test, 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.

Include commit details in deployment emails

Deployment success and failure emails can show the commit that Coolify deployed. This setting is off by default.

To enable it, open Notifications > Email and select Include commit details in deployment emails below Notification events. Coolify saves the change immediately. Only team admins and owners can change this setting.

When the setting is on, deployment emails show:

Item	Description
Commit	The first 7 characters of the commit SHA.
Commit link	The SHA links to the commit page of the Git provider when Coolify can make a link. Coolify uses the URL of the Git source, or the HTTP(S) or SSH repository URL. Bitbucket links use the `/commits/` path. If Coolify cannot make a link, the SHA shows as text.
Branch	The branch of the application, after the SHA (for example, `on main`). Pull request preview deployments do not show the branch.
Commit message	The commit message as plain text. Coolify does not render Markdown or HTML from the message, and it shortens messages that are longer than 1,000 characters.

If a deployment has no commit SHA and no commit message, the email does not show the commit block. For example, this occurs when the deployment uses HEAD instead of a specific commit.

Email only

This setting changes only deployment emails. Discord, Telegram, Slack, Pushover, and webhook notifications do not use it.

To change the setting with the API, send deployment_commit_details_email_notifications (true or false) in a PATCH request to /api/v1/notifications/email. The API token must have the write permission. A GET request to the same endpoint returns the current value.

Troubleshoot email delivery

If the test email does not arrive:

Confirm that the intended provider is enabled. SMTP, Resend, and the hosted or system-wide option are mutually exclusive.
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.
Check whether the provider requires the From address or its domain to be verified.
Check the provider's delivery or activity logs. An accepted request can still be rejected later because of sender policy or recipient filtering.
Check the recipient's spam or junk folder.
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