> 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/webhook_blocks.md).

# Exa Webhook Blocks

Blocks for receiving webhook notifications from Exa webset events.

## Exa Webset Webhook

### What it is

Triggers when Exa reports a Websets event, such as a new item, a finished search, a completed export or a monitor run

### How it works

This trigger is now enabled. When it is set up, the platform registers a webhook with Exa's Websets API for the events selected in Event Filter, and every delivery's `Exa-Signature` header is checked before the block runs. Registering needs your own Exa API key and fails with a clear message on the platform's shared Exa key, since every user of that key shares one Exa account. Besides the webset, search, item, export and import events, it can now fire on the Websets monitor events: monitor created, updated and deleted, and monitor run created and completed. 'Import processing' is legacy: Exa no longer sends it, so it is never registered, and a filter with only that event selected is rejected.

Exa webhooks cover your whole Exa team, so when Webset ID is set, events about other websets are skipped; events that name no webset, such as imports, still pass through. Each run outputs the event type and ID, the affected webset, the full resource the event is about, its timestamp and its metadata.

### Inputs

| Input         | Description                                                                                                                                                                | Type              | Required |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------- |
| webset\_id    | Only fire for events about this webset ID. Events that name no webset (imports, monitor runs) still fire. Leave empty to receive events for every webset on your Exa team. | 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, e.g. webset.item.created                          | str             |
| event\_id   | Unique identifier for this event                                               | str             |
| webset\_id  | ID of the affected webset, or the Webset ID filter when the event names none   | str             |
| data        | The full resource the event is about (webset, item, search, import or monitor) | Dict\[str, Any] |
| timestamp   | When the event occurred (ISO 8601)                                             | str             |
| metadata    | Metadata attached to the resource the event is about                           | Dict\[str, Any] |

### Possible use case

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

**Alert Systems**: Send a message when a webset search completes or an export is ready to download.

**Monitor Follow-Up**: Process new results each time a Websets monitor run completes.

***


---

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