## TL;DR

The thread was from October 2025 and marked as a resolved question. What actually fixes it (verified in the thread): The user_id you pass is just your own app identifier, not the Google account, so you have to look it up yourself.

## Steps

1. I was connecting Google accounts in my app with composio.connected_accounts.initiate and ran into a weird problem. The redirect_url lets the user pick a different Google account than the user_id I passed in, so the connected account came back with only my own user_id on it and no hint about which Google account it actually pointed at. With multiple connected Gmail accounts there was no way to tell them apart programmatically when authorizing a tool. The thread was from October 2025 and marked as a resolved question.

2. What actually fixes it (verified in the thread):

3. The user_id you pass is just your own app identifier, not the Google account, so you have to look it up yourself. On the callback_url you set in initiate, you get the new connectedAccountId, and for Gmail you can call the GMAIL_GET_PROFILE tool (or proxy the toolkit's get_current_user endpoint) with that id to get the actual email address. One gotcha: in the Python SDK the parameter is snake_case, connected_account_id, not camelCase, which cost the reporter an auth error. For Calendar or Drive there wasnt an equivalent profile tool at the time, but Composio said they were standardizing connected account names for that.

## When to use

You are seeing this: The situation: I was connecting Google accounts in my app with composio.connected_accounts.initiate and ran into a weird problem. Use this skill when you run into "How to tell which Google account a Composio connected account belongs to (multiple accounts)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.