Notifications for OnCall OSS on Grafana Labs

Phone calls and SMS notifications

Fri, 03 Apr 2026 16:45:36 +0000

Phone and SMS notifications for Grafana OnCall OSS

Warning
As of March 24, 2026, Cloud Connection features for phone calls, SMS, and push notifications will no longer be supported in Grafana OnCall OSS.

To learn more about this update, refer to the Maintenance mode notice for Grafana OnCall (OSS)

To ensure uninterrupted notifications, OnCall OSS users must set up phone and SMS notifications using one of these alternatives:

Use a third-party provider – Configure Twilio, Exotel, or Zvonok to send SMS and phone calls
Use webhooks – Set up OnCall to trigger custom SMS and call workflows via self-hosted solutions

This guide provides step-by-step instructions for configuring phone and SMS notifications using third-party providers.

Configure Twilio for OnCall OSS

To configure notifications with Twilio, you’ll need the following:

A Twilio account (sign up at twilio.com)
A Twilio phone number with SMS and Voice capabilities
API credentials (Account SID and Auth Token)
Administrator access to your Grafana OnCall OSS instance

Set up a Twilio phone number

Log in to Twilio Console
Navigate to Phone Numbers > Buy a Number
Ensure the number supports SMS and Voice
Copy your Account SID and Auth Token from the Twilio dashboard

Configure an outgoing webhook in OnCall

In Grafana OnCall OSS, go to Outgoing Webhooks
Click + Outgoing Webhook
Configure the webhook:
- URL: https://api.twilio.com/2010-04-01/Accounts/YOUR_TWILIO_SID/Messages.json
- Method: POST
- Headers:

{
  "Authorization": "Basic BASE64_ENCODED(TWILIO_SID:TWILIO_AUTH_TOKEN)",
  "Content-Type": "application/x-www-form-urlencoded"
}

Body (for SMS notifications):

{
  "From": "+YOUR_TWILIO_NUMBER",
  "To": "{{ user_phone }}",
  "Body": "New OnCall Alert: {{ alert_title }}"
}

Body (for phone call notifications):

{
  "From": "+YOUR_TWILIO_NUMBER",
  "To": "{{ user_phone }}",
  "Url": "https://handler.twilio.com/twiml/EHXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
}

Click Save & test to verify the configuration

Your OnCall notifications should now be sent via Twilio.

Configure Exotel for OnCall OSS

To configure notifications with Exotel, you’ll need the following:

An Exotel account (sign up at exotel.com)
API credentials (SID, API Key, and Auth Token)

Set up Exotel API credentials

Log in to Exotel Dashboard
Navigate to API Settings
Generate and copy the SID, API Key, and Auth Token

Configure an outgoing webhook in OnCall

In Grafana OnCall OSS, go to Outgoing Webhooks
Click + Outgoing Webhook
Configure the webhook:
- URL: https://api.exotel.com/v1/Accounts/YOUR_EXOTEL_SID/Sms/send
- Method: POST
- Headers:

{
  "Authorization": "Basic BASE64_ENCODED(EXOTEL_SID:EXOTEL_AUTH_TOKEN)",
  "Content-Type": "application/x-www-form-urlencoded"
}

Body (for SMS notifications):

{
  "From": "YOUR_EXOTEL_VIRTUAL_NUMBER",
  "To": "{{ user_phone }}",
  "Body": "New OnCall Alert: {{ alert_title }}"
}

Body (for phone call notifications):

{
  "From": "YOUR_EXOTEL_VIRTUAL_NUMBER",
  "To": "{{ user_phone }}",
  "CallerId": "YOUR_EXOTEL_CALLER_ID",
  "CallType": "trans"
}

Click Save & test to verify the configuration

Your OnCall notifications should now be sent via Exotel.

Configure Zvonok for OnCall OSS

To configure notifications with Zvonok, you’ll need the following:

Follow Zvonok’s documentation to create an API endpoint for sending SMS and calls
Configure Outgoing Webhook in OnCall using Zvonok’s API URL and required parameters
Test the setup to verify that phone/SMS notifications are working

Next steps

If you also use push notifications via Cloud Connection, refer to the Push Notification guide
Update your notification workflows before March 24, 2026 to ensure a smooth transition
Test your configuration to verify successful alert delivery

SMS notification behavior

OnCall reduces alert noise and distraction by bundling SMS notifications. When multiple alert groups require notification within a short period, the first alert group triggers an immediate SMS. A 2-minute “waiting period” follows, during which additional alerts are bundled. After this period, a single SMS with all alert information is sent.

