Authenticate securely using API keys or OAuth tokens. Store credentials safely and rotate them periodically to maintain a secure connection.
Create API credentials in Kommo or use an OAuth flow, then connect to the Blogs API via the Zapier-style app connector with proper scoping.
Primary endpoints used in this integration include: GET emails/builder, GET emails/builder.readonly, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, and related endpoints for authors and categories.
Trigger: When a new blog post is published in Blogs API
Actions: Create or update a contact in Kommo, add a note, and optionally send a digest email to subscribers.
POST /blogs/posts
title, slug, content, authorId, tags, publishDate
Trigger: When a blog post is updated in Blogs API
Actions: Update the corresponding Kommo record and log the update in the contact timeline.
PUT /blogs/posts/:postId
postId, title, slug, status
Trigger: Slug check using Blogs API (GET /blogs/posts/url-slug-exists)
Actions: Create a draft post in Blogs API and prepare a new Kommo record if the slug is available.
GET /blogs/posts/url-slug-exists
slug
Automate blog-to-crm workflows without writing code, using visual triggers and actions.
Keep blog content, authors, and schedules in sync with Kommo contacts and campaigns.
Leverage ready-made templates to accelerate setup and maintenance.
This glossary defines endpoints, triggers, actions, and field mappings you’ll encounter when automating with Blogs API and Kommo.
A specific URL and HTTP method used to access a resource in an API.
An event in an app that starts an automation.
An operation performed after a trigger to modify data or start a process.
A URL-friendly identifier used to locate a resource.
Capture the post author or subscriber from the new post and create a contact in Kommo with a link to the blog post.
Append post status or publication date to the contact timeline in Kommo.
Trigger a weekly digest via Kommo email templates to subscribers.
Create and securely store an API key or OAuth credentials from Blogs API.
In Zapier, choose Blogs API and Kommo, then connect using your credentials.
Set triggers, actions, and field mappings, then test and deploy.
No coding required. The integration uses visual workflows to connect Apps. You can set up triggers and actions without touching code. If you want a custom flow, you can add a few JavaScript steps, but it’s not necessary.
You will typically use endpoints related to blog posts, slugs, authors, and categories. Start with POST /blogs/posts to publish and PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to check slugs.
Authentication is done via API keys or OAuth tokens. Store credentials securely and rotate them periodically. Use app-level authentication in Zapier.
Yes, you can connect multiple Blogs accounts by creating separate connections in the connector and mapping fields accordingly.
The integration syncs blog posts, authors, categories, and related metadata, plus contact notes and digest emails as configured.
Most services enforce rate limits. If you hit a limit, stagger requests and cache results where possible.
Field mappings appear in Zapier as you configure the trigger and action. You can review and adjust in the app settings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
