When new activity in Runkeeper, sync it to Reply.
When a workout milestone is met in Runkeeper, update outreach sequences in Reply.
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.
Reply Explore Reply →
TriggersFires when a new lead or contact is captured in Reply.
Fires when a contact enters an automation in Reply.
Fires when a field on a contact changes in Reply.
Fires when a contact unsubscribes in Reply.
Creates or updates a contact in Reply.
Adds a contact to a workflow or campaign in Reply.
Sends an email or message to a contact via Reply.
Changes a contact's tags in Reply.
Common questions
Can Knit build “When new activity in Runkeeper, sync it to Reply.” between Runkeeper and Reply?
Yes — describe it in the box above and Knit's Integrations Agent researches Runkeeper and Reply'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.