> 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_import_update.md).

# Exa Websets Import Update

Blocks for renaming Exa Websets imports and replacing their metadata.

## Exa Update Import

### What it is

Update the title or metadata of an Exa Websets import

### How it works

This block sends a PATCH to the Websets API's `/v0/imports/{id}` with only the fields you set, so anything left empty stays as it is. Metadata is replaced as a whole, not merged. The imported data itself can't be changed after upload; create a new import for that.

If neither a title nor metadata is set, the block fails before calling Exa. It returns the import's status, title, metadata and update time as Exa reports them after the change. It charges only if Exa's response reports a cost (150 credits per USD).

### Inputs

| Input      | Description                                                                                   | Type            | Required |
| ---------- | --------------------------------------------------------------------------------------------- | --------------- | -------- |
| import\_id | The ID of the import to update                                                                | str             | Yes      |
| title      | New title for the import. Leave empty to keep the current one.                                | str             | No       |
| metadata   | Key-value pairs that replace the import's metadata. Leave empty to keep the current metadata. | Dict\[str, str] | No       |

### Outputs

| Output      | Description                                                       | Type            |
| ----------- | ----------------------------------------------------------------- | --------------- |
| error       | Error message if the operation failed                             | str             |
| import\_id  | The ID of the updated import                                      | str             |
| status      | Import status: pending, processing, completed, failed or canceled | str             |
| title       | The import's title after the update                               | str             |
| metadata    | The import's metadata after the update                            | Dict\[str, Any] |
| updated\_at | When the import was last updated                                  | str             |

### Possible use case

**Clear Naming**: Rename an import after upload so it is easy to find when attaching it to websets.

**Provenance Tracking**: Store the source system and upload date in the import's metadata.

**Status Check After Edit**: Confirm an import is completed while updating its title in the same step.

***


---

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