Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 12:15 UTC
docs: remove Strava toolkit FAQ and KB content
Strava is no longer in the toolkit catalog (public/data/toolkits*.json has no strava entry), so drop its orphaned FAQ page, KB guide, and KB source/manifest/registry entries. kb/semantic-index.json will go stale from the manifest change; it regenerates via the existing "Docs - Rebuild KB Semantic Artifact" workflow (or `bun run build:kb-semantic`).
composio-zen[bot] committed
Sep 17, 2026 at 15:27 UTC
ca2e4df0ed220bfb7b3aaf3fe74ad11fb27d108f
7 files changed
-110
docs/content/kb/guide/meta.json
-1
@@ -109,7 +109,6 @@
109
"toolkits-snapchat",
110
"toolkits-snowflake",
111
"toolkits-spotify",
112
- "toolkits-strava",
112
"toolkits-stripe",
113
"toolkits-supabase",
114
"toolkits-tavily",
docs/content/kb/guide/toolkits-strava.mdx
deleted
-19
@@ -1,19 +0,0 @@
1
----
2
-title: "Strava"
3
-description: "Public authentication and provider-capacity guidance for Strava."
4
-keywords: ["for-you","oauth","platform","strava","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/strava-athlete-limits-belong-to-the-oauth-app","strava-athlete-limits-belong-to-the-oauth-app"]
5
-sources: [{"sourcePath":"toolkits/strava/public.md","sourceHeading":"Athlete-limit errors belong to the OAuth application"}]
6
-lastVerifiedAt: "2026-08-12"
7
-reviewAfter: "2026-11-10"
8
-freshness: "evergreen"
9
-topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10
-toolkitSlugs: ["strava"]
11
-aliases: ["/kb/toolkits/strava-athlete-limits-belong-to-the-oauth-app","strava-athlete-limits-belong-to-the-oauth-app"]
12
----
13
-## Athlete-limit errors belong to the OAuth application
14
-
15
-Strava applies connected-athlete capacity per developer application. If OAuth shows `Athlete limit exceeded`, first determine whether the auth config uses Composio-managed Strava credentials or a customer-owned app; do not assume the customer owns a managed app.
16
-
17
-For dedicated production capacity, create a customer-owned Strava developer app, configure it as a custom Composio auth config, and request any capacity increase from Strava for that app. The exact current capacity is visible to the app owner in Strava's API settings and can change, so do not quote a customer-specific number without checking it.
18
-
19
-See the [Strava custom OAuth setup guide](https://composio.dev/auth/strava) for credential setup.
docs/content/toolkits/faq/strava.md
deleted
-19
@@ -1,19 +0,0 @@
1
-## How do I set up custom OAuth credentials for Strava?
2
-
3
-For a step-by-step guide on creating and configuring your own Strava OAuth credentials with Composio, see [How to create OAuth credentials for Strava](https://composio.dev/auth/strava).
4
-
5
-## Why can Strava OAuth fail with "Athlete limit exceeded" or `Application.Status.Inactive`?
6
-
7
-Strava can reject authorization or tool execution when the Strava OAuth app behind the connection has not been fully approved/activated by Strava or has hit its athlete limit.
8
-
9
-If you are using managed Strava OAuth, you may see either "Athlete limit exceeded" during authorization or a 403 response from Strava with `Application.Status.Inactive` during tool execution.
10
-
11
-We are working with Strava on approval and capacity for the managed Strava app. Since this depends on Strava's approval process, we do not have a concrete date to share yet.
12
-
13
-For production use or dedicated capacity, use your own Strava OAuth app with a custom auth config, then reconnect users through that config.
14
-
15
-## Why are private Strava activities missing?
16
-
17
-The managed Strava OAuth scope set currently includes `read`, `activity:read`, and `profile:read_all`.
18
-
19
-`activity:read` can read activities visible to the authenticated athlete based on Strava visibility rules, but private activities require `activity:read_all`. If private activities are missing, use your own Strava OAuth app with `activity:read_all` configured, then reconnect the account so the new scope is granted.
docs/kb/articles/toolkits-strava.md
deleted
-7
@@ -1,7 +0,0 @@
1
-## Athlete-limit errors belong to the OAuth application
2
-
3
-Strava applies connected-athlete capacity per developer application. If OAuth shows `Athlete limit exceeded`, first determine whether the auth config uses Composio-managed Strava credentials or a customer-owned app; do not assume the customer owns a managed app.
4
-
5
-For dedicated production capacity, create a customer-owned Strava developer app, configure it as a custom Composio auth config, and request any capacity increase from Strava for that app. The exact current capacity is visible to the app owner in Strava's API settings and can change, so do not quote a customer-specific number without checking it.
6
-
7
-See the [Strava custom OAuth setup guide](https://composio.dev/auth/strava) for credential setup.
docs/kb/external-sources/auth-guides.json
-7
@@ -153,13 +153,6 @@
153
"title": "How to create OAuth2 and API key credentials for Stripe",
154
"description": "Create Stripe OAuth2 or API key credentials and configure them in Composio."
155
},
156
- {
157
- "slug": "strava",
158
- "toolkitSlug": "strava",
159
- "canonicalUrl": "https://composio.dev/auth/strava",
160
- "title": "How to create OAuth2 credentials for Strava",
161
- "description": "Create a Strava OAuth2 application and configure it in Composio."
162
- },
156
{
157
"slug": "snowflake",
158
"toolkitSlug": "snowflake",
docs/kb/manifest.json
-37
@@ -5773,43 +5773,6 @@
5773
"state": "published",
5774
"featured": false
5775
},
5776
- {
5777
- "slug": "toolkits-strava",
5778
- "title": "Strava",
5779
- "description": "Public authentication and provider-capacity guidance for Strava.",
5780
- "articlePath": "toolkits-strava.md",
5781
- "sources": [
5782
- {
5783
- "sourcePath": "toolkits/strava/public.md",
5784
- "sourceHeading": "Athlete-limit errors belong to the OAuth application"
5785
- }
5786
- ],
5787
- "topics": [
5788
- "auth-config",
5789
- "authentication",
5790
- "errors-and-troubleshooting",
5791
- "sessions-and-execution",
5792
- "toolkits-and-providers"
5793
- ],
5794
- "tags": [
5795
- "for-you",
5796
- "oauth",
5797
- "platform",
5798
- "strava"
5799
- ],
5800
- "aliases": [
5801
- "/kb/toolkits/strava-athlete-limits-belong-to-the-oauth-app",
5802
- "strava-athlete-limits-belong-to-the-oauth-app"
5803
- ],
5804
- "relatedGuides": [],
5805
- "externalResources": [],
5806
- "updatedAt": "2026-07-16",
5807
- "lastVerifiedAt": "2026-08-12",
5808
- "reviewAfter": "2026-11-10",
5809
- "freshness": "evergreen",
5810
- "state": "published",
5811
- "featured": false
5812
- },
5776
{
5777
"slug": "toolkits-stripe",
5778
"title": "Stripe",
docs/kb/source/toolkits/strava/public.md
deleted
-20
@@ -1,20 +0,0 @@
1
----
2
-type: "troubleshooting"
3
-title: "Strava"
4
-description: "Public authentication and provider-capacity guidance for Strava."
5
-category: "auth-config"
6
-visibility: "public"
7
-timestamp: "2026-07-16T00:00:00Z"
8
-tags:
9
- - "strava"
10
- - "oauth"
11
----
12
-# Strava
13
-
14
-## Athlete-limit errors belong to the OAuth application
15
-
16
-Strava applies connected-athlete capacity per developer application. If OAuth shows `Athlete limit exceeded`, first determine whether the auth config uses Composio-managed Strava credentials or a customer-owned app; do not assume the customer owns a managed app.
17
-
18
-For dedicated production capacity, create a customer-owned Strava developer app, configure it as a custom Composio auth config, and request any capacity increase from Strava for that app. The exact current capacity is visible to the app owner in Strava's API settings and can change, so do not quote a customer-specific number without checking it.
19
-
20
-See the [Strava custom OAuth setup guide](https://composio.dev/auth/strava) for credential setup.