Skip to main content
Webhooks let you forward Strava activity data to any external service the moment an automation fires. Instead of stopping at renaming an activity or updating gear, a webhook action sends an HTTP POST request containing the full activity payload as JSON — so you can pipe that data into a workflow tool, a custom API, a Discord bot, or anything else that can receive an HTTP request.
Outbound webhooks are a PRO-only feature. Upgrade to PRO to add webhook actions to your automations.

​
What webhooks do

When an automation with a webhook action is triggered by an incoming Strava activity, Strautomator:
  1. Evaluates all conditions in the automation (as usual).
  2. If the conditions pass, sends an HTTP POST request to the URL you specified.
  3. Includes the complete activity data as a JSON body in the request.
  4. Continues processing any remaining actions in the same automation.
The external service at your target URL receives the activity data and can act on it — post to Slack, log to a spreadsheet, trigger a smart home scene, or chain into a multi-step workflow.

​
How to add a webhook action

1

Open the automation editor

Go to Automations and open an existing automation, or click New Automation to create one.
2

Add an action

Scroll to the Actions section and click Add Action.
3

Select Webhook

Choose Webhook from the action type dropdown.
4

Enter your target URL

Paste the full URL of the endpoint you want to receive the payload. For example, a Zapier webhook URL, a Make (Integromat) scenario URL, or your own server endpoint.
5

Save the automation

Click Save. The webhook fires the next time this automation matches an incoming activity.
You can also prefix your URL with an HTTP method to use something other than POST — for example, PUT https://api.example.com/activities. Supported methods are GET, POST, PUT, PATCH, DELETE, and HEAD. When no method prefix is provided, Strautomator defaults to POST.

​
Payload format

The webhook body is a JSON object containing the full Strava activity record as processed by Strautomator. This includes all standard Strava fields plus any enriched data (weather, Garmin FIT data, city names, and so on) that was resolved during processing.

​
Sample payload

​
Key fields in the payload

​
string
The Strava activity ID.
​
string
The activity name, after any name-modifying actions in the same automation have run.
​
string
The sport type reported by Strava (e.g. Ride, Run, Swim, VirtualRide).
​
number
Total distance in metres.
​
number
Moving time in seconds.
​
number
Total elevation gain in metres.
​
number
Average speed in km/h.
​
number
Average heart rate in bpm, if heart rate data was recorded.
​
number
Average power output in watts, if a power meter was used.
​
string
Activity start time in UTC ISO 8601 format.
​
string
Resolved city name for the activity start location (PRO, requires city tags to be enabled).
​
string
Country of the activity start location.
​
object
The gear assigned to the activity, with id and name fields.

​
Use cases

Zapier workflows

Send activity data to Zapier and connect to 5,000+ apps — post a Slack message, add a row to Google Sheets, or create a task in your project manager.

Make (Integromat)

Trigger a Make scenario when an activity matches your conditions. Build complex multi-step automations beyond what any single app supports.

Discord bots

Post your activity summary to a Discord channel or DM — great for sharing ride stats with a club or training group.

Home automation

Trigger a Home Assistant webhook, a Philips Hue scene, or any smart home API when you finish a workout.

Custom APIs

Forward activity data to your own backend, database, or analytics pipeline with no middleware required.

Notification services

Push a notification to your phone via Pushover, Pushbullet, or ntfy whenever a specific type of activity is recorded.
Connect Strautomator to 5,000+ services via Zapier. Create a Zap with a Webhooks by Zapier trigger set to “Catch Hook”, copy the provided URL into your Strautomator webhook action, and map the activity JSON fields to any downstream app. No coding required.

​
Combining webhooks with other actions

Webhook is just another action type — you can combine it with name changes, description updates, gear assignments, or any other action in the same automation. The webhook fires after all other actions have been applied, so the payload reflects the final state of the activity.
If the target URL is unreachable or returns an error, Strautomator logs the failure and continues processing the activity. The webhook failure does not prevent other actions in the automation from completing or block the activity from being saved on Strava.