Secure access uses an API key or OAuth token with the scope emails/builder.readonly to read and initiate blog related actions.
Nusii Proposals uses standard OAuth 2.0 client credentials flow to authorize with the Blogs API and keep access tokens refreshed.
GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, emails/schedule.readonly, GET emails/schedule, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, GET /blogs/categories, GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId
Trigger: when a Nusii proposal moves to approved, create a new blog post draft via POST /blogs/posts.
Actions: compose the post from proposal data and submit to Blogs API; then optionally update the proposal with the post URL.
POST /blogs/posts
title, content, slug, author, category, tags
Trigger: when a blog post is updated (PUT /blogs/posts/:postId) or when slug existence is checked (GET /blogs/posts/url-slug-exists).
Actions: sync title, summary, and notes back to the related Nusii proposal; keep status in sync.
PUT /blogs/posts/:postId
postId, slug, title, summary
Trigger: when a blog post is published or scheduled for release.
Actions: send notifications via emails/builder and trigger templates; fetch templates with GET /emails/builder.
POST /emails/builder
templateId, locationId, subject, body
Faster content-to-proposal loops with zero custom code.
Consistent branding across proposals and published posts.
Real-time updates between systems without manual data entry.
Key elements include endpoints, triggers, templates, field mappings, and data objects shared between Nusii Proposals and the Blogs API.
A URL that exposes a specific function in an application for programmatic access.
An event that starts an automation or workflow.
A callback URL that receives real-time data from another service.
A URL-friendly string used in blog post URLs.
Convert proposal bullet points into a ready to edit blog outline and publish via the Blogs API.
Create draft posts using Nusii proposal data and refine before publishing.
Update Nusii proposals with blog performance insights and author notes.
Generate API credentials for both apps and grant required scopes such as emails/builder.readonly.
Define mappings for title, content, slug, category, and author to ensure posts reflect proposal data.
Run test workflows, verify triggers, and deploy automation to production.
You primarily use the blogs endpoints like POST /blogs/posts and GET /blogs/posts/url-slug-exists along with related template and emails endpoints. This lets you create posts from proposals and validate slugs before publishing. Use a test environment to validate data flows before going live.
No code is required for many automations thanks to the Zapier app connector and the built in endpoints. You can map data and trigger actions without writing code. If you want deeper customization, small scripts can be added in your automation platform.
Yes. You can configure email notifications using the Emails API. Create templates, set triggers, and send updates to your team when a new post is created or a proposal status changes.
Slug conflicts are checked via GET /blogs/posts/url-slug-exists. If a slug exists, adjust by adding a suffix or using a slug generator rule. Ensure each published post has a unique slug.
The essential scope mentioned is emails/builder.readonly for read access to emails. Depending on your needs you may add additional blog related permissions in your OAuth scope set as required by your integration.
Test with a sandbox or staging environment. Use the slug exists endpoint to validate names before publishing and run end-to-end tests to confirm triggers and actions behave as expected.
Field mappings and endpoint references are described in the sections above. You can also consult the API documentation for endpoints like POST /blogs/posts, PUT /blogs/posts/:postId, and GET /blogs/posts/url-slug-exists.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
