Latenode

Automatically sync Strava workouts to your Runkeeper account

This template checks Strava on a schedule, lists recent athlete activities, and posts each new workout to Runkeeper.

JavaScript keeps activity ids you already synced and maps type, duration, and distance. Connect Strava. Put the Strava token on the Strava connection. Put the Runkeeper access token in the JavaScript node that calls the Runkeeper API.

Updated Sep 16, 2026Est. run: 9sEst. cost: $0.0006
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Copies new Strava workouts into Runkeeper
  • Lists activities on a schedule through Strava
  • Keeps the Strava token on the Strava connection
  • Puts the Runkeeper token in the JavaScript node

How it works

1
Trigger

Run on a schedule

The scenario starts on the cadence you set, such as every 15 minutes.

2
Action

List new Strava activities

Strava returns recent athlete activities. Fetch extra detail when the list payload is thin.

3
Action

Create the Runkeeper workout

JavaScript drops ids you already synced, then posts type, duration, and distance to the Runkeeper API. Put the Runkeeper access token in that JavaScript node.

Setup guide

1

Connect Strava

Add a Strava connection and sign in with access to list athlete activities.

2

Store the Runkeeper token

Add a JavaScript node that posts new activities to the Runkeeper API. Put the Runkeeper access token in that node.

3

Set the schedule and skip repeats

Add a schedule, for example every 15 minutes. List athlete activities, skip ids you already sent, then create the Runkeeper workout. Record a test activity and confirm it appears in Runkeeper.

Requirements

A Strava athlete connection that can list activities
A Runkeeper access token stored in the JavaScript node
A schedule

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.