> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/app-components/webhooks/dedicated.md).

# Dedicated

Unlike a shared webhook, dedicated webhooks are directly linked to the user account. Only notifications for the specific user are received.

{% hint style="info" %}
Even when a service sends all data to only one URL registered for the user, it's a dedicated webhook. It's up to you to determine how the app will handle incoming data. Over 90% of services use dedicated webhooks so be cautious when using a shared webhook.
{% endhint %}

## Types of dedicated webhooks

### Attached

For an [attached dedicated webhook](https://developers.make.com/custom-apps-documentation/app-components/webhooks/dedicated/attached.md), the new URL address that is created is automatically registered to the service using an attach procedure and can be unregistered using detach procedure.

If there is an endpoint available in the API for registration of the webhook, the attach directive should be implemented.

### Not attached

For a [dedicated webhook that is not attached](https://developers.make.com/custom-apps-documentation/app-components/webhooks/dedicated/not-attached.md), the new URL address that is created has to be registered manually by the user. The user copies the URL address and pastes it to the webhook's settings of the web service.

If there is no attach directive available in the API but the web service allows setting up a webhook manually, implement the dedicated webhook without the attach directive.


---

# 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://developers.make.com/custom-apps-documentation/app-components/webhooks/dedicated.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.