Notifications are bundled based on their importance. Alerts from “default” and “important” notification policies are bundled separately.

Example bundled notification

If a user needs to be notified about 5 alert groups from 2 different integrations (3 from “Grafana Alerting” and 2 from “Health Check”), they will receive an immediate notification for the first alert group and a bundled SMS for the remaining alerts after 2 minutes:

Example bundled notification text:

Grafana OnCall: Alert groups #101, #102, #103 and 1 more, from stack: TestOrg, integrations: GrafanaAlerting and 1 more.

Route incoming calls to the on-call engineer

For guidance on configuring incoming call routing, refer to our documentation and blog post.

About phone call and SMS notifications

Please note the following about phone calls and SMS notifications:

Additional costs: There are no additional costs for outgoing calls or SMS notifications
Rate limits: There are no specific rate limits, but we reserve the right to stop sending SMS/calls in case of abnormal volume
Grafana OnCall phone numbers: To learn the phone number used by OnCall, make a test call from the “Phone Verification” tab

Country support for SMS/Voice

Note
Be aware that due to limitations in telecom provider services, some numbers within supported countries may occasionally be flagged as “high-risk” when verifying your phone number, preventing you from receiving notifications.

Ensure that you test your notification rules to confirm that OnCall can reach you. For added reliability, consider backing up phone calls and SMS notifications with additional methods, such as push notifications.

Refer to the following list for countries currently supported by Grafana IRM for SMS and phone notifications:

Country	SMS/Voice Support
Andorra (+376)	✅
Albania (+355)	✅
Austria (+43)	✅
Aland Islands (+35818)	✅
Bosnia and Herzegovina (+387)	✅
Belgium (+32)	✅
Bulgaria (+359)	✅
Belarus (+375)	✅
Switzerland (+41)	✅
Czechia (+420)	✅
Germany (+49)	✅
Denmark (+45)	✅
Estonia (+372)	✅
Spain (+34)	✅
Finland (+358)	✅
Faroe Islands (+298)	❌
France (+33)	✅
United Kingdom (+44)	✅
Guernsey (+441481)	✅
Gibraltar (+350)	✅
Greece (+30)	✅
Croatia (+385)	✅
Hungary (+36)	✅
Ireland (+353)	✅
Isle Of Man (+441624)	✅
Iceland (+354)	✅
Italy (+39)	✅
Jersey (+441534)	✅
Liechtenstein (+423)	❌
Lithuania (+370)	✅
Luxembourg (+352)	✅
Latvia (+371)	✅
Monaco (+377)	❌
Moldova (Republic of) (+373)	✅
Montenegro (+382)	✅
North Macedonia (Republic of North Macedonia) (+389)	✅
Malta (+356)	✅
Netherlands (+31)	✅
Norway (+47)	✅
Poland (+48)	✅
Portugal (+351)	✅
Romania (+40)	✅
Serbia (+381)	✅
Russian Federation (+7)	✅
Sweden (+46)	✅
Slovenia (+386)	✅
Svalbard and Jan Mayen Islands (+4779)	✅
Slovakia (+421)	✅
San Marino (+378)	❌
Turkey (+90)	✅
Ukraine (+380)	✅
Holy See (Vatican City State) (+3906698)	❌
Kosovo (+383)	❌

Country	SMS Support
United Arab Emirates (+971)	✅
Afghanistan (+93)	❌
Armenia (+374)	❌
Azerbaijan (+994)	❌
Bangladesh (+880)	❌
Bahrain (+973)	✅
Brunei Darussalam (+673)	✅
Bhutan (+975)	✅
Cocos (Keeling) Islands (+672)	✅
China (+86)	❌
Christmas Island (+6189164)	✅
Cyprus (+357)	✅
Georgia (+995)	✅
Hong Kong (Special Administrative Region of China) (+852)	✅
Indonesia (+62)	✅
Israel (+972)	✅
India (+91)	✅
British Indian Ocean Territory (+246)	❌
Iraq (+964)	❌
Iran (Islamic Republic of) (+98)	❌
Jordan (+962)	❌
Japan (+81)	✅
Kyrgyzstan (+996)	❌
Cambodia (+855)	❌
Democratic People`s Republic of Korea (+850)	❌
Republic of Korea (+82)	✅
Kuwait (+965)	❌
Kazakhstan (+7)	✅
Lao People`s Democratic Republic (+856)	❌
Lebanon (+961)	❌
Sri Lanka (+94)	❌
Myanmar (+95)	❌
Mongolia (+976)	❌
Macau (Special Administrative Region of China) (+853)	✅
Maldives (+960)	✅
Malaysia (+60)	✅
Nepal (+977)	❌
Oman (+968)	❌
Philippines (+63)	✅
Pakistan (+92)	❌
Palestinian Territory (Occupied) (+970)	❌
Qatar (+974)	✅
Saudi Arabia (+966)	✅
Singapore (+65)	✅
Syrian Arab Republic (+963)	❌
Thailand (+66)	✅
Tajikistan (+992)	❌
Timor-Leste (East Timor) (+670)	❌
Turkmenistan (+993)	❌
Taiwan (Province of China) (+886)	✅
Uzbekistan (+998)	❌
Vietnam (+84)	❌
Yemen (+967)	❌

