Authenticate your Blogs API connection with a valid API key or OAuth token that includes read and write scopes for posts, categories, and authors.
Connect Chatwork via a secure access token or webhook signing as required by the App Connector to ensure message delivery and verification.
Core endpoints covered include GET emails/builder, GET emails/schedule, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts, GET /blogs/categories, GET /blogs/authors
Trigger: when a new blog post is published in Blogs API
Actions: post a formatted Chatwork message with the post title, excerpt, and link to the full post
GET /blogs/posts
Fields: postId, title, urlSlug, excerpt, publishedAt, author
Trigger: when a blog post is updated in Blogs API
Actions: post an update summary to Chatwork highlighting changed fields and including a link
PUT /blogs/posts/:postId
Fields: postId, title, slug, updatedAt, excerpt
Trigger: on demand or scheduled to sync metadata from Blogs API
Actions: post a digest of latest categories and authors to a Chatwork room
GET /blogs/categories
Fields: categoryId, name, description; authorId, name
Real-time updates: automatically push new posts to Chatwork for your team without writing code
Streamlined collaboration: discuss drafts and approvals in Chatwork alongside your content calendar
Reduced manual steps: standardize sharing to minimize errors and save time
This glossary explains core terms, data fields, and processes used when connecting Blogs API with Chatwork
A piece of content created in the Blogs API with a title, body, excerpt, and slug
A specific URL and HTTP method used to access an API resource in the Blogs API
An event in Blogs API that starts an automation in the App Connector
A notification or post sent to a Chatwork chat via the App Connector
Whenever a new post is published in Blogs API, automatically post a formatted summary in a designated Chatwork room
Share draft posts with teammates in Chatwork for quick feedback, then publish from Blogs API
Summarize new authors or categories weekly and post updates in Chatwork
Obtain your Blogs API key and authorize the Chatwork connector in the App Connector
Choose the new post and post updated triggers and set Chatwork actions to post messages
Run tests, verify messages in Chatwork, and enable the workflow
Authentication is handled through API keys or OAuth tokens provided by Blogs API. Ensure your token has the proper scopes to read posts and write updates. In the App Connector, link the Blogs API account and test a basic call to confirm access.
For notifications, use the blogs posts endpoints to pull new or updated content and map those fields to a Chatwork message. Consider using the posts list and post detail endpoints to enrich messages with title, excerpt, and author.
Yes. The App Connector allows you to format Chatwork messages with dynamic fields such as post title, excerpt, and link. You can customize the channel, message templates, and whether to include images or author credits.
No extensive coding is required. This is designed as a no-code integration via the App Connector. You configure triggers, actions, and field mappings through guided UI steps.
If you encounter errors, check the API response codes and validate your API key scopes. For rate limits, stagger requests, implement retries with backoff, and monitor quota usage in the App Connector dashboard.
Content changes are typically reflected via PUT and GET endpoints for posts. Updates to titles, slugs, and excerpts will be visible in Chatwork once the trigger fires and the action runs.
The endpoint list is included in the Core API Endpoints section of this page. The glossary terms section explains key terms and data fields used across the integration.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
