Resources · Make integration

Strava Make integrationAutomate Strava with Make.

One activity in Strava can set a whole scenario running. In Make, a scenario is the automation you build by chaining modules, the bricks that each do one job. The Strava Make integration brings seven: one starts the scenario, five act, one searches.

Try the Strava integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Strava Make integration let you automate?

You link your Strava account to Make one time. That link is what Make calls a connection, and every Strava module reuses it. From there, Make can react to what an athlete just did and act back on Strava on its own. The seven modules cover activities and your own figures: catching a new one, reading it, listing what you already logged, writing one, editing one, and pulling a stats report.

Three shapes come back often. The first is a logbook that keeps itself: Watch Activities and Athletes catches each new activity as it lands, and List Activities fills in everything logged before. The second is titles you stop fixing by hand, with Update an Activity renaming a session the second it shows up. The third is a recap nobody assembles, where Get a Stats Report returns recent, year to date and all time figures for the account behind the connection.

What Make will not do here is invent what Strava does not expose. The seven modules deal with activities and one stats report, so anything else goes through Make an API Call, which reaches the rest of the Strava API, the technical door apps use to talk to each other, on the same connection. Worth knowing too: Make says its own Strava documentation is generated and can contain mistakes, so check anything that matters against Strava before you build on it.

Strava also has an n8n node, and the same automation can live there instead. If you are still choosing, the n8n vs Make comparison lays out the criteria, and the Strava n8n integration page covers the other side. If you would rather learn the editor properly before building anything, Make training takes it in order.

Connect

How do you connect Strava to Make?

  1. 01

    Create your Strava API app

    Strava needs a developer app before Make can talk to it. In your Strava account, open Settings, click API, then Create App. Put https://www.integromat.com/oauth/cb/strava in the callback URI, then copy the Client ID and the Client secret.

  2. 02

    Open the connection window

    Back in Make, drop any Strava module into a scenario and click Create a connection. The Connection name field is optional, but filling it in pays off the day you handle two athletes' accounts from the same place.

  3. 03

    Paste the two keys

    Enter the client ID and client secret you copied from Strava, or follow the instructions Make shows in the window. Once it goes through, the connection is stored and every Strava module you add later picks it up without asking again.

First scenario

Your first scenario, start to finish

GoalWhen an activity lands in Strava, Make renames it on the spot.

  1. 01

    Start a blank scenario

    From the Scenarios page in Make, create a new scenario and click the + to add the first module. Type Strava in the search box and the app's modules show up.

  2. 02

    Drop in the trigger

    Pick Watch Activities and Athletes, the module that starts everything. It carries the instant tag, so Make asks for a webhook and then for your connection. Once both are set, it sits at the head of the chain with a lightning badge.

  3. 03

    Add the action behind it

    Click the + on the right of the trigger and choose Update an Activity. Rather than typing an ID, point it at the activity the trigger just handed over, the bundle that travels from one module to the next.

  4. 04

    Test with Run once

    Click Run once, then record or edit something in Strava. Make executes the scenario a single time and shows what each module received, which is where a wrong mapping becomes obvious.

  5. 05

    Switch it on

    Turn the scenario on and it stays on watch by itself. Each module that runs on an item counts one operation against your plan, so the bill follows how much you actually ride.

Triggers

What sets a Strava scenario off?

1 module starts a scenario when something happens in Strava. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Strava as soon as it happens.

Strava1Watch Activities and Athletes

Watch Activities and Athletes

Instant trigger

In Make“Triggers when an activity or an athlete is added, updated, or deleted.”

Watch Activities and Athletes is the starting block of almost anything you build here. It reacts when an activity or an athlete record is added, changed or removed, and hands the rest of the scenario whatever just moved.

How it fires
instantly. Strava calls Make through a webhook the moment it happens, which is why the module wears a lightning badge instead of a clock.
When to use it
anything that has to answer an athlete while the session is still fresh, like tagging a ride or feeding a shared log.
Watch out
one module covers three events on two kinds of object, so read what arrived before the next module acts on it.
Modules

What Strava can do once the scenario runs

Strava gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Strava1

