> 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/flow-settings/how-to-run-the-data-flows.md).

# Run the data flows

Learn how to run data flows in Coupler.io manually or on schedule. Check run history, view timestamps, and monitor whether source data has changed.

If you scheduled your Coupler.io data flows to automatically update your data, you might want to check the last time your data flow ran and when your data was imported.

Last run - date and time when your data flow last ran, and checked whether your data source had any changes

<i class="fa-right">:right:</i> For [**scheduled**](/functionality/flow-settings/how-to-set-up-automatic-data-refresh.md) **import**: your data will be saved to the destination each run or only by source data change (depends on the ["Update data each run"](/functionality/how-to-update-data-in-the-destination.md) setting).

<i class="fa-right">:right:</i> For **manual import:** Coupler.io will save data to your destination sheet each run (regardless of the settings and state of the data sources).

<i class="fa-right">:right:</i> For **imports triggered via** [**webhook**](broken://pages/BkClhff1Cd0BusgX7zEw): Coupler.io will save data to your destination sheet each run (regardless of the settings and state of the data sources).

There are several places where you can get information about when your data flows last ran and when they last imported your data.

#### 1. How to check the last run and last imported in Data Flow's view page <a href="#last-imported-view-page" id="last-imported-view-page"></a>

* Open [app.coupler.io/app/dataflows](https://app.coupler.io/app/dataflows).
* In the Data Flows list page, you can see when the last time the data flow ran and for scheduled data flows when the next run is going to happen:
* If you click the **'See details'** button, Data Flow's view page opens. You can find your last run date and time there. If you hover your cursor over the time, you can see the exact date and time:

{% columns %}
{% column width="66.66666666666666%" %}

<div align="left"><figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2FjUzTwYeKkGM4a2r13vlG%2Fimage.png?alt=media&amp;token=719b5052-48dc-499c-a4bc-c30208db730f" alt="" width="375"><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="33.33333333333334%" %}

<figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2FifL8dgfKTILL9549agDJ%2Fimage.png?alt=media&amp;token=7e222c16-62c1-445b-a01f-3a309a1ed232" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

#### 2. How to check the last run in the Google Sheets add-on <a href="#last-imported-add-on" id="last-imported-add-on"></a>

Each data flow in the add-on dashboard has the last run date and time. If you click on the little arrow on the right side, more information is displayed:

<div align="left"><figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2FaPSvLG2cWqatYb23R41G%2Fimage.png?alt=media&amp;token=b83b0705-69e8-4a35-b830-e9468cd016b3" alt="" width="297"><figcaption></figcaption></figure></div>

You can also see the last imported date in the first cell of the imported data:

<div align="left"><figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2F7lPVrDXwQK2j49DZT2jw%2Fimage.png?alt=media&amp;token=6db2377e-f149-4556-89a9-4d88b85f65a5" alt="" width="328"><figcaption></figcaption></figure></div>

This notification is located in the first cell of your destination sheet. It specifies the date and time when data in this sheet was last updated.


---

# 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/flow-settings/how-to-run-the-data-flows.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.
