Clear instructions for changing Airtable API to OAuth?

Following up on the changes at Airtable, could someone please provide some clear instructions on how to change an existing app from linking to Airtable via API to linking via OAuth?
I can see the instructions in Glide Docs on how to link with a new app, but I have an existing one linked through API and am worried I’ll break it!
There are a few posts in the community forum, but it’s not clear if any of them are correct.

1 Like

Here’s the official word from the team.

Here are the steps from @parisiam .

1 Like

ok - those were the posts I had seen, but wan’t sure if they were the correct steps as no-one had confirmed? If they are, I will follow them.

I think it worked for @parisiam . Hope he can weigh in here if you need further assistance.

Yes, it worked. I just had a slight problem in the end to remove the API connection and the support had to step in. But I’m on the OAuth connection since and it’s fine.

1 Like

I have the same issue with an existing an operational application linked to Airtable.
Therefore, I need to plan the switch to OATH well in advance.

Glide Team, could you please provide us with the detailed instructions to perform the migration?


Can you check if the solution written by @parisiam in the linked threads work for you?

I just check it out and it doesn’t seem to work. When I select “Add another Airtable account” a pop-up window asks me to confirm the base I shroud connect against.
Since the base is the same, nothing happens. No request for authorization is requested and the existing API connection is still there.

I can I progress about?


Can we have a video for people to follow through this @BrettH @JackVaughan ?

We have a section dedicated to connecting to AT, but I will check with the team and see if we can add more information RE Oauth.

1 Like

Hi ThinDinh,

Thank for your message but unfortunately it’s not answering to my question: How to migrate and existing (and operational) app from API auth to OATH.

Looking forward to getting your valuable reply.



Hi Luke, when Brett checks with the team and has something to update, he will let you know. Sorry I have no further info to add.

@Lukeduke Try these steps:
Switching from Airtable API Key to OAuth authentication:

  1. In your browser, open your account and make sure the current user has read/write access to the base used in your Glide app.
  2. In a second browser tab, sign into your Glide account at
  3. Navigate to the team containing your Airtable based apps.
  4. In the dashboard, click New app in the same team.
  5. On the Select a source popup, select Glide Tables and click Create app.
  6. After the app opens, navigate to the Data page.
  7. On the left side of the page, click the plus sign (+) to the right of TABLES and choose Airtable in the dropdown.
  8. In the Select an Airtable Base popup, click the dropdown and select + Add another Airtable account.
  9. A new browser tab titled Glide is requesting Airtable access should open. Click + Add a base, select the same base used in your original app, and then click Grant access.
  10. The tab Glide is requesting Airtable access should close, showing the Select an Airtable Base popup again. Below the dropdown, it should now say Edit Airtable Integration. Below the title AIRTABLE BASES, select the base you want the app to use and click Add Source.
  11. This should switch Airtable authentication to OAuth for all apps in the team.
  12. When you leave the new app and navigate back to your app, you don’t have to do anything to get OAuth working in it. Just open the Data page and click the Manual Sync arrow button to the right of Airtable under the title **DATA SOURCES (**bottom left corner of the page).
  13. NOTE: If you click the plus sign (+) to the right of TABLES and select Airtable, the UI defaults to showing the defunct API Key in the dropdown. This is a known bug that will be fixed. At this point, the app is already using OAuth. You should ignore the API Key entry and not use it anymore.

Hi Brett,

Thank you very much for reply and the detailed steps you shared.

I thouroughly followed them (in a Google Chrome enviroment), it went well till step 12 where I got the error message attached.

Would you please help me to fix it up?




This will not be possible to resolve here - You are going to have to open a support ticket I’m afraid.


Tnka you for your answer.

Anyway, I managed to sort it out, at the moment.

The issue has been caused by the different ownership of some tables, since I created some tables with an Airtable adminstrator and then , due to company constraints, I had to change the administrator of the Airtable base.

Now, to let it work I have two admin-level user in airtable, which is not the best case. If I remove the old admin user a 1035 error occurs in Glide manual sync.

So, the question is: How can I relink Glide to the new Airtable Workspace I created having the latest admin user only?



Many thanks for these instructions. I have followed them step by step and everything looks normal. Is there any way to double check that the OAuth authentication is being used - just to be sure??

Thanks, Brett. I followed the instructions but now when I click on the + icon next to the tables list in Data, it shows me my current API-key based account as selected and a new Airtable connection unchecked. Is this what you mean by the UI bug? I also tried to locate this new connection in the Airtable developer hub under OAuth integrations and the list is still empty. I worry that Glide connection hasn’t been hooked properly.

Can you help clarifying this @NoCodeAndy ? Thank you.

I think this is very unclear on an issue that is forced to do. I have several bases in Airtable that syncs with different Glideapps today via the APIkey. When I now is started to change to OAuth it is very unclear in which way the sync between Airtable and Glide is performed. Is it via APIkeys or OAUTH is impossible to know.
And I also discovered another issue. When I want to add a new Airtabelbase to sync with a new app, I need to add all of the Airtablebases again because it is on the same OAuth key and same Airtable account.