Sign in with social provider

Use this action to authenticate users with a third‑party provider (for example, Google or GitHub). If the email does not already exist and sign‑up is allowed, a new user is created.

Configuration

Display Key	Example Input	Description
Provider	google	The provider to use (e.g., google, github).
Redirect Page Optional	Dashboard page	Page to open after a successful sign‑in.
Error Redirect Page Optional	Error page	Page to open if the provider flow fails or is cancelled.
New User Redirect Page Optional	Onboarding page	Page to open on first sign‑in when a new user is created.
Disable Redirect Optional	false	If true, do not auto‑redirect after the provider completes.

Example flow

1. Add a “Continue with Google” button and attach a workflow.
2. Run “Sign in with social provider” with Provider: google (and optional redirect pages).
3. The provider window opens; the user completes the flow and returns to your app.
4. If the user already exists, they are signed in and redirected to the Redirect Page; if not, a new user is created and redirected to the New User Redirect Page.

Timeline

1

Add a “Continue with {provider}” button

2

Run Sign in with social provider with the provider and redirects

3

User completes provider flow and returns to your app

4

Route user to success, error, or first‑time destination

Related Event Triggers

The Sign in with social provider action will fire these Event Triggers

• On after sign in↗
• On after sign up↗

Use these triggers to run post‑login tasks (for example, update a lastSeenAt column or send analytics) and to create profile/role records for brand‑new users on first sign‑in.