STRAVA n8n INTEGRATION: AUTOMATE STRAVA WITH N8N

This trigger fires automatically whenever a new activity is recorded in your connected Strava account. Whether it's a morning run tracked via your phone, a cycling session from your Garmin, or a manual entry, this trigger captures it all in real-time.

Configuration parameters:

• Credential to connect with: Select your authorized Strava account from the dropdown. This is required to authenticate webhook subscriptions.
• Object: Set to "Activity" to monitor workout-related events.
• Event: Choose "Created" to trigger only when new activities are added.
• Resolve Data: Toggle this on to receive complete activity details (distance, duration, elevation, etc.) rather than just the activity ID.
• Options: Additional properties section for future customization if needed.

Typical use cases: Automatically log new workouts to a Google Sheet or Airtable base for performance tracking, send a Slack notification to your coach or accountability partner when you complete a workout, trigger a webhook to update your personal fitness dashboard, or create a backup of activity data in cloud storage immediately after each workout.

When to use it: This is your go-to trigger for any automation that needs to react to new training sessions. Perfect for daily logging, notification systems, and real-time data synchronization.

This trigger activates whenever an existing activity is modified in Strava. This includes edits to the activity name, description, gear used, privacy settings, or any manual corrections to distance and time.

Configuration parameters:

• Credential to connect with: Dropdown to select your Strava account credential (required).
• Object: Set to "Activity" to focus on workout data.
• Event: Choose "Updated" to capture modifications to existing activities.
• Resolve Data: When enabled, n8n fetches the full updated activity object, giving you access to all current field values.
• Options: Expandable section for additional configuration.

Typical use cases: Keep external databases synchronized when athletes correct activity details, detect when privacy settings change on activities for compliance monitoring, update dashboard visualizations when activity titles or descriptions are edited, or trigger re-calculations in spreadsheets when distance or time corrections are made.

When to use it: Essential for maintaining data integrity across systems. If your workflows depend on accurate, up-to-date activity information, pairing this trigger with your "Activity Created" workflow ensures nothing falls through the cracks.

This trigger fires when an activity is removed from Strava, whether deleted manually by the user or through third-party app integrations. It's crucial for maintaining clean, synchronized data across your connected systems.

Configuration parameters:

• Credential to connect with: Select the Strava account to monitor (required).
• Object: Set to "Activity" for workout monitoring.
• Event: Choose "Deleted" to specifically capture removal events.
• Resolve Data: Enable to receive additional context about the deleted activity (note: deleted activities return limited data).
• Options: Additional properties section available for extended configuration.

Typical use cases: Remove corresponding records from external databases when activities are deleted, send alerts when team members delete training sessions (useful for coach oversight), update analytics dashboards to reflect accurate activity counts, or maintain audit logs of deleted workouts for compliance or record-keeping.

When to use it: Deploy this trigger when data consistency is critical. If you're building a system of record for training data, you need to know not just when activities are added, but also when they're removed.

This trigger activates when a new athlete account is created and connected to your Strava API application. It's particularly useful for platforms and services that onboard multiple Strava users.

Configuration parameters:

• Credential to connect with: Your Strava API credential with appropriate permissions (required).
• Object: Set to "Athlete" to monitor user account events.
• Event: Choose "Created" to detect new athlete registrations.
• Resolve Data: When enabled, returns full athlete profile data including name, profile picture, and activity stats.
• Options: Additional configuration properties available.

Typical use cases: Automatically create user profiles in your database when athletes connect their Strava accounts, send welcome emails or onboarding sequences to new users, add new athletes to team rosters or coaching platforms automatically, or trigger account setup workflows in connected systems.

When to use it: Ideal for SaaS products, coaching platforms, or community apps that integrate with Strava. Automate your user onboarding flow entirely.

This trigger fires when athlete profile information is modified, such as changes to name, bio, profile picture, weight, or FTP settings. It helps keep user data synchronized across your connected applications.

Configuration parameters:

• Credential to connect with: Strava account credential selection (required).
• Object: Set to "Athlete" for profile monitoring.
• Event: Choose "Updated" to capture profile modifications.
• Resolve Data: Enable to receive the complete updated athlete object with all current values.
• Options: Additional properties can be added for extended configuration.

Typical use cases: Sync athlete profile changes to your CRM or user database, update display names and avatars in your application when users modify their Strava profiles, recalculate performance zones when FTP or weight is updated, or maintain accurate contact information for coaching communications.

When to use it: Essential for applications that display athlete information or use profile data for calculations. Keep your user records fresh without manual intervention.

This trigger activates when an athlete account is deleted or when a user revokes access to your Strava application. It's critical for proper data cleanup and compliance with user requests.

Configuration parameters:

• Credential to connect with: Select the authorized Strava credential (required).
• Object: Set to "Athlete" for user account monitoring.
• Event: Choose "Deleted" to detect account removal or deauthorization.
• Resolve Data: Toggle to resolve additional data about the deletion event.
• Options: Section for additional configuration if needed.

Typical use cases: Automatically remove user data from your systems when they disconnect Strava (GDPR compliance), trigger offboarding workflows when athletes leave your platform, update subscription or membership status in billing systems, or send exit surveys or feedback requests to departing users.

When to use it: Mandatory for any application handling user data. Proper cleanup when users revoke access isn't just good practice—it's often a legal requirement.