To call the Blogs API you need a secure access token with the required scope. Store credentials safely and attach the token to each request
Authorize via a GitHub App or Personal Access Token with permissions aligned to the endpoints used by the integration
Core endpoints you may use include GET emails/builder, POST blogs posts, PUT blogs posts and checks for slug existence along with read only access for schedules and categories
Trigger on a GitHub push to a chosen branch to create or update a blog post in Blogs API
Actions include mapping commit data to post fields and calling POST /blogs/posts
POST /blogs/posts
title, content, slug, status
Trigger on commit updates or PR merges to modify a post
Use PUT /blogs/posts/:postId to apply edits
PUT /blogs/posts/:postId
postId, title, content, lastEdited
Open issues or PRs can trigger draft posts
Call POST /blogs/posts to create and set status to draft
POST /blogs/posts
title, content, issue_number, labels
Automate publishing from GitHub without writing code
Keep content in sync with repository metadata and issues
Reduce manual steps and speed up content iteration
Key elements include endpoints, authentication, payload mapping and trigger workflows; processes describe how data moves from GitHub to Blogs API
A specific URL and method used to perform an action against Blogs API or the GitHub integration
The process of proving identity and obtaining an access token to call APIs securely
A callback that notifies your system when events occur in GitHub
The data structure sent to the API during a request including fields like title and content
Turn a successful push into a published post with automation that includes commit messages and author info
Create draft posts when issues or PRs are opened and publish after review
Automatically update published posts when PRs are merged
Authorize the GitHub connection in Blogs API and generate a webhook URL and token
Add a webhook to emit push, issues and PR events to Blogs API
Define how payload fields map to post fields and run tests
No coding is required with our no code editor. You can connect GitHub to Blogs API using a simple visual mapper that links event data to post fields. Create automations that run on push or issue events without touching code. You can test and adjust mappings in a dedicated test area.
Essential endpoints include creating posts with POST /blogs/posts, checking slug availability GET /blogs/posts/url-slug-exists, and updating posts with PUT /blogs/posts/:postId. You may also pull lists of categories and authors to tag posts.
Authentication is handled via a generated access token for Blogs API together with a GitHub App or PAT. Attach the token to requests and keep it secure. Detailed steps guide you through OAuth or token setup.
Yes, you can schedule posts by setting a publish date in the post payload or using a separate scheduling endpoint. You can define cadence and time zones for automatic publication.
If something goes wrong you can revert by restoring the previous post version or deleting the draft. Use versioning and the PUT endpoint to apply corrections.
Use a field mapping interface to map GitHub payload properties like commit message, issues or PR data to post title and content. Validate mappings with test payloads.
Support is available via our help center, documentation and community forums. You can also contact our support team for hands on assistance with setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
