> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/organization/notification-channels.md).

# Notification channels

Sending the events of runs to other systems. Found under **Organization management → Notification channels**.

## What they are for

A [trigger](https://docs.artific.nl/en/for-administrators/assistants/triggers.md) can e-mail people when a run starts, finishes, fails or needs attention. A notification channel does the same for systems: it is an outgoing webhook that receives the run events of the triggers that use it.

That lets a run set something in motion elsewhere, such as a ticket in your own system or a next step in a workflow tool.

This page is technical. If you are not the person who builds the receiving end, hand it to whoever does.

## Adding a webhook

Choose **Add webhook**.

| Field                  | What to enter                                                                                                                                                              |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**               | What the webhook is for, so you recognise it when choosing it on a trigger.                                                                                                |
| **Endpoint URL**       | Where the events go. It must be a public https address; private and internal addresses are refused.                                                                        |
| **Signing secret**     | The secret every delivery is signed with. Choose one of your [secret keys](https://docs.artific.nl/en/for-administrators/tools/secret-keys.md) or **Generate new secret**. |
| **Deliver run events** | Switches deliveries on or off without deleting the webhook.                                                                                                                |

Every delivery carries an `X-Artific-Signature` header: an HMAC-SHA256 of the timestamp, a dot and the body, keyed with the signing secret. The receiving system checks it to be sure the event really comes from your organisation and arrived unchanged.

## Connecting a webhook to a trigger

A webhook only receives events from triggers that use it. On the trigger, under **Webhooks**, switch on the webhooks that should receive its events. One webhook can serve several triggers.

## Checking that it works

The list shows each webhook's **Status** and its **Last delivery**. **Send test** sends a test event, so you can check the receiving end before a real run depends on it.

If several deliveries in a row fail, the webhook is marked as failing with the reason, and nothing more is sent to it until it is fixed. Fix the receiving end, then choose **Send test**. On a trigger, a failing webhook is shown as such, so it is clear why its events do not arrive.

## Deleting a webhook

**Delete** removes the webhook. Triggers can then no longer send events to it.

{% hint style="warning" %}
Check which triggers use a webhook before deleting it. Their e-mail notifications keep working, but any process that relied on the webhook receives nothing more.
{% endhint %}
