# \[Action Required\] Reconnect Airtable OAuth

**URL:** <https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477>\
**Category:** Ask for Help\
**Tags:** airtable\
**Created:** [May 18, 2024, 11:49am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477 "2024-05-18T11:49:20Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 18, 2024, 11:49am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/1 "2024-05-18T11:49:21Z")

</div>

I received an automatic message from Glide asking asking me to reauthenticate to Airtable.

 ![CleanShot20240518-134107](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/6/56c543d47724d4d930a9605c82f1321b39282d15.jpeg)

I clicked the button in the email, but send me to a page that keeps loading and stays stuck.  
I tried to click the button while being logged in to Glide, logged out. But nothing.  
I tried to send a message to the support, but no answer neither.

As the message indicates, all the apps (5 of them) that were connected to the Airtable base are no longer synchronizing with Airtable.  
So basically, my apps are no longer working (it’s been 3 days already).

I’m on a legacy non-profit plan.  
There’s not much traffic on the apps right now, so it’s not a problem of limitations of rows or capacity (I’m far below).

Has anyone seen and resolve this problem ?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [May 18, 2024, 11:52pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/2 "2024-05-18T23:52:27Z")

</div>

Can you check if this helps?

> [@\[Action Required\] Airtable API Key Deprecation Notice](https://community.glideapps.com/t/action-required-airtable-api-key-deprecation-notice/69918):
>
> [As announced by Airtable](https://support.airtable.com/docs/airtable-api-key-deprecation-notice), API keys can no longer be used to connect to Airtable bases. Airtable bases must be reauthenticated with OAuth for your Glide apps to continue syncing. If our systems detect that you need to switch from API key to OAuth authentication, you will receive an email explaining which bases and team members must reauthenticate their credentials. If the team member is no longer part of your Glide team, please contact [Support](https://www.glideapps.com/support). Additional Details Every Airtable base connected…

---

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 19, 2024, 6:29am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/3 "2024-05-19T06:29:32Z")

</div>

Thanks for stepping in.  
I already moved from API to OAuth long ago (I even had to do it twice with the help of the support).  
So I think it’s something else.  
And the restore button and link provided in the mail I received from Glide is simply not working, which is why I contacted directly the support first (but with no response so far).

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 19, 2024, 6:44pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/4 "2024-05-19T18:44:59Z")

</div>

Thanks for posting! I’m asking our Support team to look into it.

---

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 20, 2024, 7:18am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/5 "2024-05-20T07:18:57Z")

</div>

Thank you!  
The team concerned is named SOUND.AI and the concerned apps are shown below :

 ![CleanShot20240520-091724](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/9/e9c70ac0a486f23663a8cd6a2c7dc0e30bff0857.jpeg)  
All the apps are connected to the same Airtable base.

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 20, 2024, 5:55pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/6 "2024-05-20T17:55:36Z")

</div>

Could you try using this URL? It should trigger the reauthentication process

[https://go.glideapps.com/reauthorizeplugin/airtable](https://go.glideapps.com/reauthorizeplugin/airtable)

---

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 20, 2024, 8:20pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/7 "2024-05-20T20:20:18Z")

</div>

I quickly tried and it seems to work.  
I’ll make more extensive tests tomorrow.  
If it is confirmed, I’ll mark your answer as the solution.  
Thanks 🙏

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 20, 2024, 9:17pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/8 "2024-05-20T21:17:00Z")

</div>

That’s great! It is the same URL as from the email, but there might have been an issue.

Let us know if you run into future problems

---

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 22, 2024, 7:04am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/9 "2024-05-22T07:04:26Z")

</div>

For the record, I don’t know if the following factors had a role for the solution to work, but before clicking the link:

- I connected to the Glide account with the email that created the connection to Airtable in the first place
- I opened the team which contained the apps connecting to the Airtable base

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 22, 2024, 8:15pm UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/10 "2024-05-22T20:15:56Z")

</div>

Ah, that’s it. You must be logged into the account that originally created the connection for the re-authentication process to work. Everything good so far?

---

<div class="post-metadata">

**Author:** ![parisiam](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/parisiam/32/83734_2.png) [@parisiam](https://community.glideapps.com/u/parisiam)\
**Post date:** [May 23, 2024, 8:13am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/11 "2024-05-23T08:13:09Z")

</div>

It seems so, thanks for asking !

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [May 30, 2024, 8:13am UTC](https://community.glideapps.com/t/action-required-reconnect-airtable-oauth/73477/12 "2024-05-30T08:13:56Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
