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

# Webhooks

Configure webhooks de Devolutions Cloud para enviar notificaciones de eventos en tiempo real a herramientas de chat, sistemas de tickets y servicios de automatización.

Los webhooks permiten que Devolutions Cloud envíe notificaciones de eventos en tiempo real a sistemas externos, como herramientas de chat, plataformas de tickets o servicios de automatización. Los administradores configuran los endpoints de los webhooks y los ámbitos de eventos para que, cuando se produzcan acciones concretas, como la creación de entradas, cambios de permisos o aprobaciones de acceso privilegiado, Devolutions Cloud envíe un payload JSON estructurado a la URL de destino.

Esto convierte los eventos de Devolutions Cloud en disparadores de automatización. Por ejemplo, un webhook puede abrir un ticket cuando una bóveda sensible recibe un nuevo miembro, publicar en un canal de chat cuando se extrae una contraseña de alto riesgo o llamar a una herramienta de orquestación que inicia pasos de validación adicionales. Los webhooks complementan los registros e informes integrados, no los sustituyen.

#### Temas relacionados

* [Enviar notificaciones en tiempo real a servicios externos con webhooks](/cloud/es/knowledge-base/how-to-articles/send-real-time-notifications-to-external-services-with-webhooks.md)
* [Interfaz web](/cloud/es/web-interface.md)
* [Informes de acceso privilegiado](/cloud/es/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 dynamically 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/es/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 `build a script that syncs our docs to a CMS` 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.