To use the Blogs API with Neos, you’ll authenticate using the required scope emails/builder.readonly and your API credentials. This ensures read-only access to email builders and related features.
Neos authenticates with the Blogs API via the Zapier App Connector using secure OAuth tokens. Ensure you grant the necessary permissions and keep tokens refreshed.
Supported endpoints for this integration include: 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; blogs/post.write; blogs/post-update.write; POST /blogs/posts; 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 draft is created in Neos.
Actions: create a post in Blogs API (POST /blogs/posts), set title, slug, and content.
POST /blogs/posts
Key fields: title, content, slug, author_id
Trigger: check slug existence before creating/updating using GET /blogs/posts/url-slug-exists
Actions: verify slug, proceed with POST or PUT accordingly
GET /blogs/posts/url-slug-exists
Key fields: slug, postId
Trigger: update in Neos triggers PUT /blogs/posts/:postId
Actions: update title/content, update metadata, publish status
PUT /blogs/posts/:postId
Key fields: postId, title, content
Create content faster with no-code automation between Neos and Blogs API.
Reduce manual data transfer and fewer errors.
Keep content in sync across Neos and your blog system automatically.
Core terms and processes to help you navigate the integration between Neos and Blogs API.
A published article or entry stored in Blogs API with a title, body, and metadata.
A URL-friendly string used to identify a post in the blog system.
A specific URL path and HTTP method to perform actions with the API.
A standard authorization framework used to securely access APIs.
Trigger on new drafts in Neos to create posts in Blogs API and publish on schedule.
Sync edits instantly to the corresponding post in Blogs API.
Coordinate with email or scheduling endpoints to release content at optimal times.
Obtain API credentials and authorize the Zapier App Connector.
Select the endpoints you need for your workflows (e.g., create, update, slug check).
Run end-to-end tests and deploy to production.
No deep coding is required to get started—use the Zapier App Connector to bridge Neos and the Blogs API. You’ll need a valid API key and the proper scope. The setup wizard guides you through authentication and selecting endpoints.
To publish posts, connect the POST /blogs/posts endpoint and ensure the slug is unique. Add the post title, content, and metadata in your Neos workflow to trigger automatic publishing.
Slug conflicts are avoided by checking availability via GET /blogs/posts/url-slug-exists before creating. If a conflict is detected, update the slug or use a different title.
Neos authenticates using OAuth tokens via the Zapier connector. Maintain token security and refresh as needed.
Yes. You can schedule posts for future publication using the Blogs API scheduling workflows. Combine with emails/schedule endpoints for coordinated launches.
Yes, no-code automation is available through Zapier, allowing you to set up flows without coding. Use prebuilt triggers and actions to connect Neos and Blogs API.
The endpoints list is documented in the integration guide and accessible from the Zapier app connection screen. Key endpoints include GET /blogs/categories, GET /blogs/authors, POST /blogs/posts, GET /blogs/posts/url-slug-exists.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
