To connect, generate an API key or OAuth token from your Blogs API dashboard and authorize Kenko to access the requested scopes (including emails/builder.readonly). This ensures secure, scoped access for templates, schedules, and post data.
In Kenko, create a new GHL connection and paste the Blogs API credentials. Test the token to confirm validity and scope alignment before enabling workflows.
Endpoint list: GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; emails/schedule.readonly; GET emails/schedule; GET blogs/post.write; POST /blogs/posts; POST /blogs/post-update.write; PUT /blogs/posts/:postId; blogs/check-slug.readonly; GET /blogs/posts/url-slug-exists; blogs/category.readonly; GET /blogs/categories; blogs/author.readonly; GET /blogs/authors
Trigger when a new blog post is created in Blogs API to pull the latest email builder templates and queue a notification in Kenko.
Actions include reading emails/builder templates, pulling data via /emails/builder/data, and updating or reusing templates for campaigns.
Usage example: GET emails/builder; POST /emails/builder/data
Required fields: locationId, templateId, postId, slug to map content and templates.
Trigger when a blog post is created or updated to sync with Kenko publishing workflows.
Actions include creating/updating a blog post via /blogs/posts and updating post status via /blogs/post-update.write.
Key paths: POST /blogs/posts; PUT /blogs/posts/:postId; POST /blogs/post-update.write
postId, slug, title, content, author
Trigger scheduled publishing or category updates to ensure aligned content distribution.
Actions include scheduling emails, assigning categories, and updating authors across channels.
Endpoints used: GET /blogs/categories; GET /blogs/authors; GET /blogs/posts/url-slug-exists
categoryId, authorId, postSlug
Launch campaigns and publish content in minutes with no code.
Automate workflows across email, blog publishing, and scheduling.
Scale content distribution with consistent templates and endpoint mappings.
Key elements include API endpoints, authentication, and data mapping between Blogs API and Kenko. The process flows from connection setup, to endpoint selection, to testing and going live.
A specific URL and HTTP method used to access a resource in the GHL API from Kenko.
Credentials (API key or OAuth token) that authorize requests between Blogs API and Kenko.
A URL-friendly version of a post title used to create clean, human-readable links.
Server-to-server callbacks that notify events such as create, update, or delete.
Automatically generate draft emails from new posts and queue them for review in Kenko.
Route posts to different email lists based on category tags to improve relevance.
Track post performance across channels and adjust content strategy.
Create a new GHL connection in Kenko and paste the Blogs API credentials. Validate the token.
Select the endpoints you want to enable (e.g., emails, blogs, scheduling) and map fields.
Run a test post and verify that data flows to your Kenko workflows before going live.
You can retrieve templates, schedules, and post data from Blogs API to tailor emails and blog workflows. This helps keep content consistent across channels. The Blogs API integration in Kenko enables quick pulling of templates and schedules to align with campaigns. Two paragraphs here.
Essential endpoints include GET emails/builder, POST /blogs/posts, and GET /blogs/posts/url-slug-exists for validating slugs. They enable creating, updating, and publishing content.
Yes. The connection uses a secure token and scoped permissions to ensure only selected data is accessible. No code is required to set up basic flows.
Use the Test Connection feature in Kenko to verify credentials, endpoints, and permissions before going live. Run a sample blog post and check results.
Field mapping lets you align blog post fields with email templates and schedules. Adjust mappings in the connection settings.
Security is maintained through token-based authentication, least privilege scopes, and encrypted data transfer.
Endpoint status appears in Kenko’s connection dashboard, where you can test, monitor, and reauthorize as needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
