> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/create-a-task.md).

# Create a task

- [How a task works](https://docs.samita.io/bulk-price-editor-sami/create-a-task/overview.md): What a bulk edit task is made of and how the task form is organised.
- [Choose a field to edit](https://docs.samita.io/bulk-price-editor-sami/create-a-task/choose-a-field.md): The Choose a Field to Edit page and the full list of fields you can bulk edit.
- [Configure the edit](https://docs.samita.io/bulk-price-editor-sami/create-a-task/configure-the-edit.md): Name the task, choose an edit method and enter the new value.
- [Select products and variants](https://docs.samita.io/bulk-price-editor-sami/create-a-task/select-products.md): Choose which products and variants a task applies to, and exclude the ones you want to keep unchanged.
- [Preview the changes](https://docs.samita.io/bulk-price-editor-sami/create-a-task/preview.md): Check the current and new values for each product before you save a task.
- [Schedule, revert and save](https://docs.samita.io/bulk-price-editor-sami/create-a-task/schedule-and-save.md): Run a task now, save it for a manual start, schedule it, repeat it, and set an automatic revert.


---

# 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://docs.samita.io/bulk-price-editor-sami/create-a-task.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.