Authenticate using your Blogs API credentials and the required scope. This setup ensures Typebot can read and publish content securely.
Authorize Typebot to access your Blogs API account. Use OAuth 2.0 or token-based methods to grant permissions for publishing and managing posts.
Key endpoints include: GET emails/builder, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/authors, GET /blogs/categories, GET /blogs/posts/url-slug-exists, POST /emails/builder/data
Triggered when a Typebot form collects blog draft content from a user.
Map form fields to title, content, author, category, and slug, then publish via POST /blogs/posts.
POST /blogs/posts
title, content, author, category, slug
Triggered when post updates are required based on user input.
Update fields like title, content, slug, and category using PUT /blogs/posts/:postId.
PUT /blogs/posts/:postId
postId, title, content, slug, category
Triggered when a user asks for authors or categories or checks a post slug.
Retrieve authors via GET /blogs/authors or categories via GET / blogs/categories; validate slugs with GET /blogs/posts/url-slug-exists.
GET /blogs/authors
authorSlug, categoryName
Publish content directly from chat conversations without writing code.
Update posts and metadata quickly with template-driven mappings.
Personalize content experiences for each user interaction.
Elements include endpoints, triggers, field mappings, and error handling to ensure reliable automation.
An addressable function of the API exposed via a URL and HTTP method.
The process used to verify identity and authorize access to API resources.
A URL-friendly string derived from a post title to create unique slugs.
A specific URL on the API that performs an action.
Generate a cohesive series of blog posts from a single Typebot conversation, then publish automatically.
Capture user edits during chat and push updates to existing posts via the update endpoint.
Create weekly digest posts from user conversations and publish to your blog automatically.
Register your application, obtain API keys, and configure scope for the actions you’ll perform.
Choose OAuth 2.0 or token-based auth and map endpoints to Typebot variables.
Create content templates in Typebot and run tests to verify publishing and updates.
Yes. You can publish new posts directly from a Typebot flow using the POST /blogs/posts endpoint. Map the user-provided title and content to the post body and trigger the publish action from the chat. This eliminates manual steps and speeds up content production. Leverage templates to ensure consistent formatting and SEO-friendly metadata across posts.
You’ll typically map: title, content, author, category, slug, and any custom fields your blog uses. Also consider mapping post status and publish date if your workflow requires staged publishing.
Use standard OAuth 2.0 or token-based authentication. Store tokens securely, rotate them regularly, and scope access precisely to the required resources (e.g., read and write posts). Avoid exposing credentials in client-side flows.
If a slug already exists, the API can return a conflict error. You can either try a new slug or check slug availability in advance using GET /blogs/posts/url-slug-exists, then adjust accordingly before publishing.
Yes. You can pull lists of authors and categories via GET /blogs/authors and GET /blogs/categories and use them in Typebot prompts or dropdowns to enrich user interactions.
API endpoints may have rate limits. Plan batched requests where possible, cache frequent results, and gracefully retry with backoff in your Typebot flows.
Set up test flows that mimic real user interactions, run the publisher steps in a sandbox, and review published content in your blog to ensure proper formatting and SEO.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
