> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks.md).
# Webhooks
Webhook integration functionality is one of the key enablers in the proactive journey of IT Support teams. It enables Nexthink to communicate with many third-party tools via automatic notifications to quickly report IT incidents, issues, changes, messages, requests and alerts, making such notifications visible to the various teams within the IT ecosystem.
Webhooks are automated messages sent from the applications when an event occurs. They have a message or payload and are sent to a unique URL which acts as the application’s unique address.
They are a simple way for Nexthink to communicate with third-party tools and send automatic notifications when an event occurs. If you wish to take advantage of such notifications, you will need to know how to use webhooks to push data from one application to another automatically.
Nexthink allows you to define on outbound webhooks. They can be configured to execute and perform an action leveraging a third-party URL, resource and payload when an event takes place in Nexthink. At that point, an alert is triggered. They can be configured to send a message to a third-party product when an alert or event is triggered.
* [Managing webhooks](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks/managing-webhooks.md)
* [Webhook use cases setup](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks/webhook-use-cases-setup.md)
* [Webhooks FAQ](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks/webhooks-faq.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.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks.md?ask=&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.
