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

# Exa Search Monitors Update

Blocks for changing an Exa Search Monitor's status, search, schedule, output format or webhook.

## Exa Update Search Monitor

### What it is

Update an Exa Search Monitor: pause or resume it, or change its query, schedule, output format or webhook

### How it works

This block sends `PATCH /monitors/{monitor_id}` to Exa with only the fields you set; everything left empty keeps its current value, and the block fails if nothing is set. `remove_schedule` sends a null trigger, making the monitor manual-only, and wins over `period`; `clear_metadata` removes all metadata and wins over `metadata`. A new `period` follows the same rule as on create (a whole number followed by `h` or `d`). Leaving a domain or webhook event list, the content options or the output schema empty keeps the current value, so they cannot be cleared here. If Exa's response reports a `costDollars` total, the block bills it at 150 credits per USD; otherwise the call is free. It 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.

### Inputs

| Input            | Description                                                                                                                                                                                                                                                           | Type                                                                                                                   | Required |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | -------- |
| monitor\_id      | The monitor to update                                                                                                                                                                                                                                                 | str                                                                                                                    | Yes      |
| status           | active runs on schedule; paused runs only when triggered. Leave empty to keep the current status.                                                                                                                                                                     | "active" \| "paused"                                                                                                   | No       |
| query            | New search query                                                                                                                                                                                                                                                      | str                                                                                                                    | No       |
| period           | How often the monitor runs: a whole number followed by h (hours) or d (days), minimum 1h, e.g. 6h, 1d or 7d. The schedule is anchored to the creation time and a run may start up to 30 minutes late. Leave empty to keep the current schedule.                       | str                                                                                                                    | No       |
| remove\_schedule | Remove the schedule so the monitor only runs when triggered (overrides the run interval)                                                                                                                                                                              | bool                                                                                                                   | No       |
| name             | New name                                                                                                                                                                                                                                                              | str                                                                                                                    | No       |
| num\_results     | Search results per run (1-100)                                                                                                                                                                                                                                        | int                                                                                                                    | No       |
| include\_domains | Replace the included domains. Leave empty to keep the current list                                                                                                                                                                                                    | List\[str]                                                                                                             | No       |
| exclude\_domains | Replace the excluded domains. Leave empty to keep the current list                                                                                                                                                                                                    | List\[str]                                                                                                             | No       |
| contents         | Replace the per-result content options. Leave empty to keep the current ones                                                                                                                                                                                          | ContentSettings                                                                                                        | No       |
| output\_schema   | Replace the output format: a JSON Schema, or {"type": "text"} for a written summary. Leave empty to keep the current one                                                                                                                                              | Dict\[str, Any]                                                                                                        | No       |
| metadata         | Replace the metadata                                                                                                                                                                                                                                                  | Dict\[str, str]                                                                                                        | No       |
| clear\_metadata  | Remove all metadata (overrides metadata)                                                                                                                                                                                                                              | bool                                                                                                                   | No       |
| webhook\_url     | New webhook URL. HTTPS URL Exa posts each run to. To handle runs in a workflow, add an 'Exa Search Monitor Trigger' block to it, save, and paste that block's webhook URL here. Must be publicly reachable (no localhost or private IPs); redirects are not followed. | str                                                                                                                    | No       |
| webhook\_events  | Replace the webhook's subscribed events. Leave empty to keep the current ones                                                                                                                                                                                         | List\["monitor.created" \| "monitor.updated" \| "monitor.deleted" \| "monitor.run.created" \| "monitor.run.completed"] | No       |

### Outputs

| Output        | Description                                         | Type    |
| ------------- | --------------------------------------------------- | ------- |
| error         | Error message if the operation failed               | str     |
| monitor\_id   | The monitor's ID                                    | str     |
| status        | Status after the update                             | str     |
| next\_run\_at | Next scheduled run (ISO 8601); empty if manual-only | str     |
| monitor       | The updated monitor                                 | Monitor |

### Possible use case

**Pause and Resume**: Pause a monitor during a quiet period and set it back to active later.

**Query Refinement**: Tighten a monitor's query or domains after early runs return off-topic results.

**Webhook Move**: Point a monitor at a different Exa Search Monitor Trigger block's webhook URL when a workflow is rebuilt.

***


---

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