Use a secure API key with the required scope. The defined scope is emails/builder.readonly and you may request additional blog scopes as needed. Save credentials in a secure vault and connect through the app connector.
Rankr uses API tokens for authentication. Enter your Rankr API token into the App Connector and refresh when needed.
Key endpoints include the following. GET emails/builder and GET emails/schedule for email assets. POST blogs/posts to create posts. POST /blogs/posts to publish entries. PUT /blogs/posts/:postId to update posts. GET /blogs/posts/url-slug-exists to check slug availability. GET /blogs/categories for categories. GET /blogs/authors for author data. DELETE /emails/builder/:locationId/:templateId to remove templates. Additional endpoints cover scheduling and data retrieval such as GET emails/schedule and POST /emails/builder/data for template data.
Trigger when a new Rankr draft is finalized to create a post in Blogs API
Actions include creating a post, assigning author and category, and setting initial tags
POST /blogs/posts
title content slug authorId category
Trigger on publish date or ranking signals to schedule via Blogs API
Actions include setting publishAt updating status and confirming schedule
POST /blogs/posts
Trigger when Rankr content changes, then update the matching Blogs API post
Actions update content slug and metadata to keep both systems in sync
PUT /blogs/posts/:postId
postId title content slug
Visual no code workflows let you connect Rankr and Blogs API without writing code
Automatic data sync reduces manual updates and errors
Scale across teams with shared templates and approvals
A quick glossary of terms used in this integration including API endpoint terms slug and webhook
Application Programming Interface a set of rules that lets apps talk to each other
A specific URL path that performs a defined action
A notification sent in real time from one app to another
A human friendly unique identifier used in URLs
Automatically generate a blog post in Blogs API when a Rankr draft hits a defined threshold
Link Rankr performance signals to publish dates in Blogs API to keep content fresh
Push engagement metrics from Blogs API back to Rankr to adjust rankings
Create a secure connection by adding your API credentials to the App Connector
Map Rankr events to the corresponding Blogs API endpoints in your workflow
Create no code automations to trigger blog actions from Rankr
The connection uses API tokens over HTTPS to ensure encryption in transit. Keep credentials secure and rotate keys regularly. Apply least privilege access so only the necessary endpoints are reachable. You can enable IP allow lists for extra protection. Regularly review activity logs to detect unusual access. If credentials are compromised, revoke them immediately and reauthenticate.
For basic syncing you typically need to create or update blog posts using the blogs posts endpoints. Check slug availability with the slug check endpoint before publishing. You may also retrieve categories and authors to properly categorize posts. Optional endpoints for schedules and templates can be used as your workflow grows.
Yes you can schedule posts by providing a publishAt timestamp. Ensure time zones are correct and that the post status is set to scheduled upon creation. Monitor for any delays and verify that the scheduled publish occurs as expected. You can also update scheduled posts if changes are needed.
No heavy coding is required. Use the no code workflow builder to map events to endpoints and configure triggers. If you need advanced logic, you can extend with conditional steps or code blocks within the builder. Most teams can complete setup with drag and drop actions.
Slug conflicts happen when two posts share the same slug. Use the slug existence endpoint to validate uniqueness. If a conflict is found, modify the slug or append a unique suffix. Automations can attempt alternative slug generation automatically.
Common data fields synced include title, content, slug, authorId, category and publishAt. Additional metadata like tags and status can be tracked as part of your workflow. Ensure your field mappings are consistent across Rankr and Blogs API.
Logs and run history are visible in the App Connector dashboard. You can also route logs to your own logging system or a dedicated analytics workspace for deeper monitoring. Set up alerts for failures or retries to maintain reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
