Google Auth Settings

Reached from Configuration → Integrations → Google, an Owner-only page that lets visitors sign in — or register — with their Google account, using credentials from your own Google Cloud project.

Entirely optional. Until this is configured and enabled, Threadline's Google sign-in URLs simply 404 and no "Continue with Google" button is shown anywhere — regular email/password registration and login are unaffected either way.

1. Create OAuth credentials in Google Cloud

  1. Go to console.cloud.google.com and create (or select) a project.
  2. Under APIs & Services → OAuth consent screen, configure the consent screen (app name, support email) if you haven't already.
  3. Under APIs & Services → Credentials, click Create Credentials → OAuth client ID.
  4. Choose Web application as the application type, and give it a name (e.g. "Threadline").
  5. Under Authorized redirect URIs, add exactly: 
    https://yourdomain.com/auth/google/callback
    replacing yourdomain.com with your actual Site URL from installation. This must match exactly — including https:// and no trailing slash — or Google rejects the sign-in attempt.
  6. Click Create. Google shows a Client ID and Client secret — copy both.

2. Enter your credentials in Threadline

  1. Paste the Client ID and Client secret into their fields on this page.
  2. Switch on Enable Google Auth.
  3. Click Save.

Both fields are required for the button to appear. The "Continue with Google" button never shows up until a Client ID and Client secret are both saved — regardless of whether the Enable Google Auth switch itself is on. Once saved, the secret is never shown again, only a masked hint (its last 4 characters); leave it blank on a later save to keep the existing one.

Once enabled, a first-time sign-in through Google automatically registers a new account — there's nothing separate to set up for registration versus login.

3. Google Calendar for appointment booking (optional)

The same Google app can also let a workspace connect Google Calendar to Appointment Booking, so busy times are hidden and each booking is added to the calendar. In Google Cloud:

  1. Under APIs & Services → Library, enable the Google Calendar API.
  2. Add the redirect address https://yourdomain.com/automations/google/callback to the OAuth client (it is the same one Google Sheets uses).
  3. Under the consent screen's Data access, add the scopes .../auth/calendar.events and .../auth/calendar.freebusy.

Google treats these as sensitive scopes. While the app is in Testing, only the test users you list can connect, and their access lapses after 7 days. For customers to connect freely you must publish the app and pass Google's verification (a privacy policy, a short video of how the scopes are used, and a domain you own). Workspaces that never connect Google Calendar are not affected, and booking works fully without it.

← Mail & Email Templates Payment Gateway →