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

# Exa Websets Monitor Runs

Blocks for checking the scheduled runs of Exa Websets monitors.

## Exa Get Webset Monitor Run

### What it is

Get the status and outcome of one scheduled run of a Websets monitor

### How it works

This block reads one run from the Websets API's `/v0/monitors/{monitor_id}/runs/{run_id}` and returns it once, without waiting or polling. Status is one of created, running, completed, canceled or failed, and type says whether the run was a search or a refresh.

`failed_reason` is filled only for failed runs and `completed_at` only once the run has finished. It charges only if Exa's response reports a cost (150 credits per USD).

### Inputs

| Input       | Description                                      | Type | Required |
| ----------- | ------------------------------------------------ | ---- | -------- |
| monitor\_id | The ID of the Websets monitor the run belongs to | str  | Yes      |
| run\_id     | The ID of the run to retrieve                    | str  | Yes      |

### Outputs

| Output         | Description                                     | Type |
| -------------- | ----------------------------------------------- | ---- |
| error          | Error message if the operation failed           | str  |
| run            | The full run details                            | Run  |
| run\_id        | The unique identifier for the run               | str  |
| status         | created, running, completed, canceled or failed | str  |
| type           | What the run did: search or refresh             | str  |
| failed\_reason | Why the run failed (only for failed runs)       | str  |
| completed\_at  | When the run completed, if it has               | str  |
| created\_at    | When the run started                            | str  |

### Possible use case

**Run Health Check**: Fetch the latest run of a monitor and alert someone if it failed.

**Failure Diagnosis**: Read the failed reason of a run to decide whether to fix the monitor or retry.

**Completion Gate**: Continue a workflow only after a specific monitor run has completed.

***

## Exa List Webset Monitor Runs

### What it is

List the scheduled runs of a Websets monitor, to check whether its updates succeeded

### How it works

This block lists a monitor's runs from the Websets API's `/v0/monitors/{monitor_id}/runs` in a single request. It outputs the whole list and then each run one at a time, plus `has_more` and `next_cursor` as Exa returns them.

The block has no limit or cursor input, so it always returns Exa's first page; `next_cursor` can't be passed back to it. It charges only if Exa's response reports a cost (150 credits per USD).

### Inputs

| Input       | Description                                      | Type | Required |
| ----------- | ------------------------------------------------ | ---- | -------- |
| monitor\_id | The ID of the Websets monitor whose runs to list | str  | Yes      |

### Outputs

| Output       | Description                                       | Type                         |
| ------------ | ------------------------------------------------- | ---------------------------- |
| error        | Error message if the operation failed             | str                          |
| runs         | The monitor's runs                                | List\[WebsetMonitorRunModel] |
| run          | Individual run (yielded for each run in the list) | Run                          |
| has\_more    | Whether Exa has more runs than it returned        | bool                         |
| next\_cursor | Cursor Exa returned for the next page, if any     | str                          |

### Possible use case

**Monitor Audit**: Review recent runs of a monitor to see how often its scheduled updates succeed.

**Failure Alerts**: Loop over runs and flag any with a failed status.

**Activity Reporting**: Count search and refresh runs for a periodic report on a monitor.

***


---

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