The flow
Starts it 1Service 9
The steps in the order they run, from what starts it.
- 1Create an activityStrava ToolService
- 2Get an activityStrava ToolService
- 3Get all activity commentsStrava ToolService
- 4Get all activity kudosStrava ToolService
- 5Get all activity lapsStrava ToolService
- 6Get many activitiesStrava ToolService
- 7Get all activity streamsStrava ToolService
- 8Get all activity zonesStrava ToolService
- 9Update an activityStrava ToolService
- 10Strava Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 10
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 10 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.