# 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       |

### 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: 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:

```
GET https://agpt.co/docs/integrations/block-integrations/triggers-2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.