Documentation / Integrations

Email server (SMTP)

Sets the outbound mail server that Helm uses for alerts, user invitations and password resets.

Email server connection form, Authentication set to Password
Email server connection form, Authentication set to Password

Set up

  1. Open Integrations in the navigation for your role.
  2. Choose Add integration, then select Email server (SMTP).
  3. Enter Authentication: Password, OAuth 2.0 (Microsoft 365) or OAuth 2.0 (Google Workspace); With Password: SMTP host, port, encryption, username and password; With Microsoft 365: directory (tenant) ID, client ID, client secret, refresh details; With Google Workspace: client ID, client secret, refresh token; From address.
  4. Choose Connect. Helm tests the connection before it saves the integration.

If the test fails, you can choose Save without verifying. The integration is then saved with an error status until you fix it.

What the screen shows

The first choice is the authentication method, and the form changes to match it. Password shows the host, port (587 by default) and encryption options. Microsoft 365 and Google Workspace show OAuth fields instead. The from address is shown on every outgoing message.

Notes

  • Microsoft 365 and Google Workspace tenants usually require OAuth 2.0 for SMTP. Choose it instead of a password.
  • The Microsoft app registration needs the SMTP.Send permission.
  • The refresh token for Google Workspace must be issued for the mail.google.com scope.

Last updated

Was this page helpful?Contact support