Obtain API credentials for Blogs API and configure secure authentication in Zabun to authorize requests to the Blogs API.
Store and use Zabun’s credentials to securely authenticate with the Blogs API.
Endpoints covered include: GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/categories; GET /blogs/authors
Trigger: When a new blog post is created in Zabun, push a draft to the Email Builder to start the email workflow.
Actions: Create email drafts (POST /emails/builder) and schedule delivery (POST /emails/builder/data or via emails/schedule).
Key paths: GET emails/builder; POST /blogs/posts
postId, templateId, locationId, slug
Trigger: Create or update a Zabun blog post to automatically update the corresponding post in Blogs API.
Actions: POST /blogs/posts, PUT /blogs/posts/:postId; optionally POST /blogs/post-update.write to push updates.
Paths: POST /blogs/posts; PUT /blogs/posts/:postId
postId, slug, author, categories
Trigger: When glossary terms or suggested keywords are updated, refresh metadata and content suggestions.
Actions: Generate glossary term definitions, fetch top keywords, attach to posts; update posts using existing endpoints.
Paths: GET /blogs/categories; GET /blogs/authors; GET /blogs/posts/url-slug-exists
slug, keywords, categories, author
Fast setup with prebuilt connectors and templates that require no coding.
Drag-and-drop automation to map content workflows between Zabun and Blogs API.
Real-time data sync and monitoring without writing custom code.
Key elements include API endpoints, authentication methods, data field mappings, and workflow automation steps.
A defined interface that lets Zabun interact with the Blogs API to perform actions like create, read, update, and delete content.
A specific URL path used to access a resource in the Blogs API.
An article stored in the Blogs API that Zabun can create, schedule, publish, or update.
A URL-friendly identifier for a blog post, used in URLs and slug checks.
Automatically generate a welcome email series from a new blog post, using Blogs API data and Zabun automation to trigger the sequence.
Assemble email blocks from blog fields like title, summary, and category to personalize newsletters without code.
Generate SEO-friendly post summaries and meta descriptions from Blogs API data to enhance email content and discoverability.
Request an API key and secret from Blogs API and securely store them in Zabun.
Map fields like title, content, slug, category and author between Zabun and Blogs API. Set up endpoint connections.
Run tests, check logs, and enable monitoring before going live.
No coding is required for a basic integration. Zabun’s visual workflows can connect to the Blogs API using pre-built actions such as creating posts, drafting emails, and checking slug availability. For more complex needs, you can configure field mappings and endpoint connections. If you need tighter control, you can adjust authentication methods, permission scopes, and retry policies to ensure reliable syncing.
Core syncing typically involves endpoints for emails and blog content, such as GET emails/builder, POST /emails/builder, POST /blogs/posts, and PUT /blogs/posts/:postId. You’ll also use endpoints to check slug availability and retrieve authors and categories. Set up triggers to respond to Zabun events (new posts, updates) and map fields between Zabun and Blogs API to keep content in sync without manual steps.
Start by requesting an API key (and secret) from Blogs API. In Zabun, configure the API credentials and choose an authentication method (api key or OAuth as supported). Pass the token with your requests and use secure storage for credentials. Test authentication with a simple smoke test to confirm access to endpoints like GET emails/builder and GET /blogs/posts/url-slug-exists before enabling full automation.
Slug management is performed using GET /blogs/posts/url-slug-exists to verify uniqueness before publishing. You can also update the slug via the PUT /blogs/posts/:postId path. Categorize posts by using the blogs/categories endpoint and assign authors with blogs/authors to keep taxonomy consistent.
View and select authors and categories by querying GET /blogs/authors and GET /blogs/categories. These endpoints help you map Zabun content to the correct author attribution and taxonomy. Use the retrieved data to populate fields in your content templates and ensure consistency across channels.
Rate limits depend on your Blogs API plan; monitor request counts and implement retries with exponential backoff. Best practices include batching non-urgent updates, queuing content actions, and separating read versus write requests to reduce bottlenecks and improve reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
