# Find airtable record

**URL:** <https://community.weweb.io/t/find-airtable-record/2088>\
**Category:** Ask us anything\
**Created:** [March 21, 2023, 4:30pm UTC](https://community.weweb.io/t/find-airtable-record/2088 "2023-03-21T16:30:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AmbroiseDhenain](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ambroisedhenain/32/2609_2.png) [@AmbroiseDhenain](https://community.weweb.io/u/AmbroiseDhenain)\
**Post date:** [March 21, 2023, 4:30pm UTC](https://community.weweb.io/t/find-airtable-record/2088/1 "2023-03-21T16:30:59Z")

</div>

I am unsure about the proper workflow to use.

I have setup an Airtable collection, I have all my data available.  
I want to setup a page which uses the airtable record id in the url, that is done.  
But then, how do I get the data of the “current record”?

I guess I need to create a variable “currentRecord” and store the current record object there, but how do I do that?

---

<div class="post-metadata">

**Author:** ![chadsmithclt](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chadsmithclt](https://community.weweb.io/u/chadsmithclt)\
**Post date:** [March 21, 2023, 6:13pm UTC](https://community.weweb.io/t/find-airtable-record/2088/2 "2023-03-21T18:13:30Z")

</div>

Does this help?

[![](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/f5154ca597fd658d8a491a980320b25f75629c5f.jpeg "How to create pages dynamically in WeWeb") ](https://www.youtube.com/watch?v=uAek6r5N9ug)

---

<div class="post-metadata">

**Author:** ![AmbroiseDhenain](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ambroisedhenain/32/2609_2.png) [@AmbroiseDhenain](https://community.weweb.io/u/AmbroiseDhenain)\
**Post date:** [March 21, 2023, 6:31pm UTC](https://community.weweb.io/t/find-airtable-record/2088/3 "2023-03-21T18:31:18Z")

</div>

Thank you! Creating a different collection for a single item is what I was missing, as it really doesn’t make much sense from a developer point of view (we already have the data, why fetch them again?) but no-code 🤷

---

<div class="post-metadata">

**Author:** ![chadsmithclt](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chadsmithclt](https://community.weweb.io/u/chadsmithclt)\
**Post date:** [March 21, 2023, 6:41pm UTC](https://community.weweb.io/t/find-airtable-record/2088/4 "2023-03-21T18:41:02Z")

</div>

Working in Xano may give more flexibility here since you can define your own APIs

---

<div class="post-metadata">

**Author:** ![AmbroiseDhenain](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ambroisedhenain/32/2609_2.png) [@AmbroiseDhenain](https://community.weweb.io/u/AmbroiseDhenain)\
**Post date:** [March 21, 2023, 6:47pm UTC](https://community.weweb.io/t/find-airtable-record/2088/5 "2023-03-21T18:47:04Z")

</div>

The issue isn’t really with Airtable/Xano in this specific case, it’s more with about how WeWeb is built and what it allows.

Sounds like it’s recommended to read Airtable again, rather than filtering a collection that’s already fetched, simply because filtering the collection is more complicated to do than re-fetching.