How to Set Up Google Client ID and Secret for Gmail

Why you need Google OAuth credentials

To connect Gmail accounts in EmaReach using Google sign-in (OAuth) instead of app passwords, you need to create your own Google Cloud OAuth client and add the Client ID and Client Secret in EmaReach. This lets you authorize Gmail in the browser without storing your Gmail password. Your plan must allow Gmail (e.g. Premium); if the app does not have a default OAuth client, you must add your own credentials in Settings → Integrations → Gmail.

Step 1: Get Client ID and Secret from Google Cloud Console

1. Go to Google Cloud Console.
2. Create a project or select an existing one (top bar).
3. Open APIs & Services → Credentials (left menu, or use the search).
4. Click + Create Credentials → OAuth client ID.
5. If prompted, configure the OAuth consent screen first: choose External (or Internal for Google Workspace), add app name (e.g. EmaReach), support email, and save.
6. Back in Create OAuth client ID:
   • Application type: choose Web application.
   • Name: e.g. "EmaReach Gmail".
   • Under Authorized redirect URIs, click Add URI. Do not type the URL manually—get it from the dashboard: in EmaReach go to Settings → Integrations → Gmail, open the form to add Google credentials, and copy the Authorized redirect URI shown there. Paste that URI into Google Cloud.
   • Save. Google will show the Client ID (looks like xxxxx.apps.googleusercontent.com) and Client Secret (looks like GOCSPX-xxxxx). Copy both; the secret is shown only once (you can regenerate it later if needed).

Step 2: Add the redirect URI (critical)

In your OAuth client, under Authorized redirect URIs, you must add the URI exactly as shown in the dashboard. In EmaReach go to Settings → Integrations → Gmail, open the form where you enter your Google Client ID and Secret—the page shows the Authorized redirect URI you need. Copy it from there and paste it into Google Cloud; do not type it from documentation or guess. Google will reject sign-in if the redirect URI does not match exactly.

Step 3: Save credentials in EmaReach

1. In EmaReach, go to Settings → Integrations (or Settings and open the Integrations tab).
2. Find the Gmail section.
3. If you see Add your Google OAuth credentials or Google Client ID / Google Client Secret, click to expand or open the form.
4. Enter:
   • Google Client ID: paste the Client ID (e.g. xxxxx.apps.googleusercontent.com).
   • Google Client Secret: paste the Client Secret (e.g. GOCSPX-xxxxx).
5. Click Save. The app stores the secret securely and never returns it in the UI.
6. After saving, you can Connect Gmail with Google (OAuth): click Connect with Google and complete the browser flow; your Gmail account will be added as an inbox.

Summary checklist

• Google Cloud Console → APIs & Services → Credentials.
• Create OAuth client ID (Web application).
• Add Authorized redirect URI: copy from dashboard (Settings → Integrations → Gmail, when adding credentials)
• Copy Client ID and Client Secret.
• Settings → Integrations → Gmail: paste Client ID and Secret, Save.
• Connect Gmail with Google (OAuth) from the same Integrations section.

Troubleshooting

• "Google OAuth credentials not set" — Add your Client ID and Secret in Settings → Integrations → Gmail and save.
• Redirect URI mismatch — Ensure the redirect URI in Google Cloud matches exactly the one shown in the dashboard (copy from Settings → Integrations → Gmail when adding credentials).
• App not verified — For External consent, unverified apps show a warning; you can still choose "Advanced" → "Go to EmaReach (unsafe)" to continue during testing. For production, consider submitting the app for verification.
• Secret not shown again — If you lose the secret, create a new one in Google Cloud (Credentials → your OAuth client → reset secret) and update it in EmaReach.