# Not attached

The new URL address for the webhook, created when a user opens the instant trigger and creates a new webhook, has to be registered manually by the user. The user needs to copy the URL address and paste it to the webhook configuration in the settings of the external platform.\
\
The main advantages of webhooks that are not attached when compared to the custom webhook module are:

* Improved UX
  * Mapping is easier when you define an [interface](https://developers.make.com/custom-apps-documentation/component-blocks/interface).
  * Ability to modify the output if needed, such as parsing dates in non-standard forms, or un-nesting parameters.
* Improved discoverability
  * Easier for most users to notice as a viable option for their integrations.

If your intend to have your app approved by Make, you must provide instructions on how to connect the webhook in the app's docs.

Most webhooks that can't be attached automatically should NOT have a connection linked to them. However, there are a few notable exceptions where you might still need it:

* One or more [RPCs](https://developers.make.com/custom-apps-documentation/app-components/rpcs) are used in the parameters of the webhook
* One or more [RPCs](https://developers.make.com/custom-apps-documentation/app-components/rpcs) are used in the instant trigger module.
* One or more additional requests are defined in the instant trigger communication (for example, a webhook that sends only a resource ID with a request to retrieve the actual data for that resource).

<div align="left"><figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-45422806541031e7b7164bb6de49f720601bdaf1%2FScreen%20Shot%202022-09-02%20at%2016.31.52%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
