Manage notification destinations

This article teaches you how to create and configure notification destinations for your workspace.

System notifications are messages that tell you when your workflow experiences a run event (start, success, and failure). By default, notifications are sent to user email addresses, but admins can configure alternate notification destinations using webhooks. This allows you to build event-driven integrations with Databricks.

You must be a Databricks workspace admin to manage notification destinations. After a destination is configured, it is available to all users.

Networking requirements

• The notification destination must add the workspace control plane webapp IP addresses to its allowlist. See IP addresses and domains for Databricks services and assets.
• Databricks enforces the use of HTTPS for security. The notification destination must use Secure Sockets Layer (SSL) certificates signed by a trusted certificate authority.

Create a new notification destination

To configure a new notification destination

1. Click your username in the top bar of the workspace and select Settings from the dropdown.
2. In the Workspace admin section, click the Notifications tab.
3. Click the Manage button.
4. Click +Add destination.
5. Select a destination type. The following destinations are currently supported:
   • Email
   • Slack
   • Webhook
   • MS Teams
   • PagerDuty
6. Configure the destination based on the type.
7. Click Create.

Use different credentials for each destination

The configuration of a destination is securely stored encrypted in your Databricks workspace. To improve security if the third-party endpoint is compromised, Databricks recommends using different credentials for each configured destination. These include:

• Slack: the URL to which the notification is sent.
• MS Teams: the URL to which the notification is sent.
• PagerDuty: integration key used to uniquely route notifications to a PagerDuty service.
• Webhook: username and password used to authenticate to a third party endpoint using HTTP Basic authentication when delivering notifications.

Using different secrets for each configured destination allows you to individually revoke access of individual notification destinations without impacting the operation of all other destinations in your Databricks workspace.

Slack destination

To set up a Slack destination, follow the instructions in Incoming webhooks for Slack. Paste the generated URL into your Databricks notification destination.

Add a webhook to a job

After configuring destinations, you can access them in a job's Job notifications settings. For more information, see Add notifications on a job.

Each job supports up to three system destinations per event type. When configuring job notifications, email addresses must be entered manually.

Limitations

Notification destinations currently has the following limitations:

• You can only configure notifications for Databricks SQL and jobs.
• Email notification destinations have a 1,300-character limit on the recipient address length.
• For custom notification bodies, non-email destinations such as Slack and MS Teams do not support HTML formatting. Some notification destinations support markdown.
• For jobs, email destinations must be manually set in the job's settings.