- Pass full OAuth callback URL through auth-server for openid-client validation - Composio + Google flows: duplicate-callback guard; preserve timeout cleanup - Persist and expose Google clientId via oauth:getState; hydrate UI from useConnectors - getAccessToken returns refreshed credentials; clearer errors and missing-state handling - IPC schema: per-provider userId + clientId - Docs: google-setup redirect URI and troubleshooting Made-with: Cursor
4.2 KiB
Connecting Google to Rowboat
Rowboat requires a Google OAuth Client ID to connect to Gmail, Calendar, and Drive. Follow the steps below to generate your Client ID correctly.
1️⃣ Open Google Cloud Console
Go to:
https://console.cloud.google.com/
Make sure you're logged into the Google account you want to use.
2️⃣ Create a New Project
Go to:
https://console.cloud.google.com/projectcreate
- Click Create Project
- Give it a name (e.g.
Rowboat Integration) - Click Create
Once created, make sure the new project is selected in the top project dropdown.
3️⃣ Enable Required APIs
Enable the following APIs for your project:
-
Gmail API
https://console.cloud.google.com/apis/api/gmail.googleapis.com
-
Google Calendar API
https://console.cloud.google.com/apis/api/calendar-json.googleapis.com
-
Google Drive API
https://console.cloud.google.com/apis/api/drive.googleapis.com
For each API:
4️⃣ Configure OAuth Consent Screen
Go to:
https://console.cloud.google.com/auth/branding
App Information
- App name: (e.g.
Rowboat) - User support email: Your email
Audience
- Choose External
Contact Information
- Add your email address
Click Save and Continue through the remaining steps.
You do NOT need to publish the app — keeping it in Testing mode is fine.
5️⃣ Add Test Users
If your app is in Testing mode, you must add users manually.
Go to:
https://console.cloud.google.com/auth/audience
Under Test Users:
- Click Add Users
- Add the email address you plan to connect with Rowboat
Save changes.
6️⃣ Create OAuth Client ID
Go to:
https://console.cloud.google.com/auth/clients
Click Create Credentials → OAuth Client ID
Application Type
Select:
Universal Windows Platform (UWP)
- Name it anything (e.g.
Rowboat Desktop) - Store ID can be anything (e.g.
test) - Click Create
Authorized redirect URIs (if shown)
If your OAuth client configuration shows Authorized redirect URIs, add:
http://localhost:8080/oauth/callback
Use this exactly: no trailing slash, port 8080. This must match what the app uses for the OAuth callback. (Some client types, e.g. UWP, may not expose redirect URIs; that is fine.)
7️⃣ Copy the Client ID
After creation, Google will show:
- Client ID
- Client Secret
Copy the Client ID and paste it into Rowboat where prompted.
Troubleshooting
Error after "Authorization Successful"
If the browser shows "Authorization Successful" but the app then shows an error (e.g. "invalid response encountered" or "response parameter "iss" (issuer) missing"):
- Check the app logs (e.g. terminal or dev tools) for the full error. The message there will often indicate the cause (e.g. redirect URI mismatch, missing parameter).
- Verify redirect URI in Google Cloud Console: Open Credentials → your OAuth 2.0 Client ID. If the client type allows Authorized redirect URIs, ensure
http://localhost:8080/oauth/callbackis listed exactly. - Client type: Use Desktop or UWP as the application type. A "Web application" client may require the redirect URI to be set and can behave differently with localhost.





