Use a secure API key and OAuth style tokens to authenticate calls from EMnify to the Blogs API and ensure scoped access.
EMnify requires valid credentials with the emails/builder.readonly scope and related permissions to access templates and schedules.
GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule.readonly; GET emails/schedule; POST /blogs/posts; GET /blogs/posts/url-slug-exists; PUT /blogs/posts/:postId; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts; GET /blogs/categories; GET /blogs/authors
Trigger when a new or updated template is created in EMnify to sync with the Blogs API templates
Actions include retrieving template data from EMnify and pushing to emails builder endpoints
GET /emails/builder
templateId, name, subject, body
Trigger when a blog post is scheduled or published in EMnify to post to Blogs API
Actions include posting new content and scheduling promotion emails
GET /blogs/posts
postId, title, slug, status
Trigger when slug or category changes in Blogs API and update EMnify references
Actions include updating slug and category data via blogs check slug and categories endpoints
PUT /blogs/posts/:postId
postId, slug, categoryId, seoTitle
Automate templates and posts without writing code using visual builders
Create drag and drop workflows that connect EMnify with Blogs API
Centralized analytics across email campaigns and blog content
A short glossary of terms and core processes used to connect EMnify with Blogs API
Application Programming Interface a set of rules that lets apps talk to each other
URLs and paths used to access resources and actions in an API
Authentication and authorization methods to secure API requests
A URL friendly identifier used for blog posts
Automatically generate an email template when a new blog post is published
Trigger promotional emails when a post is scheduled
Keep author and category data aligned between EMnify and Blogs API
Add Blogs API keys and EMnify credentials to the integration
Connect endpoints such as GET emails builder and GET blogs posts
Run tests and enable automation in production
No code is required to enable EMnify to Blogs API workflows using visual builders. You can connect APIs with clicks rather than code. If your use case grows you can still extend with custom steps. The key is mapping the actions to the correct endpoints.
Essential endpoints include GET emails/builder to read templates and GET blogs/posts to fetch content. POST emails/builder to create or update templates and PUT blogs/posts to update a post. Others handle scheduling and slug checks.
Authentication uses API keys and tokens with scoped permissions. Ensure the scope matches the EMnify needs like emails/builder.readonly. Tokens refresh regularly to maintain a secure connection.
Yes you can trigger email campaigns when a new or updated blog post is published. Use the posts and templates endpoints to coordinate content and email campaigns.
Slug updates can be propagated by checking slug existence and then updating the post via the blogs endpoints. EMnify can push category changes too.
If a template changes in Blogs API EMnify will fetch the updated template and push it to the builder as needed during the workflow. This keeps templates in sync without manual steps.
API rate limits are defined by the Blogs API provider. Plan requests to stay within the limits and use batching where possible.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
