Short answer: Drop the "Strava → List Strava Activities" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Per Page per_page | number | Optional | Per Page |
After (epoch) after | number | Optional | Return activities after this epoch timestamp |
{"per_page": "{{trigger.per_page}}","after": "{{trigger.after}}"}
[{"id": 12345,"name": "Morning Run","type": "Run","distance": 5000.5,"start_date": "2026-04-11T07:00:00Z","moving_time": 1800,"average_speed": 2.78}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.