# Exa Webhook Blocks

Blocks for receiving webhook notifications from Exa webset events.

## Exa Webset Webhook

### What it is

Receive webhook notifications for Exa webset events

### How it works

This block acts as a webhook receiver for Exa webset events. When events occur on your websets (like new items found, searches completed, or enrichments finished), Exa sends notifications to this webhook endpoint.

The block can filter events by webset ID and event type. It parses incoming webhook payloads and outputs structured event data including the event type, affected webset, and event-specific details.

### Inputs

| Input         | Description                                                | Type              | Required |
| ------------- | ---------------------------------------------------------- | ----------------- | -------- |
| webset\_id    | The webset ID to monitor (optional, monitors all if empty) | str               | No       |
| event\_filter | Configure which events to receive                          | WebsetEventFilter | No       |

### Outputs

| Output      | Description                           | Type            |
| ----------- | ------------------------------------- | --------------- |
| error       | Error message if the operation failed | str             |
| event\_type | Type of event that occurred           | str             |
| event\_id   | Unique identifier for this event      | str             |
| webset\_id  | ID of the affected webset             | str             |
| data        | Event-specific data                   | Dict\[str, Any] |
| timestamp   | When the event occurred               | str             |
| metadata    | Additional event metadata             | Dict\[str, Any] |

### Possible use case

**Real-Time Processing**: Trigger workflows automatically when new items are added to websets without polling.

**Alert Systems**: Receive instant notifications when webset searches find new relevant results.

**Integration Pipelines**: Build event-driven integrations that react to webset changes in real time.

***


---

# 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/webhook_blocks.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.