To authenticate the Blogs API in GHL, obtain an API key and ensure the scope emails/builder.readonly is granted. Use OAuth tokens for secure, scoped access and rotate credentials regularly.
Rankr authenticates with the GHL API using OAuth tokens and stored credentials. Treat secrets as private and never embed them in client-side code; use server-side handling and secret vaults.
GET emails/builder; GET emails/schedule; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET /blogs/posts; GET /blogs/categories; GET /blogs/authors
Trigger: user opens the email builder in Rankr and templates are requested from GHL.
Actions: fetch GET emails/builder, map template fields (templateId, name, subject, content) into Rankr templates, cache for fast access.
GET emails/builder
templateId, name, subject, content
Trigger: calendar or schedule update in Rankr.
Actions: pull GET emails/schedule, create/update Rankr events with fields like scheduleId, time, status, recurrence.
GET emails/schedule
scheduleId, time, status, recurrence
Trigger: a new draft appears in Rankr.
Actions: POST /blogs/posts to publish, map postId, slug, authorId, status.
POST /blogs/posts
postId, slug, status, authorId
Build powerful automations without writing code, using visual triggers and actions.
Keep content, emails, and posts in sync in real time across Rankr and GHL.
Prototype new workflows quickly and test changes with confidence.
A quick glossary of terms used in the GHL-Rankr vPlan integration and how they map to everyday content workflows.
Application Programming Interface — a set of rules that lets programs talk to each other.
A specific URL path in an API that performs a defined action.
Open Authorization; a standard for secure delegated access using tokens.
A URL-friendly identifier used in post/permalink paths.
Pull email templates and generate blog outlines to accelerate content planning in Rankr.
Clone a successful post structure between campaigns using vPlan triggers.
Automate slug creation and verify slug-exists checks before publishing.
Create API credentials in GHL for Blogs API with scope emails/builder.readonly and securely store tokens in Rankr.
Map the endpoints you plan to use (e.g., GET emails/builder, GET emails/schedule, POST /blogs/posts) to Rankr fields.
Run test payloads, review logs for errors, then enable the vPlan workflow in production.
No advanced coding is required. The vPlan connector provides a visual workflow to connect endpoints. Use pre-built triggers and actions to automate tasks like template retrieval and post publishing. If you know basic API concepts, you’ll be able to customize mappings quickly. If you’re new, start with the simplest 1:1 mappings and expand.
Essential endpoints include getting email templates (GET emails/builder), viewing schedules (GET emails/schedule), and creating or updating blog posts (POST /blogs/posts). Other endpoints like slug checks (GET /blogs/posts/url-slug-exists) and author or category lookups can help enrich data during synchronization.
Authentication uses a secure API key and OAuth tokens with the scope you need (for example, emails/builder.readonly). Store credentials in a secure vault and rotate them regularly. Never expose tokens in client-side code.
Yes. You can configure a trigger to create or publish posts in Blogs API when Rankr drafts reach a certain status. Use the POST /blogs/posts endpoint to publish and keep status synchronized.
Map fields one-to-one between Rankr and Blogs API (e.g., postId to id, title to name). Use consistent data types and validate required fields before publishing.
Endpoint documentation is available in the GHL API docs for the Blogs API. You can also view the endpoint list within the vPlan connector UI and in the integration guide for Rankr.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
