Configure credentials and permissions to authorize the connection between Minut Smart Home Sensor and Blogs API. Use the recommended OAuth 2.0 flow or API keys as provided by your developer console.
Store and rotate tokens securely, apply the correct scopes, and follow best practices to keep the integration secure.
Blogs endpoints: POST /blogs/posts, GET /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors; Emails endpoints: GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule; Additional: GET /blogs/posts, POST /emails/builder and GET /blogs/categories for metadata.
Trigger: Minut detects a notable sensor event (e.g., motion spike) and immediately creates a new blog post in Blogs API.
Actions: POST /blogs/posts with a crafted title and body, optionally setting author and category to publish instantly or on schedule.
POST /blogs/posts
title, content, slug, authorId, categoryId, published
Trigger: A sensor alert fires and prepares a concise digest for distribution.
Actions: create or update an email template via POST /emails/builder; schedule delivery with GET /emails/schedule or POST /emails/builder/data as needed.
POST emails/builder; GET emails/schedule
locationId, templateId, subject, body, scheduleTime
Trigger: draft is written or updated and the slug is validated before publishing.
Actions: check slug with GET /blogs/posts/url-slug-exists; if available, create or update using POST /blogs/posts; otherwise adjust slug.
GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId
postId, slug, title, content
Automate content creation and notifications without writing code.
Leverage templates, workflows, and schedules to scale communications.
Improve decision making with real-time data-driven blog updates.
A quick glossary of the terms used in this guide and how they fit the integration.
An API is a set of rules that lets applications talk to each other securely and efficiently.
A URL that performs a specific action in an API.
An event that starts an automation or workflow.
The task executed by the system after a trigger fires.
Automatically publish a blog post whenever a significant sensor event occurs, with SEO-friendly metadata.
Compose a daily blog entry summarizing key metrics from sensors.
Post incident reports or status updates when devices go offline or require attention.
Register your app in the developer console and generate a client ID and secret, plus required scopes.
Map sensor events to blog actions and set up URL slugs and templates.
Run tests, verify webhooks, and monitor results in dashboards.
The Blogs API is a content management API that lets you create, update, and fetch blog posts programmatically. When connected to Minut Smart Home Sensor, you can automatically publish posts triggered by sensor events. This integration uses REST endpoints and webhooks to keep your content synced without manual steps.
No heavy coding is required. The connector uses no-code automations you configure in your dashboard, mapping sensor events to blog actions. If you need advanced logic, you can extend with custom workflows or add condition checks.
Essential endpoints for basic automation include POST /blogs/posts to create posts, GET /blogs/posts/url-slug-exists to check slugs, and GET /blogs/categories to categorize. For notifications, use emails/builder and emails/schedule endpoints to send email digests.
Slug existence can be verified using GET /blogs/posts/url-slug-exists, which returns a boolean. If the slug exists, you can modify or generate a new slug before publishing.
Yes. You can schedule blog posts or signals via emails endpoints or via the blog scheduling features, enabling timed publication. You can automate digests that summarize sensor events at regular intervals.
Supported authentication methods include API keys and OAuth 2.0 flows as provided by the Blogs API’s developer console. Always store tokens securely and rotate credentials periodically.
Error logs are accessible from the integration dashboard and the Blogs API console; enable webhooks and monitor delivery status. For troubleshooting, check request payloads, response codes, and rate limits; consult the docs or contact support.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
