Resources · Make integration

Runkeeper Make integrationAutomate Runkeeper with Make.

Tired of copying runs by hand between Runkeeper and your other tools? The Runkeeper Make integration gives you 4 modules: 1 trigger that spots activities and 3 actions that create, update or delete them. This page shows how to connect your account and build a first working scenario.

Try the Runkeeper integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Runkeeper Make integration do for you?

The Runkeeper Make integration links your Runkeeper account to Make, a no-code tool where you chain apps into a scenario (the automation you build, step by step). Once connected, Make can notice activities in your account and create, change or remove them for you, without a line of code.

Keep a training log in sync. Watch activities hands each activity Make finds to the next module, so you can pass it to a spreadsheet, a chat tool or a CRM your coaching business already uses.

Log sessions that start somewhere else. A class booked in a form or a session added to a calendar can become a Runkeeper entry through Create an activity, so athletes stop typing the same workout twice.

Tidy up records. Update an activity fixes an entry after the fact, and Delete an activity removes one that should not be there, which matters when a test run or a duplicate slips in.

Be realistic about the scope. Make's own documentation for Runkeeper is marked as limited, and it lists no fields, no setup notes and no API call module. Expect to learn the details inside the editor. If you get stuck, the Make troubleshooting guide covers the common errors, and the Make training walks through the editor from the start. Wondering whether another tool fits better? The n8n vs Make comparison lays out both options side by side.

Connect

How do you connect Runkeeper to Make?

  1. 01

    Add a Runkeeper module

    In a scenario, click the +, type Runkeeper and pick any of its modules. The first time, Make asks for a connection, meaning your Runkeeper account linked to Make once and then reused by every Runkeeper module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the athlete or the account it belongs to. Make then sends you to Runkeeper to approve access, or asks for a key if the app provides one. Accept on the Runkeeper side.

  3. 03

    Save and pick it

    Click Save. Back in the module, the new connection is already selected. From now on, every Runkeeper module in any scenario can use it, so you only go through this once per account.

First scenario

Your first scenario with Runkeeper and Make

GoalWhen a workout is recorded in another tool, Make logs it in Runkeeper as a new activity.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the big + to add the first module: the app where workouts first appear, such as a form or a sheet your team fills in.

  2. 02

    Set up the starting app

    Connect that first app and fill its fields. Make lists what it can read once the connection exists, so pick the form or sheet from the dropdown rather than typing its name.

  3. 03

    Add Create an activity

    Click the + on the right of the first module, search Runkeeper and choose Create an activity. Select your Runkeeper connection or click Create a connection if you have none yet.

  4. 04

    Map the workout data

    Fill the fields Make shows for the activity by clicking into each one and picking values from the first module. Each workout arrives as a bundle, one item passed from module to module.

  5. 05

    Test with Run once

    Add a sample workout in the starting app, then click Run once. Open the bubble above each module to read the bundles it received, and check that the entry now shows up in Runkeeper.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule. A new scenario checks every 15 minutes by default. Then turn the scenario on so it runs without you.

Triggers

What starts a Runkeeper scenario?

1 module starts a scenario when something happens in Runkeeper. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Runkeeper as soon as it happens.

Runkeeper1Watch activities

Watch activities

triggerIn the docs only

Watch activities lets a scenario start from your Runkeeper account: each activity it finds becomes a bundle that the next modules can send to a sheet, a message or a report.

How it fires
scheduled, based on its name, since Make's docs give no type. Make checks the app on the scenario's schedule, every 15 minutes by default, and at most that often on the Free plan.
When to use it
Runkeeper is where the activity is born and you want other tools to hear about it.
Watch out
Make's docs describe no fields for this trigger, so click Run once and read the bundles to see what an activity actually carries.
Modules

What else can Make do with Runkeeper?

Runkeeper gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Runkeeper1

Create an activity

ActionIn the docs only

Create an activity writes a new entry into Runkeeper from data that lives in another app, so a workout exists in one place without anyone retyping it.

When to use it
a session is booked or recorded outside Runkeeper and should land in the athlete's history.
Watch out
pairing it with Watch activities on the same account can feed new entries back into the trigger.
Runkeeper2

Delete an activity

ActionIn the docs only

Delete an activity removes one entry from Runkeeper for good, which helps keep stats honest once a duplicate or a test run creeps into the log.

When to use it
a booking was cancelled in your source tool and its matching entry should disappear.
Watch out
Make's docs say nothing about getting a deleted activity back, so try it on a test record before you schedule anything.
Runkeeper3

Update an activity

ActionIn the docs only

Update an activity changes an entry that already exists, so a correction made in one tool shows up in Runkeeper too instead of leaving two versions around.

When to use it
you need to fix details on a known activity rather than add a new one next to it.
Watch out
the module has to know which activity to change, so map its identifier from an earlier module.
Need help

Need help automating Runkeeper with Make?

A person reads every message.

FAQ

Runkeeper and Make: common questions

01Is the Runkeeper Make integration free?
Yes, Runkeeper is a standard app, so it works on the Make Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle.
02What do you need to connect Runkeeper to Make?
A Runkeeper account and a Make account. Make's documentation lists no special prerequisite for Runkeeper and gives no official connection steps, so the standard flow applies: add a Runkeeper module, click Create a connection, give it a name if you want, approve access on the Runkeeper side or paste the key it gives you, then click Save. The connection is then reused by every Runkeeper module. Test the new connection with Run once before building on it.
03Does the Runkeeper Make trigger fire instantly or on a schedule?
On a schedule. Watch activities is the only Runkeeper trigger and it is not an instant one. Make's docs do not state its type, but its name points to a trigger Make checks on the scenario's schedule. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap allowed; paid plans go down to 1 minute. Nothing reaches Make between two checks.
04What if a Runkeeper module is missing in Make?
It depends on what you need. Runkeeper has 4 modules in Make and no Make an API Call module, so there is no generic way to reach other parts of the app from inside Make. Make also flags its Runkeeper documentation as limited. When a step is missing, look for another app that holds the same data, or ask the team at Hack'celeration to study your case. A bundle check with Run once also shows what data each module really returns.
05Should you use Make or n8n for Runkeeper?
It depends on what you already run. On Make, Runkeeper covers watching activities and creating, updating or deleting them, which fits a team that already builds its scenarios there. The same app often has an n8n node too, so check what that node offers before choosing. Pick the tool where your other automations live, since keeping everything in one place makes each scenario easier to follow and fix. The n8n vs Make comparison linked above lists the criteria in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations