> 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/concepts/advanced-concepts/webhooks.md).

# Webhooks

Configure Devolutions Cloud webhooks to send real-time event notifications to chat tools, ticketing systems, and automation services.

Webhooks let Devolutions Cloud push real-time event notifications to external systems such as chat tools, ticketing platforms, or automation services. Administrators configure webhook endpoints and event scopes so that when specific actions occur, such as entry creation, permission changes, or privileged access approvals, Devolutions Cloud sends a structured JSON payload to the target URL.

This turns Devolutions Cloud events into automation triggers. For example, a webhook can open a ticket when a sensitive vault gains a new member, post to a chat channel when a high-risk password is checked out, or call an orchestration tool that kicks off additional validation steps. Webhooks complement built-in logs and reports rather than replacing them.

#### Related topics

* [Send real-time notifications to external services with webhooks](/cloud/knowledge-base/how-to-articles/send-real-time-notifications-to-external-services-with-webhooks.md)
* [Web interface](/cloud/web-interface.md)
* [Privileged access reports](/cloud/web-interface/reports/privileged-access.md)


---

# 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/concepts/advanced-concepts/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.