Skip to content

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

docs: fix broken internal links in Google toolkit FAQ files

Sushmithamallesh457f995d1ed7
diff --git a/docs/content/toolkit-faq/gmail.md b/docs/content/toolkit-faq/gmail.md
index 1063a01b0..bf84b4b7d 100644
--- a/docs/content/toolkit-faq/gmail.md
+++ b/docs/content/toolkit-faq/gmail.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Gmail API must be enabled in the Google
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/google_classroom.md b/docs/content/toolkit-faq/google_classroom.md
index 74950da25..62f09ceef 100644
--- a/docs/content/toolkit-faq/google_classroom.md
+++ b/docs/content/toolkit-faq/google_classroom.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Classroom API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/google_maps.md b/docs/content/toolkit-faq/google_maps.md
index acb478cf5..255e3c331 100644
--- a/docs/content/toolkit-faq/google_maps.md
+++ b/docs/content/toolkit-faq/google_maps.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Maps API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googlecalendar.md b/docs/content/toolkit-faq/googlecalendar.md
index 8f4d4b46d..c2d7bb744 100644
--- a/docs/content/toolkit-faq/googlecalendar.md
+++ b/docs/content/toolkit-faq/googlecalendar.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Calendar API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googledocs.md b/docs/content/toolkit-faq/googledocs.md
index 6d82ac722..3fa7d48b4 100644
--- a/docs/content/toolkit-faq/googledocs.md
+++ b/docs/content/toolkit-faq/googledocs.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Docs API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googledrive.md b/docs/content/toolkit-faq/googledrive.md
index 86f3dead9..5e60c970f 100644
--- a/docs/content/toolkit-faq/googledrive.md
+++ b/docs/content/toolkit-faq/googledrive.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Drive API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googlemeet.md b/docs/content/toolkit-faq/googlemeet.md
index 429b6dd11..e2903044e 100644
--- a/docs/content/toolkit-faq/googlemeet.md
+++ b/docs/content/toolkit-faq/googlemeet.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Meet API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googlesheets.md b/docs/content/toolkit-faq/googlesheets.md
index e6a62789f..57887eee0 100644
--- a/docs/content/toolkit-faq/googlesheets.md
+++ b/docs/content/toolkit-faq/googlesheets.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Sheets API must be enabled in th
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googleslides.md b/docs/content/toolkit-faq/googleslides.md
index 44536393d..08b887372 100644
--- a/docs/content/toolkit-faq/googleslides.md
+++ b/docs/content/toolkit-faq/googleslides.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Slides API must be enabled in th
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkit-faq/googlesuper.md b/docs/content/toolkit-faq/googlesuper.md
index 77a0117c2..78a2889fb 100644
--- a/docs/content/toolkit-faq/googlesuper.md
+++ b/docs/content/toolkit-faq/googlesuper.md
@@ -14,10 +14,10 @@ When using custom OAuth credentials, the required Google API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
---
diff --git a/docs/content/toolkit-faq/googletasks.md b/docs/content/toolkit-faq/googletasks.md
index 686230769..7154ff266 100644
--- a/docs/content/toolkit-faq/googletasks.md
+++ b/docs/content/toolkit-faq/googletasks.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Tasks API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-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/programmatic-auth-configs).
+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/auth-configuration/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
+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 the OAuth consent screen](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
## Why am I getting 401 errors on tool calls?