> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/quick-add.md).

# Quick Add

Manually send history, ratings, and watchlist actions to one or more providers for titles watched outside your usual media server flow.

Quick Add sends one-off actions for a movie, show, or selected episodes. An eligible connected account can receive an action without belonging to a sync pair. This does not create a pair or enable automatic synchronization.

Use it for watches that happened outside your normal server flow.

{% hint style="info" %}
Quick Add is available in **v0.9.18 and later**.
{% endhint %}

{% tabs %}
{% tab title="End users" %}

### What it does

Quick Add can send:

* **Watched**
* **Watchlist**
* **Rating**
* **Collection**

You can send one action or combine them.

Typical use cases:

* cinema visits
* travel or offline viewing
* missed scrobbles

### How to use it

{% stepper %}
{% step %}

### 1. Find the title

Choose **Movies** or **Shows**.

Search TMDb and pick the right result.
{% endstep %}

{% step %}

### 2. Choose the action

Under **What**, select **Watched**, **Watchlist**, **Rating**, **Collection**, or a mix. Only supported actions are offered.
{% endstep %}

{% step %}

### 3. Fill the extra fields

For **Watched** or **Collection**, choose the date under **When**.

If you use **Rating**, choose the destination accounts and then select a score. The available scores follow those providers’ rating scales. With several destinations selected, only shared scores are offered; if none are shared, rate the providers separately.
{% endstep %}

{% step %}

### 4. Pick providers

Under **Where**, select the accounts that should receive the action. Additional accounts appear under **Other accounts**, using the names you assigned in Connections. The choices follow the selected Profile and your access permissions.
{% endstep %}

{% step %}

### 5. Send it

Review the existing-state notes, then use the action button. Its label reflects your choice, such as **Mark watched on 2 providers**, **Add to collection on 1 provider**, or **Save on 2 providers** for combined actions.
{% endstep %}
{% endstepper %}

### Notes

* **Desktop** uses the side launcher.
* **Mobile** uses the floating button on **Main**. In Tracker, use **More add options** beside **Log a watch**.
* The **+** on a title's provider tile opens Quick Add with that title and action selected. It offers eligible accounts outside that feature's sync pairs.
* Where offered for a show, choose **Whole show** or **Pick episodes**. Use **Episode list** to choose the numbering source. TMDb episode selections can go to compatible destinations; a provider-specific episode list can only be sent back to that provider.
* For a movie or selected episodes already watched on a destination, the notes explain whether sending adds a rewatch or skips history because that destination keeps one play. A rating can replace the existing score.

### Limits

* Quick Add depends on TMDb search.
* Provider support differs by action.
* Rating needs a valid score before sending.
  {% endtab %}

{% tab title="Power users" %}

### Action behavior

* **Watched** writes History for the selected movie, show, or episodes.
* **Watchlist** adds it to provider watchlists.
* **Rating** sends the selected score.
* **Collection** adds the title to a supported collection.

Actions are checked per provider.

Unsupported actions are skipped for that provider.

Nuvio supports **Watchlist** and **History** actions. It does not support ratings.

### Provider selection

Only configured providers are shown.

Multi-instance providers are supported.

CrossWatch can restore your last provider selection.

You can also use:

* **Select all**
* **Clear**

### Watched date options

For **Watched** or **Collection**, you can use:

* **Today**
* **Release date**
* **Choose date**

**Release date** uses TMDb metadata.

It does not represent when you personally watched the item.
{% endtab %}
{% endtabs %}

### Related topics

* [Main dashboard](https://wiki.crosswatch.app/crosswatch/main-dashboard.md)
* [Watchlist](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/watchlist.md)
* [Dashboard widgets](https://wiki.crosswatch.app/crosswatch/main-dashboard/dashboard-widgets.md)


---

# 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://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/quick-add.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.
