Return

Enable Google sign in (SSO)

Let users sign in with Google and test the flow in your app.

Steps at a glance

1. Create a Google OAuth app in the Google Cloud Console.
2. Add the right Google origins and callback URLs.
3. Paste the Google credentials into WeWeb.
4. Add a Google sign-in action to your interface.
5. Test the full sign-in flow.

1) Create a Google OAuth app

1. Open the Google Cloud Console.
2. Create a project or select an existing project.
3. Open APIs & Services.
4. Open OAuth consent screen and complete the setup:
   • Choose External for most public apps.
   • Add your app name and support email.
   • Add your domain in Authorized domains if Google asks for it.
5. Go to Credentials.
6. Click Create credentials and choose OAuth client ID.
7. Choose Web application.
8. Keep this page open because you will add your domains and callback URLs in the next step.

2) Add redirect URLs

Google needs two values for each place where users can start sign in:

• An Authorized JavaScript origin
• An Authorized redirect URI

Use this pattern:

Where users start sign in	Authorized JavaScript origin	Authorized redirect URI
WeWeb editor project	https://<your-project-id>-editor.weweb.io	https://<your-project-id>-editor.weweb.io/api/auth/callback/google
Published app	https://your-domain.com	https://your-domain.com/api/auth/callback/google
Preview or staging app	https://your-preview-domain.com	https://your-preview-domain.com/api/auth/callback/google

1. Decide which environments need Google sign in.
2. In Google, add each full domain to Authorized JavaScript origins.
3. In Google, add the matching full callback URL to Authorized redirect URIs.
4. Click Create.
5. Copy the Client ID and Client secret.

WHAT GOOGLE SHOULD RECEIVE

If your app lives at https://my-app.com, the Google callback URL should be:

https://my-app.com/api/auth/callback/google

3) Connect Google in WeWeb

1. In WeWeb, open Data & API -> Auth -> Integrating providers.
2. Open the Google provider.
3. Turn on Enable.
4. Paste:
   • Client IDs - Your Google Client ID
   • Client Secret (for OAuth) - Your Google Client secret
5. Save your changes.

4) Add Google sign in to your interface

1. In the Interface tab, add a button such as Continue with Google.
2. Create a workflow on click.
3. Add the Sign in with social provider action.
4. Set:
   • Provider To google
   • Redirect Page To the page users should see after sign in
   • Error Redirect Page If you want a dedicated error page
   • New User Redirect Page If you want first-time users to go somewhere different

5) Test sign in

1. Preview your project.
2. Click your Google sign-in button.
3. Sign in with a Google account that is allowed to use your Google app.
4. Confirm that:
   • The Google sign-in window opens without a redirect error.
   • You return to the correct page in your app.
   • The user is authenticated in WeWeb.

If your Google app is still in testing mode, make sure the Google account you use is added as a test user in the Google Cloud Console.

Common pitfalls

Redirect URI mismatch

If Google shows a redirect_uri_mismatch error, the redirect URL used by your app does not match what you configured in the Google Cloud Console.

Confirm the value in Authorized redirect URIs is the full callback URL, such as https://your-domain.com/api/auth/callback/google.

Wrong domain or environment

If sign in works in one environment but not another, check that:

• Each environment has both entries added in Google.
• The full origin is listed in Authorized JavaScript origins.
• The same origin plus /api/auth/callback/google is listed in Authorized redirect URIs.
• You updated Google if you changed your editor domain, preview domain, or custom domain.

Using the success page as the Google callback

The Success page in the Sign in with social provider action is not the value you paste into Google.

• Google needs the fixed WeWeb callback URL: https://<origin>/api/auth/callback/google.
• The action page settings only decide where the user lands after that callback is complete.

Missing test users on the Google consent screen

If your Google app is still in testing mode, only approved test users can sign in.

1. Open APIs & Services -> OAuth consent screen.
2. Add your test Google accounts before trying the flow.

Need more detail?

For the full setup guide, examples for editor and published domains, and more troubleshooting, see Google authentication ->.

Related guides

Using user roles

Control what users can see and do by assigning roles and checking them in your app.

Beginner7 min

Securing APIs

Protect your APIs so only the right users can access sensitive data.

Beginner7 min