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 96 lines 7.57 KB
Rendered Raw
1 ## How do I set up custom Google OAuth credentials for Google Tasks?
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 **Google Tasks API**, 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
13 ![Google Tasks API page in the Google Cloud API Library with the Enable button](/images/toolkits/googletasks/enable-tasks-api.webp)
14
15 ![Google Tasks API details page showing the API is enabled](/images/toolkits/googletasks/tasks-api-enabled.webp)
16
17 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.
18
19 ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20
21 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**.
22
23 ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24
25 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**.
26
27 ![Data Access scope picker with the tasks.readonly scope selected](/images/toolkits/googletasks/data-access-scopes.webp)
28
29 6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30
31 ```
32 https://backend.composio.dev/api/v1/auth-apps/add
33 ```
34
35 It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36
37 ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38
39 ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40
41 7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42
43 ### Create the auth config in Composio
44
45 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googletasks), go to **Auth Configs** → **Create** and select **Google Tasks**.
46 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`.
47 3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 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**.
49
50 ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51
52 ![Google consent screen asking to view tasks](/images/toolkits/googletasks/google-consent-screen.webp)
53
54 For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55
56 ### Scopes
57
58 The default Google Tasks auth config requests `https://www.googleapis.com/auth/tasks`. If your tools only read task lists and tasks, use `tasks.readonly` instead; it can't create, complete, change, or delete tasks. See Google's [Tasks scope reference](https://developers.google.com/workspace/tasks/auth).
59
60 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.
61
62 If you change the scopes later, reconnect the account so the user grants the new access.
63
64 ### Testing, publishing, and verification
65
66 - 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.
67 - To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 - 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).
69 - **Data Access** shows which of your scopes Google treats as sensitive or restricted.
70 - 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.
71
72 ## Why am I seeing "App is blocked" when connecting Google Tasks?
73
74 The OAuth client is requesting scopes that Google hasn't verified for that client. This usually happens when you add extra scopes beyond the defaults.
75
76 Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
77
78 ## Why am I getting "Google Tasks API has not been used in project" error?
79
80 When using custom OAuth credentials, the Google Tasks API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
81
82 ## Why am I getting "Error 400: invalid_scope"?
83
84 The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
85
86 ## Why does the OAuth consent screen show "Composio" instead of my app?
87
88 By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
89
90 ## Why am I getting 401 errors on tool calls?
91
92 The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
93
94 ## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
95
96 Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.