With Slack integration, you can automate messages and notifications to your team. This integration allows you to send alerts and updates directly into Slack channels for seamless notifications.
Free - View Pricing
What Slack gives you
Configure it independently for each brand on a multi-company install, so every company runs with its own settings.
Every staff and client label ships in editable language files, ready to translate into any language or reword to match your brand.
A notification too long for one message is split across consecutive messages instead of being cut short, so nothing is silently lost off the end.
A built-in demo mode runs the whole extension from bundled sample data, so you can trial every screen and action before you have an account or API key.
Both the bot token and the Incoming Webhook URL are stored encrypted, so the credentials that can post into your workspace are never sitting in the database in plain text.
What it sends and what comes back is recorded in Blesta's own log, with credentials never written to it, so you can see exactly what happened without leaving your admin area.
Choose whether each notification also pings @here for active members or @channel for everyone, so urgent alerts are impossible to scroll past. Leave it on None for quiet delivery.
A test button on the settings page checks your credentials against the live service and reports back exactly what it said, without saving half-typed settings or waiting for a real event to fire.
Override the display name and set an emoji shortcode as the message icon, so Blesta notifications are instantly recognisable in a busy channel. Leave both blank to use your Slack app's own identity.
In bot token mode, set an optional staff channel and any notification addressed to a staff member is posted there instead, keeping internal alerts out of the channel your team watches for client activity.
Stored credentials are never rendered back into the settings page, and leaving a field blank when you edit keeps the saved value, so a secret is never exposed in day-to-day admin work and cannot be wiped by accident.
Use a Slack app bot token to post into any channel you name, or paste an Incoming Webhook URL to get running without creating a bot at all. Fill in whichever suits your workspace and the messenger uses that mode for both live sends and connection tests.
Notifications arrive as a structured Slack message with a heading, the message body and a footer, not a dump of raw HTML. Bold, italics and links from the notification template are converted to Slack's own formatting, and Slack's reserved characters are escaped so nothing renders wrong.

Welcome, and thank you for purchasing the Slack Messenger! We're delighted to have you as a customer and are committed to ensuring you have a seamless experience. This guide aims to walk you through the installation and configuration of your new extension. If you're new to Blesta or encounter any issues, please don't hesitate to reach out for support.
The Slack Messenger is designed to send notifications for various events in Blesta, ensuring you stay informed and connected with your clients and team. The notifications are categorized as follows:
Download the Messenger:
Upload to Blesta:
/var/www/html/blesta/components/messengers/slack/Install the Messenger:
Manage the Messenger:
/admin/settings/company/messengers/installed/).Check the Connection:
Messenger Configuration:
Enable Notifications:
| Setting | Description |
|---|---|
| API Token | Bot token of your Slack app, starting with xoxb-. Used with the Channel ID. Leave blank if you are using an Incoming Webhook URL instead. |
| Channel ID | The channel notifications are posted to in bot token mode. |
| Staff Channel ID | Optional. Notifications addressed to a staff member are posted here instead of the main Channel ID, keeping internal alerts separate from client ones. Bot token mode only. |
| Incoming Webhook URL | Optional alternative to the API Token: a Slack Incoming Webhook URL (https://hooks.slack.com/services/...). The webhook posts to its own channel, so Channel ID and Staff Channel ID are ignored in this mode. |
| Bot Name | Optional display name for the messages. Leave blank to use your Slack app's own name. |
| Bot Icon Emoji | Optional emoji shortcode used as the message icon, for example :bell:. Leave blank to use your Slack app's own icon. |
| Mention on Delivery | Optionally ping the channel when a notification arrives: None, @here (active members) or @channel (everyone). A notification long enough to be split across several messages pings only once. |
| Enable Mock API | Simulates deliveries from built-in sample responses instead of contacting Slack, so you can trial the messenger before you have a token or webhook. Turn it off for live sends. |
The API Token and the Incoming Webhook URL are stored encrypted and are never shown back to you. Leave them blank when you save to keep what is already stored, and type a value only when you want to replace it. Entering one of them clears the other, since the two modes are mutually exclusive.
API Token:
Channel ID:
Incoming Webhook URL:
https://hooks.slack.com/services/ - that is the only address Slack issues webhooks on, and the only one this messenger will post to.Order Notifications:
/admin/billing/index/).Ticket Notifications:
/admin/plugin/support_manager/admin_departments/)./admin/plugin/support_manager/admin_staff/).If you encounter any issues or have suggestions for improving the extension, please get in touch with us. We are committed to providing robust updates and welcome customer feedback.
Installing and updating extensions can now be done automatically through the Blesta Club Subscription Manager - this is the recommended way going forward.

Welcome, and thank you for purchasing the Slack Messenger! We're delighted to have you as a customer and are committed to ensuring you have a seamless experience. This README aims to guide you through the installation of your new extension. If you're new to Blesta or encounter any issues, please don't hesitate to reach out for support.
For detailed instructions on how to install the Slack Messenger, please ensure you have the license manager installed for leased extensions and then follow these steps:
Obtain the Messenger:
Upload to Blesta:
/var/www/html/blesta/components/messengers/slack/Install the Messenger:
/admin/settings/company/messengers/available/).The messenger connects to Slack in one of two ways. Set up whichever suits your workspace - a bot token, or an Incoming Webhook URL if you would rather not create a bot at all.
API Token:
Channel ID:
Incoming Webhook URL:
https://hooks.slack.com/services/ - that is the only address Slack issues webhooks on, and the only one this messenger will post to.Configure the Messenger:
/admin/settings/company/messengers/installed/).Messenger Configuration:
Enable Notifications:
You're now done with the installation! Proceed to configure the messenger as needed by following the usage guide!
If you encounter any issues or have suggestions for improving the extension, please get in touch with us. We are committed to providing robust updates and welcome customer feedback.
Installing and updating extensions can now be done automatically through the Blesta Club Subscription Manager - this is the recommended way going forward.

Welcome, and thank you for purchasing the Slack Messenger! We're delighted to have you as a customer and are committed to ensuring you have a seamless experience. This README aims to guide you through the update process of your new extension. If you're new to Blesta or encounter any issues, please don't hesitate to reach out for support.
To keep your Slack Messenger up-to-date, follow the steps outlined below:
Obtain the Updated Messenger:
Upload to Blesta:
/var/www/html/blesta/components/messengers/slack/Update the Messenger:
Blesta version (updating to 3.0.0):
Re-save your settings once (only if you are coming from 1.0.0):
New optional settings in 2.0.0 (no action required):
No other changes are needed outside of updating the files. Any breaking changes will be communicated to clients by the Blesta.Club team prior to it being made available for download!
Keep your Slack Messenger up-to-date to ensure you have the latest features and improvements.
If you encounter any issues or have suggestions for improving the extension, please get in touch with us. We are committed to providing robust updates and welcome customer feedback.

Welcome, and thank you for purchasing the Slack Messenger! We're delighted to have you as a customer and are committed to ensuring you have a seamless experience. This README aims to guide you through the usage of your extension. If you're new to Blesta or encounter any issues, please don't hesitate to reach out for support.
Once your Slack Messenger is installed and updated, you'll want to configure it to suit your needs. Follow the steps below for a comprehensive setup.
All settings live on Settings > Messengers (/admin/settings/company/messengers/installed/),
under "Manage" on the Slack Messenger.
The messenger talks to Slack in one of two modes. Fill in one or the other, not both:
xoxb-) and the Channel ID to post to. This mode can route staff notifications to their own channel.https://hooks.slack.com/... addresses are accepted, because that is the only place Slack issues webhooks.Both credentials are stored encrypted and are never shown back to you. Leave them blank when you save to keep what is already stored, and type a value only when you want to replace it. Entering one of them clears the other.
:bell:. Leave them blank to use your Slack app's own identity.@here for active members or @channel for everyone. Leave it on "None" for quiet delivery. A notification long enough to be split across several messages pings only once.Click Test Connection to send one test message using whichever mode you filled in. The result appears next to the button and shows exactly what Slack said, so a wrong channel or an expired token is obvious immediately. A test never saves anything - click "Update Settings" afterwards to keep what you typed. Because the credential fields are never shown back to you, re-enter your API Token or Webhook URL before running a test on an already-configured messenger.
Notifications are posted as Slack messages with a heading, the notification body and a footer. Bold, italics and links from your message templates are converted to Slack's own formatting, and a notification too long for one Slack message is split across several rather than being cut short. What was sent and what Slack answered is recorded in Blesta's messenger log under Tools > Logs.
The Slack Messenger is designed to send notifications for various events in Blesta, including:
If you encounter any issues or have suggestions for improving the extension, please get in touch with us. We are committed to providing robust updates and welcome customer feedback.
v3.0.0 - 2026-09-15
PHP 8.2 - 8.4 · Blesta 6.x
Now built for Blesta 6: the messenger installs and runs on Blesta 6.0 and newer, and no longer supports Blesta 5
The settings page is rebuilt for the Blesta 6 admin theme: related settings now sit two per row so the page is shorter, and the "Test Connection" button and result messages match the new look in both light and dark mode
No settings change on update: everything you already saved carries over as it is
v2.0.0 - 2026-09-11
PHP 7.2 - 7.4, 8.1 - 8.4 · Blesta 5.x
Notifications are now sent as rich Block Kit messages (a titled header, the body, and a footer) instead of plain text
Added optional Bot Name and Bot Icon Emoji settings so notifications can be branded per company
Added an optional Mention on Delivery setting to ping @here or @channel when a notification arrives
Added an optional Staff Channel ID so staff notifications can be routed to a separate channel from client ones
Added Incoming Webhook URL mode as a simpler alternative to creating a bot and API token
Fixed the API Token being displayed in readable text on the settings page; it is now masked, and leaving it blank keeps the token you already saved
The Incoming Webhook URL is masked on the same terms as the API Token: it is never shown back to you, and leaving it blank when you save keeps the URL you already stored
Slack rate limits are now retried once, and a message Slack still refuses is named as rate limited in the messenger log rather than blending in with other delivery failures
Fixed connection problems all being recorded the same way; the messenger log now names the reason, such as a DNS failure, a TLS failure or a timeout
v1.0.0 - 2024-09-22
PHP 7.2 - 7.3, 8.1 - 8.4 · Blesta 5.x
Blesta Club release
Get exactly what you need and want.
Requires PHP 8.2 - 8.4 · Blesta 6.x
Value: Free
Not sure whether to lease or own? Our FAQ explains how the licence types differ.
What our customers say
(0 customer reviews)
It is possible to leave a review only if you have purchased this extension or a Club tier which contains it.
We reserve the right to alter wording or formatting for presentation.
We will discuss any changes made and offer the option to withdraw review text if the changes can't be agreed on.
It may take up to 1 hour for a review to appear or update due to caching.