They actually already ended the deprecation period and now they fully migrated to OAuth
Is it True that Airtable Accounts are Now Only Connected via OAuth, with API Keys Being Depreciated?
No possibility to use the auth via Airtable API tokens instead ?
What’s weird is that previously set-up Pipedream Airtable account using API key can be updated using API tokens.
So it seems you guys can maintain a API token authentification to Airtable even if keys are depreciated.
No sorry, from the support page I linked above:
This notice was originally published January 2023. As of February 1st, 2024, the deprecation period for Airtable API keys has ended. Users of Airtable API keys must migrate to the new authentication methods to continue using Airtable’s API.
You have to delete your actions using Airtable API and recreate them with Airtable OAuth
And triggers too
This is actually working
Re-creating all the Airtable steps using API keys is extremely painful btw as you have many to update and manually configure.
A solution on your side leveraging the usage of Airtable tokens (not keys to make things clear) would be amazing
I imagine there are differences between the PAT auth vs. the old API Key method, but that might be an option
But I’ll defer to
Yes I totally feel you, we have lots of users using Airtable and this change also affects us on the support side
I know this is not good practice but to avoid re-creating the Airtable steps with OAuth in workflows that uses Airtable account with API key, I just clicked on the 3 dots > Reconnect (see screenshot) > put the AT token instead of the API key and it’s working like a charm.
May be not so much dev required on your side after all ! Just a quick revamp of the Airtable via API key connexion towards API token.
That’s great! Thanks for letting us know
Please do let me know if you plan on releasing something soon for this data source !
(cc. )
Posted thread to Discourse: Is it True that Airtable Accounts are Only Connected via OAuth and API Keys are Being Deprecated?
Thank you for sharing this! Unfortunately I already switched all my workflows to use Airtable (OAuth) steps. Looks like it’s no longer possible to create a new step that uses the original Airtable connection.
My issue with the new Airtable (OAuth) steps is that the performance is significantly worse than the original Airtable steps — I am getting a lot of rate limit errors. My understanding is that the old version used the Airtable SDK which has built-in retries for rate limit errors. [As far as I know, there’s no reason why the new version couldn’t be rewritten to use the SDK — I really hope someone at Pipedream will look into this because I think it would help a lot with performance!]
My issue right now is that I have a bunch of v1 workflows that can’t be set to auto-retry on the workflow level, and I am sick of having to manually rerun due to rate limit errors, but also don’t have the capacity right now to switch everything over to v2. Even if I could, I have some time-sensitive workflows that would really benefit from getting retried after 30 seconds (to recover from an Airtable-imposed rate-limit delay) instead of 5 minutes (the default wait time for the workflow-level auto-retry that is available for v2 workflows).
, we’ve update the Airtable (OAuth) integration to use the SDK for better performance. Let us know how that goes!
Awesome, will do!