How to Connect Multiple Accounts to Zapier Using Private Browser Windows

A practical field guide from Automation Ace.

How to Connect Multiple Accounts to Zapier Using Private Browser Windows

One of the most practically useful Zapier tips is also one of the least documented: when you need to connect a second (or third) account of the same app to Zapier — a client's Google account, a company Gmail alongside your personal Gmail, a second HubSpot portal — the reliable way to do it without authentication conflicts is to use a private or incognito browser window. This tip applies every time you are connecting an OAuth-based app and you need the connection to authenticate against a specific account rather than whichever account is currently signed in to that app in your main browser session.

The problem private windows solve: OAuth works by redirecting you to the app's own login page in a popup or redirect. If you are already signed in to that app in your browser, the OAuth flow may skip the login screen and immediately authenticate as the currently signed-in account. If that is not the account you intended to connect, you end up with a connection to the wrong account — and it is not always immediately obvious that this happened.

The Step-by-Step Method

1. Open a private browsing window. In Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac). In Firefox: Ctrl+Shift+P. In Safari: Cmd+Shift+N. The exact shortcut varies by browser, but every modern browser supports a private mode.
2. In the private window, navigate to the app you want to connect (for example, accounts.google.com for a Google account, or app.hubspot.com for HubSpot).
3. Sign in to the specific account you want to connect to Zapier. Verify you are signed in to the correct account — check the account name or email displayed in the app's header.
4. Now, while still in the private window, navigate to Zapier (zapier.com) and sign in to your Zapier account.
5. Open the Zap or go to My Apps and connect the app. When the OAuth popup or redirect fires, it will authenticate against the account you signed in to in the private window.

Why This Works

Private browser windows have isolated session storage from your main browser session. Cookies, session tokens, and saved login states are not shared between private windows and your main browser. When an OAuth redirect fires in the private window, the only account session available is the one you signed in to explicitly in that private window — not your personal account from your main browser. The authentication flow correctly picks up the intended account.

This technique is particularly useful for consultants who manage Zapier accounts for multiple clients. You may need to connect a client's Gmail, Slack, HubSpot, and Airtable accounts to their Zapier account — all of which require you to authenticate as the client rather than yourself. Using a private window for each OAuth connection ensures you connect the right account every time. For more on the broader topic of app authentication in Zapier, see how to connect apps to Zapier. For a deeper look at the authentication patterns behind these connections — OAuth, API keys, bearer tokens — see the guide on API authentication for automation.

This private window trick is the fastest fix for the confusion of "I connected Google but it connected the wrong Google account." Sign in to the right account in a private window first, then connect from Zapier in that same window. Problem solved.

When Private Windows Are Not Enough

For scenarios where you need to manage many client accounts simultaneously, consider browser profiles (Chrome profiles, Firefox containers) rather than private windows. Browser profiles maintain persistent sessions per profile, so you can have "Client A profile" and "Client B profile" each with their own authenticated app sessions without needing to sign in and out every time. This is the setup many automation consultants use for managing multiple client Zapier environments efficiently. If you need help setting up a multi-client Zapier management workflow, reach out to Automation Ace.