> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/chatops/slack/incoming-webhook.md).

# Post alerts with a Slack webhook

Post ilert alerts to a Slack channel through a Slack incoming webhook, where the ilert app cannot be installed.

{% hint style="warning" %}
Prefer the [ilert app for Slack](/chatops/slack/post-alerts-to-a-slack-channel.md). A webhook only posts messages: nobody can accept, reroute, or resolve from the channel, the message is never updated as the alert changes, and the slash commands do not exist. Use this route only where your workspace will not grant the ilert app its permissions.
{% endhint %}

## In Slack: create an incoming webhook

Create a Slack app for your workspace, enable **Incoming Webhooks**, and add a webhook for the channel you want alerts in. Slack's own guide, [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks), walks through it.

Copy the webhook URL Slack gives you. It starts with `https://hooks.slack.com/services/` and ends in three path segments that identify the workspace, the channel, and the webhook's own secret.

{% hint style="danger" %}
Treat that URL as a secret. Anyone who has it can post to your channel.
{% endhint %}

## In ilert: create the alert action

{% stepper %}
{% step %}

## Start a new alert action

In the sidebar, go to **Alerting** → **Alert actions** and click **Create new alert action**.
{% endstep %}

{% step %}

## Choose Slack, with the webhook option

Select the **Slack** tile and tick **Use webhook**. Click **Next**.
{% endstep %}

{% step %}

## Choose the alert sources and the events to publish

Pick the alert sources whose alerts should reach the channel, and tick the events to publish. Only **Alert created** is ticked to begin with, and every event you add becomes its own message in the channel. Click **Next**.
{% endstep %}

{% step %}

## Skip the conditions

Set conditions under **Conditional execution**, or click **Next** to publish every alert of those sources.
{% endstep %}

{% step %}

## Paste the webhook URL

Name the alert action, paste the URL into **URL**, and click **Save**. Click **Save** again on the edit page to reach the detail page.
{% endstep %}

{% step %}

## Test it

Click **Test** in the top right. A test message appears in the channel.
{% endstep %}
{% endstepper %}

## What arrives in the channel

Each message carries the alert's status and summary as a link into ilert, the alert details, and the first image attached to the alert. A comment event carries the comment and its author. The color follows the status: red while pending, yellow once accepted, green when resolved.

Messages are always in English, and there are no buttons. Every event you tick posts a new message, so a busy alert produces a series of messages rather than one that keeps up to date.

## FAQ

### Can I use several webhooks?

Yes. Create one alert action per webhook URL, each with its own channel and its own trigger events.

### The messages stopped arriving

Open the alert action and read **Alert action logs** on its detail page. Slack rejects a webhook whose app was removed from the workspace, or whose channel was deleted; create a new webhook in Slack and paste the new URL into the alert action.

### Can I change how the message looks?

No. The Slack webhook alert action has no message template. The [ilert app](/chatops/slack/post-alerts-to-a-slack-channel.md) gives the richer card, and the generic [webhook integration](/integrations/outbound-integrations/webhook.md) gives full control over the payload.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/chatops/slack/incoming-webhook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.