Begin by granting EasyMe permission to access your Blogs API data to ensure secure calls and proper ownership.
In this step, provide EasyMe credentials to generate an access token for the Blogs API.
Endpoints 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; POST /blogs/posts; blog 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 new blog post is created in Blogs API, automatically publish or schedule in EasyMe.
Actions: create email templates, update posts, notify subscribers.
Method path: GET /blogs/posts and POST /blogs/posts to create or fetch posts.
Key fields: postId, slug, title, authorId, categoryId
Trigger: schedule-based publish in EasyMe when a blog post is updated.
Actions: update post, queue in EasyMe calendar, refresh feeds.
Method path: PUT /blogs/posts/:postId and POST /blogs/posts
Key fields: postId, scheduledAt, status
Trigger: new post published or new comment triggers alerts.
Actions: send notifications, update subscriber segments, log analytics.
Method path: GET /blogs/authors and GET /blogs/categories
Key fields: authorId, categoryId, emailList
Build complex workflows without writing code using drag-and-drop steps.
Automate repetitive tasks with triggers, actions, and data mappings.
Launch campaigns and publish posts faster with integrated tools.
This glossary defines terms used for APIs, endpoints, triggers, and data fields in the Blogs API + EasyMe integration.
A set of rules that lets two systems communicate and share data securely.
A specific URL path in an API that performs a defined action or returns data.
An event in one system that starts an automation in another system.
The process of proving identity to access the API, often via OAuth or tokens.
Aggregate weekly posts in Blogs API and push a summarized roundup to EasyMe campaigns.
When a post goes live, automatically start an EasyMe nurture sequence.
Use blog categories to tailor EasyMe campaigns to reader interests.
Create or copy your Blogs API key from the dashboard and store securely.
Authorize EasyMe to access your Blogs API data using OAuth or token-based auth.
Map blog fields (title, content, slug, author) to EasyMe fields to enable automation.
No coding is required. The visual workflow builder handles triggers and actions, and you can set up steps with drag-and-drop. You can also copy templates to reuse across posts.
For basic workflows, you mainly need access to the Blogs API endpoints for posts, categories, and authors, plus email endpoints if you want messaging. The connector guides you through mapping fields and testing the flow.
We use OAuth tokens and encrypted requests; you can revoke access anytime from the Apps settings. Data at rest is encrypted and transit is secured.
Yes. Use the scheduling endpoints to queue posts for future publication; you can set time zones and recurrence. The workflow can trigger based on dates or events.
Test mode lets you run dummy data and view responses. Check the logs, error messages, and retry options.
If the API changes, update the endpoint paths and field mappings in your workflow. We publish updated connector docs and migration tips.
API docs, auth guides, and support are available in the developer center and via our support team.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
