Notification Actions
Buddy integrates with the most popular messaging services to ensure your team is always up-to-date with the progress in the project:
Image loading...
About notifications
Notifications are usually added at the end of the delivery pipeline as a summary of the executed actions:
Image loading...
Each notification action contains a default message with essential pipeline details: pipeline name, execution ID, and invoker. The details are generated with default Buddy variables:
[#$BUDDY_RUN_ID] $BUDDY_PIPELINE_NAME execution by <$BUDDY_TRIGGERING_ACTOR_URL|$BUDDY_TRIGGERING_ACTOR>
Most notification actions support attachments. In case of Slack, you can also define content blocks, as shown on the screenshot below:
Image loading...
And here's how the message looks rendered in the Slack's window:
Image loading...
Available notification actions
Discord
Discord is a communication platform primarily used by gaming and development teams for real-time collaboration.
In the configuration, you provide the Discord channel’s webhook URL and define the message content. The action supports embedded content in JSON format as well as attachments.
Email is a standard electronic mail service that allows sending text messages and attachments.
In the configuration, you can select recipients from the workspace or provide a custom email address. The action supports attachments.
Google Chat
Google Chat is a corporate messenger within the Google Workspace ecosystem used for communication in rooms and threads. The Google Chat notification action requires prior configuration of the Google Cloud integration and enabling the Google Chat API.
In the configuration, you select the Google Cloud integration and the target channel in Google Chat. See the Google Chat setup guide for detailed instructions.
Microsoft Teams
Microsoft Teams is a collaboration platform for teams that provides chat, video conferencing, and integration with Microsoft tools. The action sends a message to a selected Teams channel. Simply paste the channel email address and define the message title and content.
In the configuration, you provide the channel’s email address and define the message title and content. The action supports attachments.
Pushbullet
Pushbullet is a device synchronization service that enables sending notifications across different platforms and devices.
In the configuration, you can send push notifications directly to mobile and browser devices connected to your Pushbullet account. Learn how to configure the Pushbullet integration and start sending notifications from your pipeline to your devices.
Pushover
Pushover is a dedicated push notification service that sends alerts to mobile and desktop applications.
In the configuration, you can choose specific devices or leave the field empty to target all active devices. The action allows you to set the notification priority and add a title, message content, URL, and URL title. Learn how to configure the Pushover integration and receive pipeline status notifications on all your devices.
Slack
Slack is a popular communication platform for teams, offering topic-based channels, integrations, and advanced message formatting.
In the configuration, you can use content blocks and attachments. Learn how to configure the Slack integration and use slash commands to manage pipelines directly from Slack channels.
SMS
SMS are standard text messages sent directly to mobile phone numbers.
In the configuration, you provide phone numbers (one per line, without leading zeros or special characters, e.g. 12025550198, 48500500500) and the message content. The cost of sending one SMS is $0.25. Attachments are not supported by this action.
Telegram
Telegram is a secure messaging platform focused on privacy and performance, offering public channels and groups.
In the configuration, you use the Buddy Telegram Bot to publish pipeline status messages to a selected Telegram group chat or channel. Learn how to configure the Telegram integration and send automatic build and deployment status notifications to your Telegram channels.
Conditional notifications
To prevent filling your inbox or channel with unwanted spam, you can configure Buddy to inform you only in certain cases. The most common use case is sending a message only when your tests or deployment have failed.
To do that, add the notification to the On Failure scenario of the pipeline:
Image loading...
To let your team know that the pipeline status has gone back from 'Failed' to 'Successful', you can add another notification to On Back to Green:
Image loading...
Learn more about Events and Actions in pipelines, including ON RUN, ON FAILURE, ON BACK TO GREEN, and other scenarios.
If you use Buddy to monitor your website, you can configure the action in the On Failure scenario to send the notification only once when the pipeline fails. This way you won't get overloaded with messages about the failure every few minutes. You can find the when option in the Options tab of the action:
Image loading...
Advanced conditioning
You can add an extra set of trigger conditions in the Conditions tab. The options let you send notifications, for example, on changes to a specific path (e.g. when somebody modifies the /assets folder), or depending on the value of an ENV VAR (e.g. $BUDDY_TRIGGERING_ACTOR – when you have that one developer you need to keep an eye on):
Image loading...
Last modified on Nov 7, 2025