Create detailed Google Calendar events from new Runkeeper activities.
Create a detailed event on Google Calendar whenever a new workout activity is logged in Runkeeper.
See all Runkeeper + Google Calendar integrations or talk to a human
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.
Google Calendar Explore Google Calendar →
TriggersFires when a new event is created in Google Calendar.
Fires when an event's time or details change in Google Calendar.
Fires when an event in Google Calendar is canceled.
Fires shortly before a scheduled event in Google Calendar starts.
Creates a new event in Google Calendar.
Updates an existing event in Google Calendar.
Cancels an event in Google Calendar.
Finds an open time slot on a calendar in Google Calendar.
Common questions
Can Knit build “Create detailed Google Calendar events from new Runkeeper activities.” between Runkeeper and Google Calendar?
Yes — describe it in the box above and Knit's Integrations Agent researches Runkeeper and Google Calendar'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.