Country	SMS Support
Antigua and Barbuda (+1268)	❌
Anguilla (+1264)	❌
Netherlands Antilles (+599)	✅
Aruba (+297)	✅
Barbados (+1246)	✅
Saint Barthelemy (+590)	✅
Bermuda (+1441)	✅
Bonaire, Sint Eustatius And Saba (+5993)	✅
Bahamas (+1242)	✅
Belize (+501)	❌
Canada (+1)	✅
Costa Rica (+506)	✅
Cuba (+53)	✅
Dominica (+1767)	❌
Dominican Republic (+1809)	✅
Grenada (+1473)	❌
Greenland (+299)	❌
Guadeloupe (+590)	❌
Guatemala (+502)	✅
Honduras (+504)	❌
Haiti (+509)	✅
Jamaica (+1876)	✅
Saint Kitts and Nevis (+1869)	❌
Cayman Islands (+1345)	✅
Saint Lucia (+1758)	❌
Saint Martin French (+590)	❌
Martinique (+596)	❌
Montserrat (+1664)	❌
Mexico (+52)	✅
Nicaragua (+505)	✅
Panama (+507)	✅
Saint Pierre and Miquelon (+508)	❌
Puerto Rico (+1787)	✅
El Salvador (+503)	❌
Sint Maarten Dutch (+1721)	✅
Turks and Caicos Islands (+1649)	❌
Trinidad and Tobago (+1868)	✅
United States (+1)	✅
Saint Vincent and the Grenadines (+1784)	❌
Virgin Islands British (+1284)	❌
Virgin Islands US (+1340)	❌

Country	SMS Support
Argentina (+54)	✅
Bolivia (+591)	❌
Brazil (+55)	✅
Chile (+56)	✅
Colombia (+57)	✅
Ecuador (+593)	✅
Falkland Islands (Malvinas) (+500)	❌
French Guiana (+594)	❌
Guyana (+592)	❌
Peru (+51)	✅
Paraguay (+595)	✅
Suriname (+597)	✅
Uruguay (+598)	✅
Venezuela (+58)	✅

