# Force sync a particular table (or alternatively single record) via API

**URL:** <https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389>\
**Category:** Feature Requests\
**Created:** [October 29, 2024, 2:44pm UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389 "2024-10-29T14:44:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\
**Post date:** [October 29, 2024, 2:44pm UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389/1 "2024-10-29T14:44:33Z")

</div>

I use Xano. When a record is created in Xano, independently of Noloco (so via Xano API), it takes a while to sync back to Noloco. I know I could create the record via the Noloco GraphQL API, then it’ll sync straight back to Xano, but sometimes this makes everything much more complex. Ideally I’d like to be able to force Noloco to sync a particular table after a new record has been created. Thanks!

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [October 29, 2024, 2:54pm UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389/2 "2024-10-29T14:54:39Z")

</div>

Thanks for the suggestion @lukebranford - ultimately this wouldn’t be much quicker than what’s currently happening, because for Xano we need to go through all of the records and identify the new ones, the updated ones and the deleted ones.

---

<div class="post-metadata">

**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\
**Post date:** [October 29, 2024, 2:57pm UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389/3 "2024-10-29T14:57:35Z")

</div>

Ah, gotcha, no worries, makes sense! I just didn’t know how often it tried to sync the changes. Thanks for the quick reply though 🙂

---

<div class="post-metadata">

**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\
**Post date:** [January 13, 2025, 10:26am UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389/4 "2025-01-13T10:26:09Z")

</div>

This continues to be an issue for me so suggesting a potential workaround. Because the record has been created in Xano, I know its ID, so an ideal scenario would be to somehow tell the Noloco API to import that record (based on ID), avoiding the need for Xano to go through all the records. Not sure if feasible, but thought it worth requesting as would solve all my major Xano issues!

---

<div class="post-metadata">

**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\
**Post date:** [January 14, 2025, 2:39pm UTC](https://community.noloco.io/t/force-sync-a-particular-table-or-alternatively-single-record-via-api/1389/5 "2025-01-14T14:39:55Z")

</div>

@darragh is the above something that sounds feasible? I’m just considering whether I update a couple of my Xano workflows to use the Noloco API rather than creating records in Xano.