> 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/knowledge-base/how-to-articles/send-real-time-notifications-to-external-services-with-webhooks.md).

# Enviar notificaciones en tiempo real a servicios externos con webhooks

Los webhooks le permiten enviar notificaciones en tiempo real a servicios externos cada vez que se producen determinados eventos en su Devolutions Cloud. Tenga en cuenta que los webhooks también están disponibles en Devolutions Server.

{% hint style="info" %}
El [servicio de informes de Devolutions Cloud](/cloud/es/web-interface/reports/scheduled-reports.md) debe estar en ejecución, ya que se encarga del cifrado y descifrado de las cargas útiles de los webhooks durante el procesamiento.
{% endhint %}

1. Vaya a ***Administración*** – ***Webhooks***.
2. Haga clic en **Añadir.**
3. Introduzca un nombre descriptivo.
4. Indique la URL del endpoint donde Devolutions Cloud enviará las solicitudes HTTP POST.
5. Elija los eventos que activarán el webhook.
6. Opcionalmente, puede definir una carga útil personalizada para enviarla con el webhook. Por ejemplo, si desea enviar un mensaje en Slack por cada nueva entrada creada, el ***Custom HTTP Body (JSON***) tendría este aspecto:

![](https://cdnweb.devolutions.net/docs/HUBB6002_2025_3.png)

7. Haga clic en ***Añadir*** para guardar el webhook.

### Lista de handlebars de webhooks

A continuación se muestra la lista de marcadores de posición handlebars disponibles. Estos marcadores de posición se sustituyen automáticamente por los datos reales del evento cada vez que se activa un webhook.

#### Campos adicionales disponibles en todos los desencadenadores

* VaultName
* TriggerType (enum)
* TriggerTypeName

#### Nueva solicitud de checkout

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

#### Solicitud de checkout aprobada y denegada

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

#### Entrada creada

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

#### Solicitud de acceso temporal

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

#### Solicitud de acceso temporal aprobada y denegada

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.