Country	SMS Support
Angola (+244)	❌
Burkina Faso (+226)	✅
Burundi (+257)	❌
Benin (+229)	❌
Botswana (+267)	✅
Democratic Republic of the Congo (+243)	❌
Central African Republic (+236)	❌
Congo (+242)	❌
Cote d`Ivoire (+225)	✅
Cameroon (+237)	❌
Cape Verde (+238)	✅
Djibouti (+253)	✅
Algeria (+213)	❌
Egypt (+20)	❌
Western Sahara (+212)	✅
Eritrea (+291)	❌
Ethiopia (+251)	❌
Gabon (+241)	❌
Ghana (+233)	❌
Gambia (+220)	❌
Guinea (+224)	❌
Equatorial Guinea (+240)	❌
Guinea-Bissau (+245)	❌
Kenya (+254)	✅
Comoros (+269)	❌
Liberia (+231)	❌
Lesotho (+266)	❌
Libyan Arab Jamahiriya (+218)	❌
Morocco (+212)	❌
Madagascar (+261)	❌
Mali (+223)	❌
Mauritania (+222)	✅
Mauritius (+230)	❌
Malawi (+265)	❌
Mozambique (+258)	✅
Namibia (+264)	✅
Niger (+227)	❌
Nigeria (+234)	✅
Reunion (+262)	❌
Rwanda (+250)	❌
Seychelles (+248)	❌
Sudan (+249)	❌
Saint Helena (+290)	✅
Sierra Leone (+232)	❌
Senegal (+221)	❌
Somalia (+252)	✅
South Sudan (+211)	❌
Sao Tome and Principe (+239)	❌
Swaziland (+268)	✅
Chad (+235)	❌
Togo (+228)	✅
Tunisia (+216)	✅
Tanzania (United Republic of) (+255)	✅
Uganda (+256)	✅
Mayotte (+262269)	✅
South Africa (+27)	✅
Zambia (+260)	❌
Zimbabwe (+263)	❌

Country	SMS Support
American Samoa (+1684)	❌
Australia (+61)	✅
Cook Islands (+682)	❌
Curacao (+5999)	✅
Fiji (+679)	✅
Micronesia (Federated States of) (+691)	❌
Guam (+1671)	✅
Kiribati (+686)	❌
Marshall Islands (+692)	❌
Northern Mariana Islands (+1670)	✅
New Caledonia (+687)	✅
Norfolk Island (+672)	✅
Nauru (+674)	❌
Niue (+683)	❌
New Zealand (+64)	✅
French Polynesia (+689)	✅
Papua New Guinea (+675)	❌
Pitcairn (+64)	✅
Palau (+680)	❌
Solomon Islands (+677)	❌
Tokelau (+690)	✅
Tonga (+676)	❌
Tuvalu (+688)	❌
United States Minor Outlying Islands (+1)	✅
Vanuatu (+678)	❌
Wallis and Futuna Islands (+681)	❌
Samoa (+685)	❌

Country	SMS Support
Antarctica (+672)	✅
Bouvet Island (+47)	✅
South Georgia and The South Sandwich Islands (+500)	✅
Heard Island and McDonald Islands (+61)	✅
French Southern Territories (+1)	✅

For a comprehensive list of all supported countries, please visit the Twilio international coverage page.

Configure push notifications for Grafana OnCall OSS

Fri, 03 Apr 2026 16:45:36 +0000

Configure push notifications for Grafana OnCall OSS

Grafana OnCall OSS allows you to set up a personal notification webhook, which provides flexibility and control over how you receive push notifications.

To enable push notifications as a notification method, you can configure a webhook to send notifications via a third-party push notification service, such as Pushover, ntfy, or Gotify.

Configure webhooks for push notifications

The personal notification webhook feature allows you to configure customized notifications based on your preferred push notification provider. The configuration process is similar across push notification services like Pushover, Gotify, or ntfy.

Choose a push notification provider

Pushover – Third-party push notification service.
ntfy – Open-source push notification service.
Gotify – Self-hosted push notification server.

Create an outgoing webhook in OnCall OSS

Navigate to Outgoing Webhooks in Grafana OnCall OSS.
Click + Outgoing Webhook, then select Advanced.
Set the Trigger Type to Personal Notification.
Configure the webhook:
- URL: Enter the URL for your chosen push notification service.
- Method: POST
- Headers: (Optional, based on service requirements.)
- Body: Ensure the message format aligns with the selected service.
Click Save.

Tip
Define your webhook using templates where needed so that each user can personalize it by providing their own values via the context in their profile. Templating can be applied to different parts of the webhook configuration, such as the URL, headers, or body payload. Depending on the service you are integrating with, you may need to template a specific field (e.g., setting a payload field referencing the user ID or a header with a specific key). See examples below.

Assign the webhook as a personal notification channel

Navigate to your User Profile.
Under Notification Channels, click Connect for Webhook.
On the Webhook Connection tab, select the webhook created in the previous step.
If you used a templated webhook URL, define your JSON key/value in the Context section.
Add the webhook as a notification step in your notification rules.

Once configured, notifications from OnCall OSS will be sent through the webhook to your chosen push notification provider. Ensure all necessary configurations are completed with your provider.

Example: Configure Pushover for OnCall OSS

Before you begin, ensure you have:

A Pushover account (sign up at pushover.net).
The Pushover mobile app installed and configured (iOS/Android). Ensure notifications are enabled and can override Do Not Disturb (DnD) mode if needed.
A Pushover API token (generated from the Pushover website).
Administrator access to your Grafana OnCall OSS instance.

Create a Pushover application

Log in to Pushover.
Navigate to Apps & Plugins > Create an Application.
Enter an Application Name (e.g., Grafana OnCall Alerts).
Copy and save the API token provided.

Configure an outgoing webhook in OnCall

In Grafana OnCall OSS, go to Outgoing Webhooks.
Click + Outgoing Webhook, then select Advanced.
Set the Trigger Type to Personal Notification.
Configure the webhook:
- URL: https://api.pushover.net/1/messages.json
- Method: POST
- Headers:

{
  "Content-Type": "application/json"
}

Body:

{
  "token": "YOUR_PUSHOVER_APP_TOKEN",
  "user": "USER_KEY",
  "message": "New Alert: {{ alert_title }}",
  "title": "Grafana OnCall Alert"
}

Replace YOUR_PUSHOVER_APP_TOKEN with your Pushover API token.
Replace USER_KEY with your personal Pushover key.
Click Save & test to verify the configuration.

Assign the webhook as a personal notification channel

Navigate to User Profile.
Under Notification Channels, click Connect for Webhook.
Select the webhook created in the previous step from the dropdown.
(Optional) Provide additional context data for webhook templates in JSON key/value pair.
Add the webhook as a notification step in your notification rules.

Example: Configure push notifications with ntfy

ntfy is an open-source push notification service that allows you to send notifications via REST API. A simple message can be sent using:

curl -d "Backup successful 😀" ntfy.sh/mytopic

For more customization options, refer to the ntfy documentation.

Set up an outgoing webhook for ntfy

Tip
Use a templated webhook URL to configure your webhook to be reused by multiple users. This allows users to set that value according to their personal information (i.e. the ntfy topic in our example).

In Grafana OnCall OSS, click + Outgoing Webhook, then select Advanced.
Set the Trigger Type to Personal Notification.
Configure the webhook:
- URL: https://ntfy.sh/{{ user_defined_topic }}
- Method: POST
- Headers:

{
  "Title": "Grafana OnCall Alert",
  "Priority": "5"
}

Body:

{
  "message": "New Alert: {{ alert_title }}"
}

Click Save.

Once configured, each user can set up a new notification channel in their profile and provide a ntfy_topic key with their desired topic name as the value.

Assign the webhook as a personal notification channel

Navigate to User Profile.
Under Notification Channels, click Connect for Webhook.
Select the webhook created in the previous step.
In the Context section, define your ntfy_topic as a JSON key/value pair.
Add the webhook as a notification step in your notification rules.

Webhook as personal notification channel

Fri, 03 Apr 2026 16:45:36 +0000

Webhook as a personal notification channel

It is possible to setup a webhook as a personal notification channel in your user profile. The webhook will be triggered as a personal notification rule according to your notification policy configuration.

Configure a webhook to be used as personal notification

In the webhooks page, you (or a user with the right permissions) need to define a webhook as usual, but with the Personal Notification trigger type.

Each user will then be able to choose a webhook (between those with the above trigger type) as a notification channel in their profile. Optionally, they can also provide additional context data (as a JSON dict, e.g. {"user_ID": "some-id"}) which will be available when evaluating the webhook templates. This data can be referenced via {{ event.user.<key> }} (e.g. {{ event.user.user_ID }}).

MS Teams integration for Grafana OnCall

Fri, 03 Apr 2026 16:45:36 +0000

MS Teams integration for Grafana OnCall

Note
This integration is available exclusively on Grafana Cloud.

The Microsoft Teams integration for Grafana OnCall embeds your MS Teams channels directly into your incident response workflow to help your team focus on alert resolution.

Integrating MS Teams with Grafana OnCall allows users to be notified of alerts directly in MS Teams with automated escalation steps and user notification preferences. Users can also take action on alerts directly from MS Teams, including acknowledge, unacknowledge, resolve, and silence.

Before you begin

The following is required to connect to Microsoft Teams to Grafana OnCall:

You must have Admin permissions in your Grafana Cloud instance.
You must have Owner permissions in Microsoft Teams.
Install the Grafana IRM app from the Microsoft Marketplace.

Connect Microsoft Teams with Grafana OnCall

Note
A Microsoft Teams workspace can only be connected to one Grafana Cloud instance and cannot be connected to multiple environments.

To connect Microsoft Teams with Grafana OnCall:

In Grafana OnCall, open Settings and click Chat Ops.
From the Chat Ops tab, select Microsoft Teams in the side menu.
Follow the in-app instructions to add the Grafana IRM app to your Teams workspace.
After your workspace is connected, copy and paste the provided code into a Teams channel to add the IRM bot, then click Done.
To add additional channels click +Add MS Teams channel and repeat step 3 as needed.

Post-install configuration for Microsoft Teams integration

Configure the following settings to ensure Grafana OnCall alerts are routed to the intended Teams channels and users:

Set a default channel from the list of connected MS Teams channels. This is where alerts will be sent unless otherwise specified in escalation chains.
Ensure all users verify their MS Teams account in their Grafana OnCall user profile.

Connect Microsoft Teams user to Grafana OnCall

From the Users tab of Grafana OnCall, click View my profile.
In the User Info tab, locate Notification channels, MS Teams, and click Connect account.
Follow the steps provided to connect your Teams user.
Navigate back to your Grafana OnCall profile and verify that your Microsoft Teams account is linked to your Grafana OnCall user.

Configure user notifications with Microsoft Teams

To be notified of Grafana OnCall alerts via MS Teams:

Navigate to the Users tab in Grafana OnCall, click Edit next to a user.
In the User Info tab, edit or configure notification steps by clicking +Add Notification step
Select Notify by in the first dropdown and select Microsoft Teams in the second dropdown to receive alert notifications in Teams.

Configure escalation chains to post to Microsoft Teams channels

Once your MS Teams integration is configured you can add an escalation step at the integration level to automatically send alerts from a specific integration to a channel in MS Teams.

To automatically send alerts from an integration to MS Teams channels:

Navigate to the Integrations tab in Grafana OnCall, select an existing integration or click +New integration to receive alerts.
From the integrations settings, navigate to the escalation chain panel.
Enable Post to Microsoft Teams channel by selecting a channel to connect from the dropdown.

Slack integration for Grafana OnCall

Fri, 03 Apr 2026 16:45:36 +0000

Slack integration for Grafana OnCall

Warning
The OnCall Slack app is now a Grafana IRM app with new incident management features. Migrate now to access the enhanced capabilities.

Refer to the Grafana IRM Slack integration documentation to learn more.

The Slack integration for Grafana OnCall incorporates your Slack workspace directly into your incident response workflow to help your team focus on alert resolution with less friction.

Integrating your Slack workspace with Grafana OnCall allows users and teams to be notified of alerts directly in Slack with automated alert escalation steps and user notification preferences. There are a number of alert actions that users can take directly from Slack, including acknowledge, resolve, add resolution notes, and more.

Before you begin

To install the Slack integration, you must have Admin permissions in your Grafana instance as well as the Slack workspace that you’d like to integrate with.

For Open Source Grafana OnCall Slack installation guidance, refer to Slack setup.

Install Slack integration for Grafana OnCall

Navigate to Settings tab in Grafana OnCall.
From the Chat Ops tab, select Slack in the side menu.
Click Install Slack integration.
Read the notice and agree to proceed to the Slack website.
Provide your Slack workspace URL and sign with your Slack credentials.
Click Allow to give Grafana OnCall permission to access your Slack workspace.

Configure timeout for acknowledged alerts

You can configure reminders for acknowledged alerts in the Additional settings section of the Chat Ops tab. This section allows you to enable reminders to be sent through Slack at set intervals. You can also choose to have an alert group revert to unacknowledged after a designated period of time if the reminder is not confirmed.

Why does OnCall Slack App require so many permissions?

OnCall has an advanced Slack App with dozens of features making it even possible for users to be on-call and work with alerts completely inside Slack. The drawback is that our Slack bot requires a lot of permissions and some of those permissions may sound suspicious, so we commented on them to give you more context.

Content and info about you

The bot is using those permissions to receive Slack handles and avatars. Those permissions are supporting account matching between Grafana and Slack.

View information about your identity
View profile details about people in your workspace

Content and info about channels & conversations

View basic information about public channels in your workspace — this permission is supporting channel selectors in the integration settings so the user could choose where to send Alert Groups.
View messages and other content in public channels, private channels, direct messages, and group direct messages that Grafana OnCall has been added to — this permission is supporting a feature of adding messages to the resolution notes in the Alert Group’s Slack thread.
View basic information about private channels that Grafana OnCall has been added to — this permission allows to add a slack bot to the private channel and make it selectable in the list of channels. So users will be able to route Alert Groups to the private channels.
View basic information about direct messages that Grafana OnCall has been added to

Content and info about your workspace

This set of permissions is supporting the ability of Grafana OnCall to match users with Grafana users.

View people in your workspace
View email addresses of people in your workspace
View the name, email domain, and icon for workspaces Grafana OnCall is connected to
View user groups in your workspace
View profile details about people in your workspace

Perform actions in channels & conversations

View messages that directly mention @grafana_oncall in conversations that the app is in
Join public channels in your workspace
Send messages as @grafana_oncall
Send messages as @grafana_oncall with a customized username and avatar
Send messages to channels @grafana_oncall isn’t a member of — users configure channels to publish Alert Groups in the OnCall’s UI, but the bot is usually not a member of those channels.
Start direct messages with people
Add and edit emoji reactions

Perform actions in your workspace

Add shortcuts and/or slash commands that people can use — the permission is used to add /escalate and /oncall (deprecated) slack commands.
Create and manage user groups — the permission is used to automatically update user groups linked to on-call schedules. It will add users once their on-call shift starts and remove them once the on-call shift ends.
- NOTE: per Slack’s documentation, you must have a paid plan for this feature to work properly
Set presence for Grafana OnCall

Post-install configuration for Slack integration

Configure the following additional settings to ensure Grafana OnCall alerts are routed to the intended Slack channels and users:

From your Slack integration settings, select a default slack channel in the first dropdown menu. This is where alerts will be sent unless otherwise specified in escalation chains.
In Additional Settings, configure alert reminders for alerts to retrigger after being acknowledged for some amount of time.
Ensure all users verify their slack account in their Grafana OnCall users info.

Connect Slack user to Grafana OnCall

From the Users tab in Grafana OnCall, click View my profile.
In the User Info tab, navigate to Slack username, click Connect.
Follow the instructions to verify your account.

Configure Escalation Chains with Slack notifications

Once your Slack integration is configured you can configure Escalation Chains to notify via Slack messages for alerts in Grafana OnCall.

There are two Slack notification options that you can configure into escalation chains, escalate to all Slack channel members and notify Slack user group:

In Grafana OnCall, navigate to the Escalation Chains tab then select an existing escalation chain or click + New escalation chain.
Click the dropdown for Add escalation step.
Configure your escalation chain with automated Slack notifications.

Configure user notifications with Slack mentions

To be notified of alerts in Grafana OnCall via Slack mentions:

Navigate to the Users tab in Grafana OnCall, click Edit next to a user.
In the User Info tab, edit or configure notification steps by clicking + Add Notification step
select Notify by in the first dropdown and select Slack mentions in the second dropdown to receive alert notifications via Slack mentions.

Configure on-call notifications in Slack

The Slack integration for Grafana Oncall supports automated Slack on-call notifications that notify individuals and teams of their on-call shifts. Admins can configure shift notification behavior in Notification preferences:

When an on-call shift notification is sent to a person or channel, click the gear icon to access Notifications preferences.
Configure on-call notifications for future shift notifications.

Slack commands and message shortcuts

The Grafana OnCall Slack app includes helpful message shortcuts and slash commands.

Slack `/escalate` command

Use /escalate to page a team (and additional responders) directly from Slack.

Type /escalate in the message box of any Slack channel then click Send.
Fill out the Create Alert Group form then click Submit.
Once the Grafana OnCall app sends a Slack message with the newly created alert, the alert group is open and firing.

It’s also possible to page additional responders for an existing alert group. To do so, use the “Responders” button in the alert group message. To manually page people, refer to Page people manually.

Slack `/oncall` command

DEPRECATED: /oncall is deprecated and WILL BE REMOVED in a future release. Use /escalate instead.

Use the /oncall Slack command to create a new alert group directly from Slack targetting a team and/or route.

Type /oncall in the message box of the desired Slack channel then click Send.
Fill out the Start New Escalation creation form then click Submit.
Once the Grafana OnCall app sends a Slack message with the newly created alert, the alert group is open and firing.

Message shortcuts

Use message shortcuts to add resolution notes directly from Slack. Message shortcuts are available in the More actions menu from any message.

Note: In order to associate the resolution note to an alert group, this message shortcut can only be applied to messages in the thread of an alert group.

From an alert group thread, navigate to the Slack message that you wish to add as a resolution note.
Hover over the message and select More actions from the menu options.
Select Add as resolution note.
The Grafana OnCall app will react to the message in Slack with the memo emoji and add the message to the alert group timeline.

Telegram integration for Grafana OnCall

Fri, 03 Apr 2026 16:45:36 +0000

Telegram integration for Grafana OnCall

You can manage alerts either directly in your personal Telegram DMs or in a dedicated team channel.

Configure Telegram user settings in Grafana OnCall

To receive alert group contents, escalation logs and to be able to perform actions (acknowledge, resolve, silence) in Telegram DMs, please refer to the following steps:

In your profile, find the Telegram setting and click Connect.
Click Connect automatically for the bot to message you and to bring up your telegram account.
Click Start when the OnCall bot messages you and wait for the connection confirmation.
Done! Now you can receive alerts directly to your Telegram DMs.

If you want to connect manually, you can click the URL provided and then SEND MESSAGE. In your Telegram account, click Start.

(Optional) Connect to a Telegram channel

In case you want to manage alerts in a dedicated Telegram channel, please use the following steps as a reference.

NOTE: Only Grafana users with the administrator role can configure OnCall settings.

In OnCall, click on the ChatOps tab and select Telegram in the side menu.
Click Connect Telegram channel and follow the instructions, mirrored here for reference. A unique verification code will be generated that you must use to activate the channel.
In your team Telegram account, create a new channel, and set it to Private.
In Manage Channel, make sure Sign messages is enabled.
Create a new discussion group. This group handles alert actions and comments.
Add the discussion group to the channel. In Manage Channel, click Discussion to find and add the new group.
In OnCall, click the link to the OnCall bot to add it to your contacts.
In Telegram, add the bot to your channel as an Admin. Allow it to Post Messages.
Add the bot to the discussion group.
In OnCall, send the provided verification code to the channel.
Make sure users connect to Telegram in their OnCall user profile.

Each alert group is assigned a dedicated discussion. Users can perform actions (acknowledge, resolve, silence), and discuss alerts in the comments section of the discussions. In case an integration route is not configured to use a Telegram channel, users will receive messages with alert group contents, logs and actions in their DMs.

Mattermost

Fri, 03 Apr 2026 16:45:36 +0000

Mattermost

Mattermost support is not implemented yet.

Please join GitHub Issue or check PR.

Grafana OnCall Mobile app

Fri, 03 Apr 2026 16:45:36 +0000

Grafana OnCall Mobile App

The Grafana OnCall mobile app allows teams to monitor and respond to critical system events from anywhere. On-call engineers can start exploring the benefits of the Grafana OnCall mobile app, with real-time alerts, on-call notifications, and a growing feature set.

About Grafana OnCall mobile app

Grafana OnCall mobile app key features:

Override Do Not Disturb on your device to ensure delivery of important alerts
Receive push notifications according to your personal notification settings
Login with a quick and secure QR code authorization, even to multiple OnCall stacks
Viewing, filtering and responding to Alert Groups (acknowledge, resolve, silence, etc)
Adding responders to Alert Groups
Creating new escalation manually
Browsing and filtering schedules
View your on-call status and information about current and upcoming shifts

The OnCall mobile app allows users to receive push notifications as part of their notification policy. Push notifications are one of the many notification options in Grafana OnCall.

Consider using multiple notification methods, such as mobile app and phone/SMS, to remain available in case of degraded internet or phone network connectivity.

Notifications for OnCall OSS on Grafana Labs

Phone calls and SMS notifications

Phone and SMS notifications for Grafana OnCall OSS

Configure Twilio for OnCall OSS

Set up a Twilio phone number

Configure an outgoing webhook in OnCall

Configure Exotel for OnCall OSS

Set up Exotel API credentials

Configure an outgoing webhook in OnCall

Configure Zvonok for OnCall OSS

Next steps

SMS notification behavior

Example bundled notification

Route incoming calls to the on-call engineer

About phone call and SMS notifications

Country support for SMS/Voice

Configure push notifications for Grafana OnCall OSS

Configure push notifications for Grafana OnCall OSS

Configure webhooks for push notifications

Choose a push notification provider

Create an outgoing webhook in OnCall OSS

Assign the webhook as a personal notification channel

Example: Configure Pushover for OnCall OSS

Before you begin, ensure you have:

Create a Pushover application

Configure an outgoing webhook in OnCall

Assign the webhook as a personal notification channel

Example: Configure push notifications with ntfy

Set up an outgoing webhook for ntfy

Assign the webhook as a personal notification channel

Related configuration

Webhook as personal notification channel

Webhook as a personal notification channel

Configure a webhook to be used as personal notification

Related configuration

MS Teams integration for Grafana OnCall

MS Teams integration for Grafana OnCall

Before you begin

Connect Microsoft Teams with Grafana OnCall

Post-install configuration for Microsoft Teams integration

Connect Microsoft Teams user to Grafana OnCall

Configure user notifications with Microsoft Teams

Configure escalation chains to post to Microsoft Teams channels

Slack integration for Grafana OnCall

Slack integration for Grafana OnCall

Before you begin

Install Slack integration for Grafana OnCall

Configure timeout for acknowledged alerts

Why does OnCall Slack App require so many permissions?

Content and info about you

Content and info about channels & conversations

Content and info about your workspace

Perform actions in channels & conversations

Perform actions in your workspace

Post-install configuration for Slack integration

Connect Slack user to Grafana OnCall

Configure Escalation Chains with Slack notifications

Configure user notifications with Slack mentions

Configure on-call notifications in Slack

Slack commands and message shortcuts

Slack /escalate command

Slack /oncall command

Message shortcuts

Telegram integration for Grafana OnCall

Telegram integration for Grafana OnCall

Configure Telegram user settings in Grafana OnCall

(Optional) Connect to a Telegram channel

Mattermost

Mattermost

Grafana OnCall Mobile app

Grafana OnCall Mobile App

About Grafana OnCall mobile app

Slack `/escalate` command

Slack `/oncall` command