Skip to main content
The Slack integration gives you collective visibility: the whole team sees the incident, who acknowledged it and how it evolved.

​
Setting it up

1

Create an Incoming Webhook in Slack

In your Slack workspace, create an app (or use an existing one), enable Incoming Webhooks and generate a webhook URL for the channel that should receive incidents. The URL starts with https://hooks.slack.com/.
2

Adjust name and icon (optional)

Slack doesn’t let a message set its own sender. To make cards show up as aciona.me, set that name and the official icon in the app settings (Basic Information).
3

Add the integration in aciona.me

Under Integrations → Slack, paste the URL in Organization configuration. Optionally give it a display name so you can recognize the destination later. Owners and admins can do this.
4

Test it

Click Test and confirm the test message reaches the channel.

​
One channel per team

The organization configuration is the default for every team. Under Team overrides, you can point a specific team to another channel (or disable it). Teams without an override keep using the organization webhook.

​
What arrives in the channel

A card in the organization’s language with:
  • Incident severity and title.
  • Affected service and alert origin.
  • Current owner, when there is one.
  • Open incident, Acknowledge and Assign to me buttons into the authenticated dashboard.
The card follows the lifecycle: creation, acknowledgement, assignment, escalation and resolution each produce their own message.
Slack messages are sent regardless of whether personal recipients exist. Even when the schedule points at nobody, the channel still gets the incident — an important safety net.

​
Accepted addresses

For security, aciona.me only accepts https:// URLs from Slack itself (hooks.slack.com). Any other address is rejected on save. Older integrations pointing at an address outside that list stop receiving notifications and show a warning on the integration screen. To fix it, save again with the official Incoming Webhook URL.

​
Best practices

A channel such as #incidents keeps the history readable. Mixing it into a conversation channel makes incidents disappear among the chatter.
A channel notification does not reliably wake anyone. Slack is for visibility; push is for paging.
Anyone holding the URL can post to the channel. If it leaks, revoke it in Slack and generate a new one.

​
Troubleshooting