Begin by obtaining your Blogs API key or OAuth token, then store it securely in WhatTime’s connection settings. The scope shown is emails/builder.readonly, which defines the permissions WhatTime will request when accessing the content.
Connect WhatTime to Blogs API by entering the API credentials into the app connector. This creates a secure channel for triggers and actions to flow between systems.
Endpoint List: 1) GET emails/builder 2) emails/builder.write 3) POST emails/builder 4) POST /emails/builder/data 5) DELETE /emails/builder/:locationId/:templateId 6) emails/schedule.readonly 7) GET emails/schedule 8) blogs/post.write 9) POST /blogs/posts 10) blogs/post-update.write 11) PUT /blogs/posts/:postId 12) blogs/check-slug.readonly 13) GET /blogs/posts/url-slug-exists 14) blogs/category.readonly 15) GET /blogs/categories 16) blogs/author.readonly 17) GET /blogs/authors
Trigger: New email draft created in Emails Builder.
Actions: Create a blog post using POST /blogs/posts with the email subject as the title and the email body as the content.
POST /blogs/posts
title from subject, content from body, slug generated or provided, author, status
Trigger: Updated blog post data in Blogs API through WhatTime.
Actions: Use PUT /blogs/posts/:postId to apply updates; map title and content from WhatTime fields.
PUT /blogs/posts/:postId
postId, title, content, lastModified
Trigger: New blog draft ready in Blogs API
Actions: Check slug uniqueness with GET /blogs/posts/url-slug-exists, then publish with POST /blogs/posts
GET /blogs/posts/url-slug-exists and POST /blogs/posts
slug, title, content, status
Automate publishing and updates without writing code. Use triggers, actions, and mappings to move data between Blogs API and WhatTime.
Visual workflow design lets you prototype integrations quickly and adjust mappings as needs evolve.
Built-in auditing, error handling, and retries improve reliability.
This glossary explains common terms used when connecting Blogs API with WhatTime, including endpoints, authentication, slugs, and data mappings.
An interface that lets WhatTime and Blogs API exchange data securely via defined endpoints and methods.
A specific URL and HTTP method used to perform an action against the API.
The process of verifying identity and granting access to API resources, typically via API keys or tokens.
A URL-friendly string derived from the post title used to form readable, SEO-friendly URLs.
Set up a recurring task to generate a weekly digest post from your drafts and publish via Blogs API.
Trigger content updates based on seasons or events and publish automatically.
Validate slugs and metadata to improve search visibility when publishing.
Register the Blogs API integration in WhatTime and copy your API key.
Choose endpoints such as POST /blogs/posts and PUT /blogs/posts/:postId and map fields.
Run tests, verify data flow, and enable automation for production use.
You can authenticate using API keys or OAuth tokens depending on what the Blogs API supports. Store credentials securely in WhatTime’s connector and scope access to the needed resources, such as emails/builder.readonly for reading templates and blog endpoints for publishing. The exact method will depend on your Blogs API setup.
Essential endpoints for publishing include POST /blogs/posts to create posts, GET /blogs/posts/url-slug-exists to verify slug availability, and PUT /blogs/posts/:postId to update existing posts. For metadata, fetch categories with GET /blogs/categories and author information with GET /blogs/authors.
Slug uniqueness is typically checked via GET /blogs/posts/url-slug-exists. If the slug already exists, adjust the title or slug and retry. Consider implementing a slug generation rule in WhatTime to consistently produce unique slugs.
Yes. Use PUT /blogs/posts/:postId to update a post’s title, content, or metadata. You can trigger updates from WhatTime when draft content changes or upon approval workflows.
Use WhatTime’s test mode to send sample requests and inspect responses. Verify credentials, endpoints, and data mappings, then monitor results in your logs and any webhook signals.
Rate limits depend on your Blogs API plan. Plan for bursts and implement retries with exponential backoff in WhatTime to maintain reliability during peak times.
Endpoint details are documented in the Blogs API reference. In WhatTime, you connect by supplying credentials, selecting endpoints, and running test requests to confirm data flow.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
