This repository has been archived on 2024-05-31. You can view files and clone it, but cannot push or open issues or pull requests.
authentik/website/docs/events/transports.md
Jens Langhammer 9a7fa39de4 events: allow setting a mapping for webhook transport to customise request payloads
closes #1383

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
2021-09-12 01:05:42 +02:00

945 B

title
Transports

Notifications can be sent to users via multiple mediums. By default, the global email configuration will be used.

Generic Webhook

This will send a POST request to the given URL with the following contents:

{
    "body": "body of the notification message",
    "severity": "severity level as configured in the trigger",
    "user_email": "user's email",
    "user_username": "user's username",
}

The Content-Type header is set to text/json.

Starting in 2021.10, you can also select a Notification mapping. This allows you to freely configure the request's payload. For example:

return {
    "foo": context['notification'].body,
}

Slack Webhook

This sends a request using the Slack-specific format. This is also compatible with Discord's webhooks by appending /slack to the Discord webhook URL.