Authenticate to the Blogs API using API keys or OAuth, with the scope provided (emails/builder.readonly) to access blog data for integration with Wiza.
Connect Wiza to your account using your Wiza credentials so actions in Wiza can trigger Blogs API calls and keep data in sync.
GET emails/builder; POST /emails/builder/data; PUT /blogs/posts/:postId; POST /blogs/posts; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts; GET /blogs/categories; POST /blogs/posts; GET /blogs/authors
Triggered when a new blog post is published in Blogs API
Push post metadata to Wiza and enroll readers in related campaigns
POST /blogs/posts
title, content, slug, author_id
Triggered on post updates or slug changes
Update Wiza campaign segments and refresh post data
PUT /blogs/posts/:postId
postId, slug, status
Triggered on demand or scheduled
Pull /blogs/categories and /blogs/authors into Wiza for richer personalization
GET /blogs/categories or GET /blogs/authors
categoryId, name; authorId, name
Faster content distribution to your audience without writing code
Drag-and-drop automation to route posts into campaigns
Centralized data flow between platforms with minimal setup
Key elements include endpoints, triggers, actions, authentication, and data fields. Processes cover mapping fields, handling slugs, and keeping content in sync.
A set of rules and endpoints that allow software to communicate securely.
A real-time notification mechanism that informs apps when something changes, such as a new blog post.
A specific URL in an API that performs a defined action, such as GET /blogs/posts.
A URL-friendly identifier for a post used in linking and SEO.
Automatically push new blog posts to corresponding Wiza campaigns to nurture readers.
Use post topics to build audience segments in Wiza for targeted outreach.
Bring author and category data into Wiza to personalize messaging.
Create or obtain API key and set the scope to read blog data. Save securely.
Select the required endpoints from the list and test connections in the Wiza setup panel.
Create workflows that trigger on new posts and update Wiza campaigns accordingly.
No coding is required. The Wiza integration is designed for no-code users with a guided setup and clear field mappings. If you already use the Blogs API, you can connect via API keys and authenticate securely. The UI guides you through each field mapping step. You can test the connection in the Wiza panel and start with core blog endpoints to validate data flow.
Start with the core endpoints: GET /blogs/posts, POST /blogs/posts, and GET /blogs/categories. Test connectivity in the Wiza UI, then map required fields such as title, slug, content, and author.
Use API keys or OAuth as provided by Blogs API. Store credentials securely in the Wiza vault and rotate keys periodically. Wiza offers encrypted storage and a test-connection feature.
Yes. Map fields like title, slug, content, author, and category to corresponding Wiza fields. Use simple transform rules if needed to format content for campaigns.
Sync frequency is configurable in your Wiza workflow. Choose near real-time updates or scheduled intervals to balance API rate limits.
Existing campaigns can be enriched with blog data. Integrations can run alongside current flows without disruption, and you can gradually expand the data mappings.
Check the integration logs in Wiza for error codes. Common issues include invalid credentials, missing scopes, or endpoint rate limits. Use the retry guidance provided in the logs.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
