> ## Documentation Index
> Fetch the complete documentation index at: https://relevanceai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Triggers

> Connect to a custom webhook to trigger your Agent

Webhook Triggers let you trigger your Agent via HTTP requests from any external system — no native integration required. When your webhook receives a request, it sends the payload to your Agent as a message.

### Setting up a Webhook Trigger

1. Navigate to your Agent's settings and select the **Triggers** section
2. Choose **Webhook Trigger** from the available options
3. Copy your unique webhook URL
4. Configure your webhook settings:
   * **Message template**: Use template variables with double brackets (e.g., `{{first_name}}`) to format incoming data, or use `{{$}}` to pass the entire payload
   * **Thread ID mapping**: Map a field from your payload to a Thread ID to keep related messages in the same conversation
   * **Unique ID mapping**: Map a field to prevent duplicate processing of the same event

### Common use cases

* Process form submissions from your website
* Trigger responses when new support tickets are created
* Connect third-party platforms that support outgoing webhooks
* Build automated workflows between different systems

## Frequently asked questions (FAQs)

<AccordionGroup>
  <Accordion title="Can I use webhook triggers with any external system?">
    Yes, any system capable of sending HTTP requests can integrate with Relevance AI's webhook triggers, making them extremely versatile for various integration scenarios.
  </Accordion>

  <Accordion title="How secure are webhook triggers?">
    Webhook triggers use unique URLs that are difficult to guess. For additional security, you can implement Unique ID mapping to prevent duplicate processing and validate incoming requests.
  </Accordion>

  <Accordion title="What happens if the same webhook is triggered multiple times?">
    By mapping a Unique ID field, you can prevent duplicate processing. If an event with the same Unique ID is received again, it will be ignored, ensuring data integrity.
  </Accordion>
</AccordionGroup>