Is there any way to connect to multiple Airtable workspaces in the same WeWeb project? Using the the Airtable plugin appears to only be able to allow one connection.
Hi @EvilHIdden 
Indeed, you can only setup the Airtable plugin with one personal access token?
However, if your personal access token gives you access to multiple bases from multiple workspaces, you should be able to interact with all of them in your WeWeb project.
For example, with this token, I could work on 3 bases in one WeWeb project even though each one is in a different Airtable workspace:
Hope that helps!
Thanks @Joyce! Always appreciate your replies. Yes, that would definitely work, however if that wasn’t available as an option - would you see any issues/drawback from using standard REST API calls directly to Airtable along side the official Airtable plugin?
My pleasure! 
I would strongly advise against that approach because the API calls you make with our REST API plugin are frontend calls, meaning the info used to make the call is visible in the browser’s inspector, meaning your private access token could be found very easily, meaning people could access your Airtable data 
So if you needed to work with different Airtable access tokens in a single WeWeb project, I’d recommend:
-
creating the call to Airtable in a backend or automation tool like Xano, Supabase or Zapier, Make (i.e. a place that can store the private access token securely) and,
-
in WeWeb, make the API call to Xano or Zapier to trigger the call.
Does that make sense?
Here’s an article that talks more about when and where to make API calls with public or private keys: https://www.weweb.io/blog/securely-using-api-keys-from-a-frontend-no-code-app
Yup. Makes total sense, and it’s what I figured I’d had to do if I had to go this way. Always good to get confirmation on a security choice. Thanks. Keep up the great work!
1 Like