> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/triggers-3.md).

# Generic Webhook Triggers

Blocks for receiving and processing generic webhook payloads from external services.

## Generic Webhook Trigger

### What it is

This block will output the contents of the generic input for the webhook.

### How it works

This block creates a webhook endpoint that receives and outputs any incoming HTTP payload. When external services send data to this webhook URL, the block triggers and outputs the complete payload as a dictionary.

Constants can be configured to pass additional static values alongside the dynamic webhook data.

### Inputs

| Input         | Description                                                                                                                                                                                                                 | Type            | Required |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------- |
| constants     | The constants to be set when the block is put on the graph                                                                                                                                                                  | Dict\[str, Any] | No       |
| secret\_token | Optional. If set, the platform will only accept incoming webhook requests that include this exact value in the 'X-Webhook-Secret' header. Leave empty for unauthenticated webhooks (the URL itself is the only credential). | str             | No       |

### Outputs

| Output    | Description                                                              | Type            |
| --------- | ------------------------------------------------------------------------ | --------------- |
| error     | Error message if the operation failed                                    | str             |
| payload   | The complete webhook payload that was received from the generic webhook. | Dict\[str, Any] |
| constants | The constants to be set when the block is put on the graph               | Dict\[str, Any] |

### Possible use case

**External Integrations**: Receive data from any third-party service that supports webhooks.

**Custom Triggers**: Create custom workflow triggers from external systems or internal tools.

**Event Processing**: Capture and process events from IoT devices, payment processors, or notification services.

***


---

# 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://agpt.co/docs/integrations/block-integrations/triggers-3.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.