OtherReal-timeUpdated May 2026

Strava

Strava athlete activities and workouts

Strava is the social fitness platform for runners, cyclists, hikers, and swimmers, and Tiny Command surfaces three triggers covering the activity lifecycle: Activity Created (a new workout was uploaded — from the Strava app, a Garmin/Wahoo sync, or a manual entry), Activity Updated (the athlete edited the activity — name, description, type, privacy), Activity Deleted (removed by the athlete). Three actions cover reads: Get Activity (full detail including the per-second stream of GPS, heart rate, cadence, power if the device captured it), List Activities (paginated history), and Get Athlete Profile. The connection uses Strava OAuth at activity:read_all scope. Activity Created is the workflow trigger for fitness-data downstream: pipe new workouts to a Notion training log, push summary stats to a Slack training-buddies channel, sync to a Google Sheet for weekly mileage rollup, or run an AI summary that generates a one-line workout narrative. Strava's webhook delivery is typically under 60 seconds from upload.

Connect Strava See 3 triggers

3triggers

3actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Strava does.

3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When strava activity created

Fires when a new activity is uploaded — from the Strava app, Garmin/Wahoo sync, or manual entry. For "new workout → log to Notion training log, push stats to Slack" personal-automation.

See what it returns →

Trigger live

When strava activity deleted

Fires when an athlete deletes a workout. For sync workflows that need to remove the corresponding record from external systems.

See what it returns →

Trigger live

When strava activity updated

Fires when the athlete edits an activity (rename, type change, privacy). The payload includes updates dict with changed fields for selective downstream reactions.

See what it returns →

Actions

Do anything Strava can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Strava Activity	Returns the activity with GPS polyline, per-second streams (HR, cadence, power, altitude), segment efforts. For detailed analysis workflows after a webhook lands.	1 fields	View →
Get Strava Athlete	Returns the connected athlete's profile — name, location, weight, FTP, follower count. Useful for personalisation workflows.	0 fields	View →
List Strava Activities	Paginated activities with date filters. For "weekly training summary" or "monthly mileage rollup" personal-fitness workflows.	2 fields	View →

Recipes

Pre-built Strava workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Strava → Slack alerts

AI-triage every Strava event, ping the right channel only when it matters.

Strava → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Strava → Notion database

Turn Strava into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Strava once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Strava field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Strava integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Strava to Tiny Command?

Open the Tiny Command workflow builder, drop in a Strava node, and click Connect. Authorize Strava once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Strava triggers does Tiny Command support?

Tiny Command supports 3 real-time Strava triggers, including "Strava Activity Created", "Strava Activity Deleted", "Strava Activity Updated". Each trigger fires within seconds of the event happening in Strava.

What Strava actions can I run from a workflow?

3 Strava actions are available out of the box, covering other operations like "Get Strava Activity". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Strava integration real-time?

Yes. Strava Activity Created and every other Strava trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Strava rather than on a polling schedule.

Do I need to write code to use Strava with Tiny Command?

No. Every Strava trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Strava API endpoint directly.

How much does the Strava integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Strava integration itself has no per-app surcharge.