# Import from Airtable contains no rows

**URL:** <https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958>\
**Category:** APIs\
**Created:** [June 26, 2025, 8:18pm UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958 "2025-06-26T20:18:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dood](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@Dood](https://community.nocodb.com/u/Dood)\
**Post date:** [June 26, 2025, 8:18pm UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/1 "2025-06-26T20:18:42Z")

</div>

Trying to import from Airtable but after the import I see all the tables & columns but they all contain no rows. Verified the share URL works & tried recreating the token making sure it has data.records:read and schema.bases:read permissions. Any ideas?

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [June 28, 2025, 1:16am UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/2 "2025-06-28T01:16:47Z")

</div>

“schema.bases.read” permissions is also not required. NocoDB infers schema details from the Shared Base URL

- Delete all tables created in this base & retry.
- Download logs & share to help us reproduce this issue. After import is complete, you can say ‘show-details’ and then download logs

 ![Screenshot 2025-06-28 at 6.17.21 AM](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/6de629edcd9661eab63a75ee7be4cce1896a96bf.png)

---

<div class="post-metadata">

**Author:** ![Dood](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@Dood](https://community.nocodb.com/u/Dood)\
**Post date:** [June 28, 2025, 2:14am UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/3 "2025-06-28T02:14:34Z")

</div>

Deleted all bases. Did import. Still fails.

WARNING: There were errors on reading ‘houses’ data :: You should provide valid api key to perform this operation(AUTHENTICATION\_REQUIRED)[Http code 401]

---

<div class="post-metadata">

**Author:** ![Dood](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@Dood](https://community.nocodb.com/u/Dood)\
**Post date:** [June 28, 2025, 2:24am UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/4 "2025-06-28T02:24:38Z")

</div>

Recreated url & api a few times & it finally went further, but still 0 records in every table.  
How do I upload the log? Website only allows images  
I see lots of this line in the log:  
WARNING: There were errors on importing ‘houses’ data :: Error: Column “Open URL” is virtual and cannot be updated

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [June 28, 2025, 4:13am UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/5 "2025-06-28T04:13:43Z")

</div>

Issue is noticed when importing button field. Created an issue to track it further  
[🐛 Bug: Error importing button field from airtable](https://github.com/nocodb/nocodb/issues/11775#top)

Meanwhile, you can try removing button field from “houses” table & adding it back later in NocoDB directly.

---

<div class="post-metadata">

**Author:** ![Dood](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@Dood](https://community.nocodb.com/u/Dood)\
**Post date:** [June 28, 2025, 1:48pm UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/6 "2025-06-28T13:48:28Z")

</div>

OK Removing the button field enabled the import.

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [June 30, 2025, 7:57am UTC](https://community.nocodb.com/t/import-from-airtable-contains-no-rows/1958/7 "2025-06-30T07:57:29Z")

</div>

A fix is in place to handle this & will be available from our next release.
