Strava Activity Management: Create, Update, and Retrieve Data - n8n Workflow

• Strava users or developers looking to automate fitness tracking data.
• Users seeking a robust example of sequential API calls within an n8n workflow.
• Anyone needing n8n templates to interact with OAuth2 authenticated services.
• n8n specialists testing the capabilities of the core Strava n8n node.

This comprehensive n8n workflow provides a robust demonstration of interacting with the Strava API through the platform's specialized Strava n8n node. Often, automation requires not just creating data, but subsequently modifying or reading that data based on the unique ID generated during creation. This n8n workflow template solves the problem of needing to chain dependent operations by sequentially creating an activity (a 'Morning Run' of 1000m), immediately updating it with a detailed description, and finally performing a GET request to verify the successful update. This is a foundational example for building more complex n8n automation scenarios involving fitness and personal tracking data.

The logical flow of this n8n workflow is strictly sequential, demonstrating chained operations:

1. Manual Execution: The process begins with the 'On clicking 'execute'' n8n trigger node, allowing for easy testing and demonstration.


2. Activity Creation (Strava): The first Strava n8n node creates a new activity named 'Morning Run', specifying parameters like the type ('Run'), elapsed time (3600 seconds), and distance (1000 meters).


3. Activity Update (Strava1): Immediately following creation, the second Strava n8n node retrieves the id generated by the previous node using an n8n expression (={{$node["Strava"].json["id"]}}). It then uses the update operation to add a description: 'Morning run in the park'.


4. Activity Retrieval (Strava2): The final Strava n8n node uses the get operation, again referencing the dynamically generated activity id. This action retrieves the fully updated activity record, proving that the creation and update operations in the preceding n8n nodes were successful.

To install this n8n workflow template, follow these steps:

1. Import: Copy the provided JSON data and paste it directly into your n8n instance via the 'New' menu > 'Import from JSON'.


2. Credentials Setup: You must configure Strava OAuth2 API credentials. In your n8n settings, add a new credential of type 'Strava OAuth2 API'. Follow the authorization flow to connect your Strava account.


3. Attach Credentials: Ensure that all three Strava n8n nodes ('Strava', 'Strava1', and 'Strava2') are configured to use the newly created Strava credentials.


4. Execute: Since the starting point is a manual n8n trigger, simply click 'Execute Workflow' or 'Execute Node' to run the entire sequence and observe the created, updated, and fetched data in the subsequent node outputs.

On clicking 'execute' (Manual Trigger): The starting n8n trigger for the workflow. It allows for immediate, manual execution to test the Strava integration logic.
Strava (Create Operation): This is the first Strava n8n node. Its function is to create a new activity with predefined static data (Type: Run, Name: Morning Run, Distance: 1000).
Key Configuration: Operation: Create Activity. Uses Strava OAuth2 credentials.
Strava1 (Update Operation): This crucial Strava n8n node updates the activity created in the previous step. It dynamically links to the output ID.
Key Configuration: Operation: Update Activity. Activity ID: ={{$node["Strava"].json["id"]}}. Update Field: Description ('Morning run in the park').
Strava2 (Get Operation): The final Strava n8n node. It retrieves the full activity details using the same dynamic ID, ensuring all previous updates were saved correctly to Strava.
Key Configuration:* Operation: Get Activity. Activity ID: ={{$node["Strava"].json["id"]}}.