Use a Bearer token or API key to authorize requests from AppFlowy to Blogs API. Store credentials securely in AppFlowy connections.
In AppFlowy create a new connection named Blogs API and paste the access token. Select appropriate scopes for post creation slug checks and reading categories.
GET emails/builder; 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; blogs/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 draft is created in AppFlowy or when a draft is updated
Actions include create post update post set category and assign slug
Uses POST /blogs/posts and PUT /blogs/posts/:postId
Required fields title content slug category_id author_id status
Trigger on demand or scheduled fetch
Update local records in AppFlowy with names and IDs from Blogs API
GET /blogs/categories and GET /blogs/authors
Fields id name slug description
Trigger when drafting a post or editing slug
Check slug existence and create or update posts with valid slug
GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId
Fields slug title
Faster go live with no code automation
Automatic content sync across platforms
Unified content creation in AppFlowy to multiple endpoints
Key elements include endpoints triggers actions authentication and data mapping used in no code workflows
A specific URL path and method used to perform an action in Blogs API
A URL friendly version of a post title used in blog URLs
Process to prove identity and authorize API requests such as bearer tokens
A series of actions that run automatically when a trigger occurs
Drafts created in AppFlowy automatically publish to Blogs API after approval in a workflow
Generate and validate slugs when creating posts
Map topics in AppFlowy to blog categories via the categories endpoint
Create the API connection in AppFlowy and grant access to Blogs API
Define field mappings and choose endpoints
Run tests and enable scheduled automation
No code is not required to connect AppFlowy with Blogs API. The integration uses standard API connections in AppFlowy to call the Blogs API endpoints. You can build powerful workflows without writing code. You can also start with ready made templates to speed setup.
Post publishing is best supported by the blogs posts endpoints. Use create or update post actions to publish drafts and manage metadata. You can also check slug existence to ensure clean URLs.
Slug existence is checked via the url slug exists endpoint. Run a quick ping before publishing to prevent duplicates. If a slug exists you can adjust the title or slug in AppFlowy and retry.
Yes, you can pull categories and authors from Blogs API and map them into AppFlowy. Schedule regular syncs to keep your planning content in sync with live data.
Use secure connections and rotate tokens. Limit access to only required scopes. Use read only for planning data and write where necessary. Store credentials safely in AppFlowy vaults.
Yes you can schedule posts to publish at a future time. Configure a time based trigger in AppFlowy to run the publish action when the post is ready.
API rate limits vary by plan. Check the Blogs API docs for current quotas and implement simple backoff retries in AppFlowy to stay within limits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
