Begin by creating an OAuth connection for Blogs API with the scope emails/builder.readonly. Use the available endpoints to read, create, update, and manage posts and related resources.
In Zapier, add a new connection to Blogs API, choose OAuth 2.0, and authorize. Grant the emails/builder.readonly scope. Zapier securely stores tokens for all actions.
– GET emails/builder; – POST emails/builder; – POST /emails/builder/data; – DELETE /emails/builder/:locationId/:templateId; – emails/schedule.readonly; – GET emails/schedule; – blogs/post.write; – POST /blogs/posts; – 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 compelling Office 365 email lands in a designated label, automatically draft a blog post.
Actions: Use POST /blogs/posts to create posts, and GET /blogs/posts/url-slug-exists to verify slug availability.
Method path: POST /blogs/posts (title/content/slug derived from email).
Key fields: title, content, slug, postId
Trigger: New blog draft is ready for publication
Actions: Schedule via POST /blogs/posts and publish via PUT /blogs/posts/:postId at the desired time.
Method path: POST /blogs/posts to create, PUT /blogs/posts/:postId to schedule/publish.
Key fields: postId, scheduleTime, status
Trigger: A post is published in Blogs API and ready for distribution
Actions: Use GET /blogs/authors and GET /blogs/categories to enrich emails; craft distributions with emails/builder templates.
Method path: GET /blogs/authors, GET /blogs/categories, POST /emails/builder.
Key fields: authorId, categoryId, templateId
Automate content workflows without writing code, linking Blogs API to Office 365 through Zapier.
Schedule, update, and distribute blog posts automatically across channels with no coding needed.
Maintain publishing cadence and reduce manual tasks using event-driven automations.
This glossary defines common terms used throughout this guide: API Endpoint, Trigger, Action, Post, Slug, Schedule, and related concepts.
A specific URL path in the API that accepts requests and returns data or performs an action.
A blog entry created or updated via the API.
A URL-friendly version of the post title used in links and SEO.
A time window when a post is set to publish or be distributed.
Automatically convert noteworthy Office 365 emails into drafts by posting to /blogs/posts with a derived slug.
Use PUT /blogs/posts/:postId and POST /blogs/post-update.write to keep content current.
Schedule publications and deliver via Office 365 email templates using the Apps Connector.
Register the Blogs API app in Zapier, obtain client ID and secret, and set the redirect URL.
Add a new connection in Zapier, select OAuth 2.0, and authorize with the scope emails/builder.readonly.
Create a Zap that uses Office 365 triggers to drive Blog posts via the Blogs API endpoints; test thoroughly before going live.
The Blogs API is a set of endpoints that exposes blog-related actions. It connects with the Zapier App Connector via OAuth tokens to enable automation without coding. This guide focuses on using the endpoints for creating, updating, and distributing posts within your Microsoft Office 365 workflow.
Scopes like emails/builder.readonly and blog-related write permissions provide read and write access to emails, drafts, and posts. Ensure your app requests exactly what it needs and that your account has the required permissions.
Yes. Use the GET /blogs/posts/url-slug-exists endpoint to verify slug availability before creating or updating a post.
POST /blogs/posts creates posts; PUT /blogs/posts/:postId updates content and metadata; GET /blogs/post-update.write handles post updates.
Use POST /blogs/posts to create a draft, then schedule with PUT /blogs/posts/:postId and the scheduling endpoint to publish at a chosen time.
No-code automation is possible with Zapier App Connector, which handles authentication, workflow building, and error handling for you.
If you encounter issues, review the Zapier task history and the API error responses; verify tokens, scopes, and endpoint permissions, and re-auth if necessary.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
