Use OAuth 2.0 tokens and the required scope emails/builder.readonly to authorize requests to the Blogs API from Runkeeper.
Connect Runkeeper by providing your Runkeeper app credentials and enabling the integration to view workouts and post updates to your blog.
Key endpoints you may use with Runkeeper and Blogs API: POST /blogs/posts (create posts), PUT /blogs/posts/:postId (update posts), GET /blogs/posts/url-slug-exists (check slug), GET /blogs/categories (list categories), GET /blogs/authors (list authors), GET /blogs/posts (list posts), POST /blogs/categories (add a category and assign to a post).
Trigger: A new Runkeeper workout is logged.
Action: Create a blog post using POST /blogs/posts with the workout summary as content, mapping title, slug, author, and category.
POST /blogs/posts
title, content, slug, authorId, categoryId
Trigger: Runkeeper workout details change.
Action: Update the corresponding blog post via PUT /blogs/posts/:postId with new content.
PUT /blogs/posts/:postId
postId, title, content, slug
Trigger: Runkeeper workout is categorized or tagged.
Action: Assign a category via POST /blogs/categories and update the post’s category field.
POST /blogs/categories
postId, categoryId
Create consistent content workflows without writing code using visual automations.
Automatically publish and update posts as workouts are logged or changed.
Maintain an SEO-friendly, searchable archive of Runkeeper activity on your blog.
A quick glossary of terms and processes used in this integration, including API, slug, post, and categories.
Application Programming Interface: a set of rules that allows two software systems to communicate.
A signal sent by a service to trigger an automated action in another service.
A URL-friendly identifier for a blog post used in links and SEO.
A blog entry created in the Blogs API.
Automatically publish daily workout summaries to your blog with visuals and stats.
Aggregate weekly workouts into a single post with key metrics.
Link Runkeeper workouts to author bios and categorize by athlete.
Authorize Runkeeper access and grant the Blogs API the required scope to read workouts.
Define how Runkeeper fields map to blog post fields (title, content, slug, category).
Enable automation and test with a sample workout to verify results.
No-code connections are possible through the visual automation builder. You can drag triggers from Runkeeper to actions in Blogs API without writing code. This keeps your setup fast and maintainable. Start with a simple workflow and gradually add conditions, mappings, and error handling as you grow.
For posting updates, map the Runkeeper trigger to a Blogs API action (POST /blogs/posts) to create posts, and use PUT /blogs/posts/:postId to update as needed. Use GET /blogs/posts/url-slug-exists to ensure unique slugs.
Yes. You can customize slugs by supplying your own slug value when creating or updating posts. Check slug availability with GET /blogs/posts/url-slug-exists and adjust as needed.
Expect occasional errors due to rate limits or invalid mappings. Build retries with exponential backoff and clear error messages. Log failures and alert your team when actions cannot complete.
Yes. Use triggers and filters to post only workouts that meet criteria such as duration or distance. You can also map only certain workout types to posts.
OAuth2 tokens with secure storage; use scopes appropriate to read workouts and write posts; rotate tokens regularly. Ensure data in transit is protected with TLS.
Yes, you can delete posts automatically if your Blogs API plan supports deletion. Include a delete action in your workflow to remove posts when needed. Alternatively, you can archive posts or set a published flag instead of deletion.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
