> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/documentation/automations/nodes/nodes-triggers/using-webhook-triggers.md).
# Use webhook triggers
## What is a webhook trigger?
*Webhook triggers* are an effective way to kick off a workflow with context from external systems. By sending an API request to a webhook trigger, Rewst will fire the workflow and include any data and or queries included in the request. For example, when a customer submits a support ticket, a webhook instantly sends that information to Rewst and starts a workflow.
{% hint style="warning" %}
When using webhook triggers, design your workflow with our [rate limiting policy](/rewst-documentation/security/organization-rate-limits.md) in mind.
{% endhint %}
### **Webhook trigger process**
Webhooks follow a simple process:
1. An event happens, such as when a new ticket is submitted.
2. The webhook sends a message with data to a URL.
3. A workflow is triggered based on that message.
### **Webhook URLs**
A *webhook URL* is a unique address where data is received for that particular webhook. It continuously listens for data, and kicks off the related workflow the moment data is received. Once that data is captured, we call it a *payload*, and it becomes usable inside the workflow. This allows you to do things like:
* Assign tasks based on field values
* Push updates to other systems
* Send messages or alerts
* Store or log information for reporting
Webhook URLs are formatted consistently using the trigger ID and organization ID. The format is as follows: `https://engine.rewst.io/webhooks/custom/trigger/{{ Trigger ID }}/{{ Organization ID }}` . Find the webhook URL in the **Details** tab of the trigger node after it's been placed on the Workflow Builder Canvas.
---
# 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.rewst.help/rewst-documentation/documentation/automations/nodes/nodes-triggers/using-webhook-triggers.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.
