Feb 12, 2023 03:25 PM
I created a new token and tried to use it to replace my API key in a Zapier app connection for Airtable. Thought I was doing the right thing in preparation for the deprecation in 2024. It didn't work. Zapier doesn't seem to recognise the token and wouldn't accept it.
Likewise tried to use tokens in direct connections with other subscriber apps. They didn't accept them either.
I'm missing something fundamental here right? Grateful for any help.
Solved! Go to Solution.
Feb 12, 2023 08:13 PM
Zapier probably hasn't implemented support for the new token system yet as it's a fairly new introduction. You might want to open support tickets with Zapier and your other subscriber apps asking whether they support it?
Feb 12, 2023 08:13 PM
Zapier probably hasn't implemented support for the new token system yet as it's a fairly new introduction. You might want to open support tickets with Zapier and your other subscriber apps asking whether they support it?
Feb 19, 2023 03:42 PM
Thanks for your response Adam @TheTimeSavingCo
I'm surprised there isn't more discussion about this in the community. Maybe it will ramp up now that "Notice of Airtable API Key Deprecation" email has gone out. I'm immediately getting queries from current and past clients.
Perhaps we can have a thread tracking when the most prominent integrating products ar eupdated to handle the new tokens (Zapier and Make at the top of the list).