Create an Activity

Action

In Make“Creates a new activity.”

Create an Activity writes a session into Strava from data the scenario already carries, so something tracked elsewhere ends up on the athlete's profile.

When to use it
a treadmill hour kept in a spreadsheet, or a club event you want on every member's feed.
Watch out
it adds, it never checks. Run the scenario twice and you get the session twice, which is what Run once is for.
Strava2

Get an Activity

Action

In Make“Retrieves details of an activity by its ID.”

Give Get an Activity an ID and it returns the full record of that one session, ready for the modules that follow.

When to use it
the trigger tells you something changed and you want the detail before deciding what to do with it.
Watch out
one ID, one activity. To work through a batch, start from List Activities instead.
Strava3

Get a Stats Report

Action

In Make“Retrieves your recent, year to date and all activity stats.”

Recent totals, the year to date and the all time figures come back together with Get a Stats Report, for the account behind the connection.

When to use it
a recap you send out, a progress line in a newsletter, a number on a dashboard someone actually reads.
Watch out
it answers for the connected athlete, not for a club or a list of friends.
Strava4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the escape hatch: it sends a request you write yourself to the Strava API, on the connection you already set up.

When to use it
what you need has no module of its own and you would otherwise drop the idea.
Watch out
you build the call by hand, so this is the one module that sends you to Strava's API reference first.
Strava5

Update an Activity

Action

In Make“Updates an activity by its ID.”

Same ID, different purpose: Update an Activity rewrites a session that already exists, so the version on Strava matches what your scenario decided.

When to use it
a naming rule applied across a team, or a correction that comes from another tool.
Watch out
the new value replaces the old one and Make keeps no copy, so try the mapping on a test activity before it runs on everyone's.
Strava6

List Activities

Search

In Make“Lists your activities.”

List Activities is a search: it comes back with the sessions of the connected account as separate bundles, one per activity, and the modules behind it run on each in turn.

When to use it
filling a history, rebuilding a table, or checking what exists before you create anything.
Watch out
a search can return nothing, one item or a long list, and each item spends operations further down the chain.
Need help

Need help automating Strava with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Strava Make integration free?
Yes, on the Free plan. Strava is a standard app in Make, not an Enterprise one, so it works from the moment you sign up. The Free plan runs two active scenarios at a time, stops a run after five minutes, and comes with 512 MB of transfer. Paid plans lift that ceiling: active scenarios become unlimited, execution goes up to 40 minutes, and usage is counted in credits, one per operation, each month. Strava's own subscription is a separate matter and has nothing to do with Make.
02What do you need before connecting Strava to Make?
An active Strava account and a developer app created on it. Strava does not hand Make a ready-made key, so you open Settings, then API, then Create App, set the callback URI Make expects, and copy the client ID and client secret that appear. Those two values are what the connection window asks for. If the first module you add is the instant trigger, Make asks you to create the webhook before the connection, in that order. Nothing else is required on the Make side.
03Does the Strava trigger react in real time?
Yes. Watch Activities and Athletes is an instant trigger, which means Strava calls Make through a webhook as soon as an activity or an athlete record is added, changed or deleted. Make is not checking Strava on a clock, it waits to be told. In practice you record a session, the scenario wakes up, and the modules behind the trigger run on what arrived. It is the only trigger Strava offers in Make, so every reactive scenario you build starts there.
04What if a Strava module is missing in Make?
Use Make an API Call. It sits in the same list as the other modules and sends any request you write to the Strava API, using the connection already in place, so the corners of Strava without a module of their own stay reachable. The trade-off is that you build the call yourself, with Strava's API reference open next to you. One more thing worth knowing: Make says its Strava documentation is generated and can contain mistakes, so verify anything critical with Strava.
05Make or n8n for Strava?
It depends on what you are optimizing for. Make draws the scenario as a chain of round modules and reads faster while you are learning, and Strava sits there as a standard app with seven modules and an instant trigger. n8n shows more of the plumbing and suits people comfortable writing a bit of code. Both cover Strava. If what you are building is a small reactive loop around activities, the real question is which editor you will actually open again.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations