Notifications
Send Huckleberry alerts and reports to Slack and Microsoft Teams channels via webhooks.
Huckleberry can post alerts, fault notifications, and scheduled reports directly into Slack or Microsoft Teams channels. Each integration uses an incoming webhook URL — a unique URL generated by Slack or Teams that Huckleberry posts messages to.
The setup is the same shape for both platforms:
- Create a webhook URL in the chat platform.
- Paste the URL into Huckleberry’s notification settings.
- Pick which alerts route to that channel.
Only users with the Client Admin role can access Account Management in Huckleberry. If you can’t see that menu, ask a Client Admin on your team to add the webhook for you, or to grant you the role first.
Slack
There are two ways to connect a Slack channel. The one-click Add to Slack button is the easiest and the recommended path; the manual webhook flow is still available if you’d rather manage the URL yourself.
Add to Slack (recommended)
- In Huckleberry, go to Account Management → Client Organization tab and find the Notification Webhooks section.
- Click Add to Slack.
- Slack opens its authorization screen. Choose the workspace and the channel you want Huckleberry to post into, then click Allow.
- You’re returned to Huckleberry and the new channel appears in your webhook list automatically — there’s no URL to copy or paste.
Slack shows the channel picker for you, and Huckleberry labels the connection
with the channel and workspace name (for example #alerts (Acme Corp)) so
it’s easy to tell your channels apart. Huckleberry only requests the
incoming-webhook permission — it can post to the channel you pick and
nothing more.
Add a webhook URL manually
Prefer to create and manage the webhook yourself? You can still paste a URL in.
- Go to api.slack.com/apps and sign in.
- Click Create New App → From scratch. Give it a name (e.g. "Huckleberry") and pick the workspace it belongs to.
- In the app’s left sidebar, open Incoming Webhooks and toggle Activate Incoming Webhooks on.
- Scroll down and click Add New Webhook to Workspace.
- Choose the channel you want Huckleberry to post into and click Allow.
- Copy the generated Webhook URL. It will look like
https://hooks.slack.com/services/T000.../B000.../.... - In Huckleberry, go to Account Management → Client Organization tab, find the Notification Webhooks section, paste the URL, and save.
Treat the webhook URL like a password. Anyone with the URL can post messages into that channel. Don’t commit it to a public repo.
Microsoft Teams
Microsoft retired the legacy Office 365 Connectors and Incoming Webhook connector for Teams. The supported way to receive an external HTTP webhook into a Teams channel is now a Workflow built in Power Automate. The setup takes about a minute per channel.
1. Create a Workflow webhook in Teams
- In Teams, hover over the channel you want notifications in, click the
...menu, and pick Workflows. - Search for the template "Post to a channel when a webhook request is received" and select it.
- Confirm the Teams account, channel, and (optionally) a workflow name. Click Next → Add workflow.
- Teams will display the generated HTTP POST URL. Copy it — you
can’t see it again after closing the dialog. It will look like
https://prod-XX.westus.logic.azure.com:443/workflows/.../triggers/manual/paths/invoke?....
Like the Slack URL, the Teams workflow URL is a secret. Anyone with it can post messages into that channel.
2. Add the webhook to Huckleberry
In Huckleberry, go to Account Management → Client Organization tab and find the Notification Webhooks section. Paste the Teams workflow URL there and save.
Testing
Once a webhook is configured, send a test message from Huckleberry to confirm the channel is receiving posts. If a test message doesn’t arrive:
- Slack — verify the webhook URL is current; webhooks can be revoked from the app’s Incoming Webhooks page.
- Teams — check that the Workflow is enabled. In Power Automate, open the workflow and look at the run history for errors.
- For both — confirm the URL was copied with no leading/trailing whitespace.
Troubleshooting
| Symptom | Likely cause |
|---|---|
Slack returns no_service | Webhook was deleted or the app was uninstalled. |
Slack returns channel_not_found | The target channel was archived or the integration lost access. |
| Teams workflow returns 400 | Message payload doesn’t match the expected Adaptive Card schema. |
| No errors but no message appears | Workflow is paused, or the URL points to a different channel. |
Need help getting a webhook wired up? Email info@huckleberryservices.com.