> For the complete documentation index, see [llms.txt](https://docs.flexy.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexy.bot/modules/scripting/triggers/webhook.md).
# Webhook
**Introduction**
The "Webhook" trigger reacts to HTTP requests, allowing a seamless integration with other services.
**Configuration**
* **Method**: Specify the HTTP request method to be used, such as GET, POST, PUT, DELETE, etc. This field is required.
* **Parameters**: Define the parameters to be included in the webhook processing. Parameters can be of various types, including text, integer, number, object, list, boolean, and date. You can pass parameters as query parameters (for GET requests) or within a JSON object in the request body (for other methods). You can include up to 20 parameters. If you specify a required parameter and you don't include it when executing a webhook, it will return an error and automation will not be triggered.
To obain the **Webhook URL**, use the button on the trigger when editing an automation. Button will be visible only after automation has been created.
After getting the URL, you can use it to make a HTTP request. When making a request, make sure to use the same HTTP Method as you selected as **Method** when configuring the trigger, and include parameters (if you specified them).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.flexy.bot/modules/scripting/triggers/webhook.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.