# Is there a variable I can use to Identify a flow run?

**URL:** <https://connective.celigo.com/t/is-there-a-variable-i-can-use-to-identify-a-flow-run/603>\
**Category:** Integrator.io\
**Tags:** export, flow-builder\
**Created:** [November 14, 2022, 6:36am UTC](https://connective.celigo.com/t/is-there-a-variable-i-can-use-to-identify-a-flow-run/603 "2022-11-14T06:36:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexbaeza](https://avatars.discourse-cdn.com/v4/letter/a/ecd19e/32.png) [@alexbaeza](https://connective.celigo.com/u/alexbaeza)\
**Post date:** [November 14, 2022, 6:36am UTC](https://connective.celigo.com/t/is-there-a-variable-i-can-use-to-identify-a-flow-run/603/1 "2022-11-14T06:36:31Z")

</div>

I would like to keep of all of the API result sets from an export.

So if I call the export today and it returns 10 records, and I call it again tomorrow and it returns 12 records, I would like my history table to contain 22 records (even though 10 may be duplicates).

I would like the history table to have all the columns mapped from the export, plus an extra column to identify which flow execution loaded the data.

I have tried using this mapping:

 ![5301043caa20740200000001-9af6b8015a404c9e8afc97c90fc8ae44.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/f/ff2ad55855016207b6c7723cd0e745430d4ee73f.png)

but timestamp appears to update for each page of records returned by the API.

I would like something more like {{flow startdate}}. Or maybe {{flowname}}-{{started}} or {{flowid}}-{{started}}.

Does something like this exist?

---

<div class="post-metadata">

**Author:** ![anithaabraham](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/anithaabraham/32/6964_2.png) [@anithaabraham](https://connective.celigo.com/u/anithaabraham)\
**Post date:** [January 11, 2023, 8:11am UTC](https://connective.celigo.com/t/is-there-a-variable-i-can-use-to-identify-a-flow-run/603/2 "2023-01-11T08:11:47Z")

</div>

@alexbaeza Sorry, we missed this one. We don't yet have this support to identify the flow run. We've created a feature request for our engineering team to consider. We really appreciate your feedback!