How Do I Alert Different Teams Using Multiple Integrations From the Same Provider?

This guide will cover step-by-step instructions and suggestions for a specific use case: the same integration provider can be used to send alerts to different teams or users based on the check. 

This approach is useful when your organization uses a single notification service (like Slack, PagerDuty, or Teams) but needs to send alerts to different channels, users, or departments based on the check being monitored. We'll walk through creating multiple integrations with the same provider, connecting each integration to a dedicated contact, and assigning these contacts to specific checks or escalation policies. Following this process ensures that alerts reach the right people without overwhelming other team members with unnecessary notifications.

Creating Multiple Integrations With the Same Provider

The first step is to set up multiple integrations using the same provider but with different credentials or configurations. Access the Integrations screen by clicking Notification > Integrations, then click Add next to the integration you’ll be creating. 

The Add Integration pop-up for your chosen integration appears. Set up your integration according to its specific instructions; you can find a list of all available integrations, with links to their setup documentation, at our document Overview of Push Notifications.

Each integration provider has a unique setup process, along with a method of identifying that specific integration channel. This is how you will differentiate between individual integration setups that will be used when assigning them to a team or user. For example, several integration providers use a unique key or ID, such as the Webhook URL and Channel used by Slack:

When setting up the same provider to send individual alerts to different team members, you’ll want to set up an integration for each team member or group so that they can be assigned with the appropriate granularity. Here are some best practices to consider when creating multiple integrations with the same provider:

• Give each integration a descriptive name that clearly identifies its purpose or assigned user. For example, if you're creating multiple Slack integrations, name them "Slack - NOC Team," "Slack - DevOps Team," or "Slack - Management Alerts" to quickly distinguish between them when you’re assigning them to contacts.
• Each integration will require its own set of credentials or configuration settings. For example, Slack integrations will each need a separate webhook URL pointing to different channels. For PagerDuty, each integration requires a unique key tied to different services or escalation policies within your PagerDuty account.
• You can create an unlimited number of integrations from the same provider, so don't hesitate to create as many as needed to segment your alerting.

Connecting Integrations to Contacts

Once you've created your integrations, the next step is to create dedicated contacts that utilize each integration. Navigate to Notification > Contacts and click New Contact. If the contact already exists, click the Edit button next to the contact name. When configuring the contact, select the appropriate integration from the Integrations drop-down menu:

Contacts can be created with multiple alerting channels, such as email, phone/SMS, or integration, or they can be created with any combination of alerting methods. In this use case, create an individual contact only for each integration setup; since we’re focused specifically on integrations, there is no need to also add email or phone/SMS alerting to these integration-only contacts.

Following are some best practices for linking integrations to contacts:

• In this use case of alerting multiple teams from the same provider, keep a one-to-one association between the contact and integration.. This makes it easier to understand which checks are alerting which teams.
• Use naming conventions that mirror your integration names. If your integration is called "Slack - NOC Team," name the contact "NOC Team - Slack" or similar. This will make it easier to see associations at a glance.
• Even though you have multiple contacts using the same integration provider, each contact should be configured with a different integration setup that was created in the previous step.

Assigning Contacts to Specific Checks

With your integrations and contacts configured, you can now assign them to the appropriate checks. Add contacts to individual checks by creating or editing the check and navigating to the General tab, under the Notifications & Metadata section:

Click the Contacts drop-down and select the appropriate integration contacts that should be associated with the check. Remember there is no limit to the number of contacts that can be associated with a check, so you can add as many as necessary depending on the teams or users that should be alerted.

Here are some best practices for assigning contacts to your checks:

• Use Tags to group checks by team, website, or environment. This allows you to filter checks on the Monitoring page and assign contacts to relevant checks in bulk.
• Review your check configurations periodically to ensure contacts are assigned correctly, especially when new sites are added or teams change.
• You can also add contacts to checks in bulk. Select multiple checks from the Monitoring page by checking the box next to them, then click More Actions > Set Contacts: