Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## How do I set up custom Google OAuth credentials for Google Data Studio? |
| 2 | |
| 3 | Composio doesn't provide a managed OAuth app for Google Data Studio, so you need your own Google OAuth app to connect it. |
| 4 | |
| 5 | You need a Google Workspace or Cloud Identity organization. A Workspace administrator has to authorize your OAuth client for the Data Studio API. |
| 6 | |
| 7 | ### Create the Google OAuth app |
| 8 | |
| 9 | 1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one. |
| 10 | |
| 11 |  |
| 12 | |
| 13 | 2. Open **APIs & Services** → **Library**, search for **Data Studio API** (`datastudio.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. |
| 14 | 3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save. |
| 15 | |
| 16 |  |
| 17 | |
| 18 | 4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with. |
| 19 | |
| 20 |  |
| 21 | |
| 22 | 5. Leave the Data Studio scopes out of **Data Access**. Google's instructions keep them out of the OAuth client's Data Access setup, because your Workspace administrator authorizes them in the Admin console instead (step 9). |
| 23 | 6. Open **Clients** → **Create client**, choose **Web application**, and give it a name. |
| 24 | |
| 25 |  |
| 26 | |
| 27 | 7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config. |
| 28 | |
| 29 |  |
| 30 | |
| 31 | 8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog. |
| 32 | |
| 33 |  |
| 34 | |
| 35 | 9. Have a Workspace administrator open the [Google Admin console](https://admin.google.com/) → **Security** → **Access and data control** → **API controls** → **Manage Domain Wide Delegation**. Under **API clients**, select **Add new**, enter the OAuth client ID, add the Data Studio scopes your app needs, and authorize the client. Follow Google's [Data Studio API instructions](https://developers.google.com/data-studio/integrate/api) for this grant. |
| 36 | |
| 37 | ### Create the auth config in Composio |
| 38 | |
| 39 | 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_data_studio), open **Auth Configs** → **Create** and select **Google Data Studio**. |
| 40 | 2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**. |
| 41 | 3. Open the auth config, select **Connect Account**, and sign in with a Google account in the authorized organization. If Google reports `invalid_scope`, ask the administrator to check the authorized client ID and scope list. |
| 42 | 4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection. |
| 43 | |
| 44 | For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs). |
| 45 | |
| 46 | ### Scopes |
| 47 | |
| 48 | The default auth config requests `https://www.googleapis.com/auth/datastudio`, `openid`, `email`, and `profile`. Composio uses the OpenID scopes to identify the account. If you only search reports and data sources, `https://www.googleapis.com/auth/datastudio.readonly` is enough. Request only scopes your administrator has authorized. |
| 49 | |
| 50 | ### Publish and verify the app |
| 51 | |
| 52 | While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview). |
| 53 | |
| 54 | If you change the requested scopes later, reconnect the account so the user grants the new access. |