> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/integrations/enate-integrations/webhook-sample-auto-notifying-other-apps-of-new-cases-tickets-and-comms.md).

# Auto-notify other apps of new Cases, Tickets & comms with Enate's Webhooks

A sample integration showing how to auto-notify other apps of new Cases, Tickets and communications via Enate's Webhook subscriptions.

Check out this explainer for how you can get your client apps to automatically receive real-time updates from Enate, such as from new Cases, Tickets and communications, via Webhook subscriptions. It will also show you how you can make additional updates into Enate from the client app itself.

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM5Nzk3NA==>" %}

Check out our Webhooks section for more information about Enate's Webhooks and how to use them:

{% content-ref url="/pages/-MWitakdiScHygZobBO9" %}
[Webhooks](/enate-help/integrations/enate-integrations/webhooks.md)
{% endcontent-ref %}


---

# 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.enate.net/enate-help/integrations/enate-integrations/webhook-sample-auto-notifying-other-apps-of-new-cases-tickets-and-comms.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.