Short answer: You can get strava activity in Strava by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Strava Get Strava Activity action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Activity ID activityId | number | Required | Activity ID |
{"activityId": "{{trigger.activityId}}"}
{"id": 12345,"name": "Morning Run","type": "Run","calories": 350,"distance": 5000.5,"moving_time": 1800,"elapsed_time": 2100,"max_heartrate": 175,"average_heartrate": 145,"total_elevation_gain": 50}
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.