> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/api-documentation-v2/webhook/how-webhook-works.md).

# How Webhook Works

Webhook enables you to receive incoming messages into your server on real-time basis from various messaging channels activated by you.

{% embed url="<https://youtu.be/1Er5KsDJZAs>" %}

## Type of Webhooks

| Webhook Type                                                                                                     | Description                                                                                                               | Path                                                                                                          | Path V4                                                                                                       |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [Global Webhook ](/api-documentation-v2/webhook.md)                                                              | This is a global webhook which capture all incoming messages in your project from all configured channels                 | Settings -> Developers-> Webhook -> [Global Webhook](https://pickyassist.com/app/settings/developers/webhook) | Settings -> Developers-> Webhook -> [Global Webhook](https://app.pickyassist.com/settings/developers/webhook) |
| [Smart Reply Webhook](https://help.pickyassist.com/setting-up-guide/smart-replies/settings#configuring-webhooks) | This can be set along with Smart Replies , if smart replies webhook are enabled then global webhook will not be triggered | Smart Replies -> Settings -> [Webhook](https://pickyassist.com/app/smart-replies/settings)                    | Smart Replies -> Settings -> [Webhook](https://app.pickyassist.com/smart-replies/settings)                    |
| [Event Webhook](/api-documentation-v2/event-webhook.md)                                                          | This can be set to capture all events like Delivery Report, WhatsApp Filter Report, New Subscriber Alert etc              | Settings -> Developers-> Webhook -> [Event Webhook](https://pickyassist.com/app/settings/developers/webhook)  | Settings -> Developers-> Webhook ->[ Event Webhook](https://app.pickyassist.com/settings/developers/webhook)  |

{% hint style="warning" %}
Please enable the POST method in your server to receive webhook requests and make sure your server firewall allows incoming POST requests from our server.&#x20;
{% endhint %}


---

# 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://help.pickyassist.com/api-documentation-v2/webhook/how-webhook-works.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.