This is a n8n community node. It lets you use Strava in your n8n workflows.

Strava is the activity platform used by athletes to track running, cycling, swimming, routes, segments, clubs,
uploads, and performance streams. This node exposes the official Strava API v3 operations, Strava webhook triggers, and
a separate opt-in web-session resource for a few undocumented browser-only actions.

n8n is a fair-code licensed workflow automation platform.

• Installation
• Operations
• Official n8n Strava vs this package
• Credentials
• Compatibility
• Usage
• Web session notes
• Resources

Installation

Follow the installation guide in the n8n community nodes documentation.

1. Go to Settings > Community Nodes.
2. Select Install.
3. Enter n8n-nodes-strava in Enter npm package name.
4. Agree to the risks of using community nodes: select I
   understand the risks of installing unverified code from a public source.
5. Select Install.

After installing the node, you can use it like any other node. n8n displays Strava and Strava Trigger in search
results in the Nodes panel.

For local development:

npm install
npm run build
npm run dev

Official n8n Strava vs. this package

The official n8n Strava node is a good starting point for simple activity workflows. This package is built for people
who want to go much further: more Strava API coverage, cleaner advanced workflows, route exports, uploads from binary
data, streams, and guarded web-session actions that the official node does not expose.

As of the n8n documentation checked on 2026-04-26, the official Strava action node documents only the Activity
resource operations: create, get, get all, comments, kudos, laps, zones, and update. The official Strava Trigger
supports activity and athlete events. This package keeps those core workflows, then adds the missing power-user surface.

In practice, this package removes the need to keep dropping down into the generic HTTP Request node for normal Strava
automation. If your workflow is only "create or read activities", the official node is fine. If your workflow touches
routes, streams, clubs, segments, uploads, exports, athlete stats, or browser-session-only social actions, this package
is the stronger tool.

Official reference pages:

• Official n8n Strava node documentation
• Official n8n Strava Trigger documentation
• Official n8n Strava credentials documentation

Operations

This package includes two nodes:

• Strava: regular actions against Strava API v3 and selected web-session routes.
• Strava Trigger: starts workflows from Strava push subscription events.

Official Strava API resources

Implemented Strava operation IDs

Web session operations

These operations are intentionally separated under Web Session (Undocumented) because they use Strava browser
routes, not the official API.

Trigger events

The Strava Trigger node supports Strava push subscriptions for:

• Objects: Activity, Athlete, or All
• Events: Created, Updated, Deleted, or All
• Optional data resolution for activity events
• Optional cleanup of an existing Strava push subscription when Strava reports that one already exists

Credentials

This node supports two credential types.

1. Strava OAuth2 API

Use this credential for all official Strava API v3 resources and for the Strava Trigger node.

To set it up:

• Create an API application in the Strava API settings.
• Copy the client ID and client secret into the n8n OAuth2 credential.
• Use the OAuth callback URL shown by n8n in your Strava application settings.
• Authorize the scopes required by your workflows.

Configured scopes:

read,read_all,profile:read_all,profile:write,activity:read,activity:read_all,activity:write

The OAuth2 credential uses n8n's built-in OAuth2 handling, including token storage and refresh behavior.

2. Strava Web Session API

Use this credential only for Web Session (Undocumented) operations.

Required values:

• Strava Session Cookie: the full Cookie header copied from an authenticated browser request to www.strava.com.
• CSRF Token: the token from the same browser session. Strava expects it in the X-CSRF-Token header for writing
  requests.
• User-Agent: ideally the same browser user agent used when copying the cookie.
• Accept-Language: optional, but keeping it close to the browser request helps reproduce the same session behavior.

Important: the cookie grants access to your Strava account. Store it as a secret, rotate it often, and never paste it
into logs, issues, screenshots, or shared workflows.

Compatibility

• n8n package format: community node API version 1 with strict mode enabled.
• Node.js: >=20.19.0
• n8n workflow peer dependency: ^2.15.1
• Tested locally with: npm run typecheck, npm run lint, npm run build, and npm run pack:dry

Known compatibility notes:

• Strava allows only one push subscription per application. If trigger registration fails because a subscription already
  exists, enable the cleanup option only when you intentionally want to replace the existing subscription.
• Some Strava endpoints require specific OAuth scopes. A valid OAuth connection can still receive 403 Forbidden if the
  authorized scopes are too narrow.
• Web-session operations depend on undocumented Strava browser routes and may change or stop working without notice.

Usage

Common official API workflows

• Sync recent activities into a database or spreadsheet.
• Fetch detailed activity, lap, zone, comment, and kudo data.
• Export routes as GPX or TCX for downstream processing.
• Upload GPX, TCX, FIT, and compressed activity files from n8n binary data.
• Listen for Strava activity updates with Strava Trigger and enrich the event with activity details.

Binary upload

For upload workflows:

1. Add a node that produces binary data, such as Read/Write Files from Disk, HTTP Request, or an incoming
   webhook.
2. In Strava > Upload > Create Upload, select the binary property that contains the activity file.
3. Choose the matching data type: gpx, gpx.gz, tcx, tcx.gz, fit, or fit.gz.

Route exports

GPX and TCX exports can be returned as:

• n8n binary data, ready to write to disk or upload elsewhere.
• Raw XML text, useful for debugging or transformations.

Streams

Stream keys are sent in the CSV format expected by Strava. Select the stream keys in the node UI, and the node handles
the required request formatting.

Web session notes

The Web Session (Undocumented) resource exists for Strava actions that are not available in the official API. It is
intentionally more guarded than regular API operations.

Before using write operations:

1. Log in to Strava in a browser.
2. Open DevTools > Network.
3. Copy the full Cookie header from a request to https://www.strava.com.
4. Copy the CSRF token from either the X-CSRF-Token request header or the page source meta-tag named csrf-token.
5. Put both values in the Strava Web Session API credential.
6. Run Web Session (Undocumented) > Test Session.

For write operations:

• The CSRF token is sent as X-CSRF-Token.
• Origin and Referer headers are sent to match browser-style requests.
• Follow, unfollow, and kudo operations require explicit confirmation fields in the node UI.
• Bulk web write actions are guarded to reduce accidental account changes.

If Strava returns 403 Forbidden, refresh the session cookie and CSRF token from the same browser session. A cookie can
be valid enough to load some pages while still being rejected for protected write routes.

Resources

• n8n community nodes documentation
• n8n community nodes risks
• Strava API documentation
• Strava authentication documentation
• Strava webhooks documentation
• Strava upload documentation