When new activity in Runkeeper, sync it to Journey.
When a new activity is completed in Runkeeper, log fitness entries in Journey.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Runkeeper Explore Runkeeper →
TriggersFires when a new member, client or user joins in Runkeeper.
Fires when someone books a class or session in Runkeeper.
Fires when a workout, habit, journal entry or goal is logged in Runkeeper.
Creates or updates a member's profile in Runkeeper.
Books a class or session for a client in Runkeeper.
Logs a workout, habit or data point in Runkeeper.
Journey Explore Journey →
TriggersFires when a new note or document is created in Journey.
Fires when an existing note or document changes in Journey.
Fires when a document in Journey is viewed or shared with someone.
Generates a new document in Journey from a saved template.
Creates a note in Journey or adds text to an existing one.
Converts a file in Journey to PDF.
Publishes a document from Journey or shares it by link.
Common questions
Can Knit build “When new activity in Runkeeper, sync it to Journey.” between Runkeeper and Journey?
Yes — describe it in the box above and Knit's Integrations Agent researches Runkeeper and Journey's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.