> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/functionality/how-to-update-data-in-the-destination.md).

# Update data in the destination

Choose how Coupler.io updates your destination data: refresh on every scheduled run, or update only when source data has changed. Learn how each mode works.

Coupler.io supports two approaches to scheduled data updating in the destination update data each run and Update data only if the source data has changed

#### Update data each run <a href="#update-each-run" id="update-each-run"></a>

To use this approach - enable the "Update data each run" setting during the importer's setup:

<div align="left"><figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2F1Lm65YUHiPyhqSPzmFqX%2Fimage%20(3).png?alt=media&amp;token=06836e34-d80d-4620-870d-176a3196a5fc" alt="" width="375"><figcaption></figcaption></figure></div>

Once you define a schedule for the importer with this setting, Coupler.io **will update your data in the destination sheet each time the importer is executed**. If you set up an importer to run hourly, Coupler.io runs every hour, pulls your data, and saves it to the destination.

#### Update data only if the source data has changed <a href="#update-when-data-changed" id="update-when-data-changed"></a>

In Coupler.io terms, "*the source was changed*" means:

* new data added
* old data updated
* data order is changed
* etc.

The logic behind this is that Coupler.io calculates the hash of your data and compares it during runs. So even adding space to some secondary field you don't care about is counted as data change.

To use this approach, disable the "Update data each run" setting during the importer's setup.

Once you define a schedule for the importer with this setting, **Coupler.io will update your data in the destination sheet only if it has changed in the data source** since the last time our tool imported it. If you set up an importer to run hourly, Coupler.io runs every hour, pulls your data, and checks whether something has changed or not.

If your data updates only once per day (in your data source), Coupler.io will update it in your destination only once per day as well (even if you set up data refresh frequency to 1 hour).

#### **FAQ**

<details>

<summary>How is data updated when I run the importer manually?</summary>

When you run an importer manually, Coupler.io will rewrite data in your destination sheet because you asked it to do so (not because your data changed from the previous time Coupler.io had pulled it over to the destination).

</details>

<details>

<summary>How is data updated when the importer is triggered by a webhook?</summary>

Once your importer is triggered by a [webhook](broken://pages/BkClhff1Cd0BusgX7zEw) - Coupler.io will update data in the destination without checking if the data has changed or not, so you can be sure that your automation flows are working with the newest data.

</details>


---

# 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.coupler.io/functionality/how-to-update-data-in-the-destination.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.
