Outgoing e-mails

Send incident notifications to any external e-mail address. Keep clients, stakeholders, or a distribution list in the loop when an incident starts, without giving them a Better Stack seat.

Using outgoing e-mails with Uptime

  1. Go to Uptime → Integrations → Exporting data and find the Outgoing e-mails section.
  2. Click Add.
  3. Give the integration a name you'll recognize later.
  4. Under Who should we notify?, add one recipient e-mail per line, or upload a CSV to import many at once.
  5. Choose which events send an e-mail, optionally customize the message, and click Create integration.

Choosing when to notify

Under When should we send the e-mail?, pick which incident events trigger a notification:

  • New incident is started
  • Incident is acknowledged
  • Incident is resolved
  • Incident is reopened
  • New comment is added

Enable Notify alongside the primary responder to also e-mail your recipients when no escalation policy is configured.

Adding recipients

List one recipient e-mail per line, or upload a CSV to add many at once. The sample CSV uses email, first_name, and team columns, and you can insert any column into your templates with $RECIPIENT.column, for example $RECIPIENT.first_name.

Customizing the e-mail

Under Customize the sent e-mails, tailor the Subject, Title, and Content for each event: Started, Acknowledged, Resolved, Reopened, and New comment. Leave a field empty to use the default.

Insert incident details with variables such as $NAME, $STATUS, $CAUSE, and $INCIDENT_URL. Insert a single metadata value with $METADATA.Key, or all of it with $METADATA_ARRAY. The incidents API documentation lists every available variable.

You can also override any template for a specific incident by adding email_subject, email_title, or email_content to the incident's metadata.

Need help?

Please let us know at hello@betterstack.com. We're happy to help. 🙏