I enabled Google SSO sign-up today. Previously, I’d used only manual sign-up and I had a few hidden fields that would pre-fill new users’ profiles with some information. They could then edit this information as they wanted.
But with Google SSO, those hidden fields are not pushed through to my Airtable. Further, Google SSO pulls in their name from their Google account (not just their email) when I’d prefer it not do that (users for my app may not want to use their real name here).
I should note: I’ve managed to build an automation on the database (Airtable) side to pre-fill this information. But if there’s any slowness there, the user on my Softr app gets to their profile page before Airtable has managed to run that automation. It’s more fool-proof if the data comes from Softr, so that the profile page will not even load before this data has been sent to Airtable. Make sense?
So I’d prefer to send this data from Softr at the time of sign-up rather than use an automation on the Airtable side.
+1
I am having the same issue as well. This is particular to the sign-up forms because this is where some user role info is pushed through to the account record