Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 62 lines 5.58 KB
Rendered Raw
1 ## How do I set up custom Google OAuth credentials for Google Photos?
2
3 Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4
5 ### Create the Google OAuth app
6
7 1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8
9 ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10
11 2. Go to **APIs & Services** → **Library**, search for **Photos Library API** (`photoslibrary.googleapis.com`), and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
13
14 ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
15
16 4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
17
18 ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
19
20 5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
21 6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
22
23 ```
24 https://backend.composio.dev/api/v1/auth-apps/add
25 ```
26
27 It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
28
29 ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
30
31 ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
32
33 7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
34
35 ### Create the auth config in Composio
36
37 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlephotos), go to **Auth Configs** → **Create** and select **Google Photos**.
38 2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
39 3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
40 4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
41
42 ![Google consent screen asking to manage photos added by the app](/images/toolkits/googlephotos/google-consent-screen.webp)
43
44 ![Google Photos auth config details with an Active connected account](/images/toolkits/googlephotos/composio-connected-account-active.webp)
45
46 For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
47
48 ### Scopes
49
50 The default Google Photos auth config requests `https://www.googleapis.com/auth/photoslibrary.readonly.appcreateddata` and `https://www.googleapis.com/auth/photoslibrary.edit.appcreateddata`. Google removed the library-wide read and sharing scopes in March 2025, so the Library API only sees albums and media your app created. A new OAuth app returns an empty album list until it creates content. To let users pick items from their whole library, Google offers the separate Photos Picker API. See Google's [Photos scope reference](https://developers.google.com/photos/overview/authorization) and [API changes](https://developers.google.com/photos/support/updates).
51
52 Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
53
54 If you change the scopes later, reconnect the account so the user grants the new access.
55
56 ### Testing, publishing, and verification
57
58 - While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
59 - To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
60 - Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
61 - **Data Access** shows which of your scopes Google treats as sensitive or restricted.
62 - If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.