> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Send incidents to a Slack channel with an Incoming Webhook.

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

## Setting it up

<Steps>
  <Step title="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.
  </Step>

  <Step title="Add the integration in aciona.me">
    Under **Integrations**, add the Slack integration and paste the webhook URL. Owners and admins can do this.
  </Step>

  <Step title="Adjust name and icon (optional)">
    In the Incoming Webhook settings in Slack, set the name to `aciona.me` and use the official icon. That makes the cards instantly recognizable in the channel.
  </Step>

  <Step title="Send a test alert">
    Trigger a test incident and confirm the card reaches the channel.
  </Step>
</Steps>

## What arrives in the channel

A card with:

* Incident severity and title.
* Affected service and alert origin.
* Current owner, when there is one.
* An **Open incident** link into the authenticated dashboard.

The card follows the lifecycle: creation, acknowledgement, assignment, escalation and resolution each produce their own message.

<Note>
  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.
</Note>

## Best practices

<AccordionGroup>
  <Accordion title="Use a dedicated channel" icon="hash">
    A channel such as `#incidents` keeps the history readable. Mixing it into a conversation channel makes incidents disappear among the chatter.
  </Accordion>

  <Accordion title="Slack does not replace push" icon="triangle-alert">
    A channel notification does not reliably wake anyone. Slack is for visibility; push is for paging.
  </Accordion>

  <Accordion title="Treat the webhook URL as a secret" icon="key-round">
    Anyone holding the URL can post to the channel. If it leaks, revoke it in Slack and generate a new one.
  </Accordion>
</AccordionGroup>

## Troubleshooting

| Symptom                         | What to check                                                                             |
| ------------------------------- | ----------------------------------------------------------------------------------------- |
| Nothing arrives in the channel  | The integration is active in aciona.me and the webhook URL is valid                       |
| It used to work and stopped     | The Incoming Webhook was revoked or the app was removed from the workspace                |
| Card lands in the wrong channel | Incoming Webhooks are pinned to one channel — generate a new URL for the channel you want |