> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/da/knowledge-base/how-to-articles/send-real-time-notifications-to-external-services-with-webhooks.md).

# Send meddelelser i realtid til eksterne tjenester med webhooks

Konfigurer webhooks i Devolutions Cloud til at sende hændelsesmeddelelser i realtid til eksterne tjenester som Slack med brugerdefinerede nyttedata.

Med webhooks kan De sende meddelelser i realtid til eksterne tjenester, når bestemte hændelser indtræffer i Deres Devolutions Cloud. Bemærk, at webhooks også findes i Devolutions Server.

{% hint style="info" %}
[Rapporteringstjenesten i Devolutions Cloud](/cloud/da/web-interface/reports/scheduled-reports.md) skal køre, da den håndterer kryptering og dekryptering af webhook-nyttedata under behandlingen.
{% endhint %}

1. Gå til ***Administration*** – ***Webhooks***.
2. Klik på **Tilføj.**
3. Angiv et beskrivende navn.
4. Angiv den slutpunkts-URL, som Devolutions Cloud skal sende HTTP POST-anmodningerne til.
5. Vælg de hændelser, der skal udløse webhooken.
6. De kan eventuelt definere en brugerdefineret nyttelast, der sendes med webhooken. Hvis De f.eks. vil sende en meddelelse i Slack, hver gang en ny post oprettes, ser ***Brugerdefineret HTTP-brødtekst (JSON***) sådan ud:

​`json { "Text": "New entry {{EntryName}} created by {{CreatedBy.DisplayName}}" } ​`

7. Klik på ***Tilføj*** for at gemme webhooken.

### Liste over handlebars til webhooks

Nedenfor er listen over tilgængelige handlebars-pladsholdere. Disse pladsholdere erstattes automatisk med de faktiske hændelsesdata, når en webhook udløses.

#### Yderligere felter, der er tilgængelige ved alle udløsere

* VaultName
* TriggerType (enum)
* TriggerTypeName

#### Ny udtjekningsanmodning

* EntryId
* EntryName
* RequesterMessage
* Requester.DisplayName
* Requester.Email
* Approvers (Array of {DisplayName: "name", Email: "<email@example.com>"})
* RequestedMinutes

#### Udtjekningsanmodning godkendt og afvist

* EntryId
* EntryName
* RequesterMessage
* Requester.DisplayName
* Requester.Email
* Approvers (Array of {DisplayName: "name", Email: "<email@example.com>"})
* ApproverMessage
* RequestedMinutes
* Approved (bool)

#### Post oprettet

* EntryId
* EntryName
* CreatedBy.DisplayName
* CreatedBy.Email

#### Anmodning om midlertidig adgang

* EntryId
* EntryName
* RequesterMessage
* Requester.DisplayName
* Requester.Email
* Approvers (Array of {DisplayName: "name", Email: "<email@example.com>"})
* RequestedMinutes

#### Anmodning om midlertidig adgang godkendt og afvist

* EntryId
* EntryName
* RequesterMessage
* Requester.DisplayName
* Requester.Email
* Approver.DisplayName
* Approver.Email
* ApproverMessage
* RequestedMinutes
* Approved (bool)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/cloud/da/knowledge-base/how-to-articles/send-real-time-notifications-to-external-services-with-webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.