Authenticate requests with a secure API token issued in the Blogs API dashboard. Include the token in the Authorization header (Bearer
In Outgrow, generate an API key for the Blogs API connection and paste it into the connector. The app will use this key to sign requests, so keep it private.
Endpoints include: GET emails/builder; POST /emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; PUT /blogs/posts/:postId; POST /blogs/posts; blogs/post.write; blogs/post-update.write; GET /blogs/posts/url-slug-exists; blogs/check-slug.readonly; GET /blogs/categories; blogs/category.readonly; blogs/author.readonly; GET /blogs/authors
Trigger: when new content is finalized in Outgrow to publish to a blog via the Blogs API.
Actions: POST /blogs/posts to create a post; optionally update with PUT /blogs/posts/:postId after review.
POST /blogs/posts
title, content, excerpt, slug, authorId, categoryId, publishedAt
Trigger: Outgrow content updates trigger a post update.
Actions: PUT /blogs/posts/:postId to update; use blogs/post-update.write for change tracking.
PUT /blogs/posts/:postId
postId, title, content, slug
Trigger: when creating a post to assign category and author data.
Actions: GET /blogs/categories and GET /blogs/authors to populate selection lists.
GET /blogs/categories; GET /blogs/authors
categoryId, authorId
Rapid setup without coding—configure triggers, actions, and field mappings with a few clicks.
Automate end-to-end publishing workflows from idea to live post.
Centralize content data and analytics between Outgrow and your Blogs API.
Key elements include endpoints, authentication, triggers, actions, fields, and responses. Understanding these helps you design predictable integrations.
A defined URL path that performs a specific action when called.
An event that starts an automation workflow.
The process of proving identity and permissions to access protected resources.
A blog entry published on a site.
Use Outgrow prompts to draft blog content and publish via the Blogs API to streamline content creation.
Pull reader engagement data back into Outgrow to tailor quizzes and CTAs.
Validate and generate SEO-friendly slugs using GET /blogs/posts/url-slug-exists before publishing.
Create or select your Blogs API connection in Outgrow and paste your API token to authorize.
Map Outgrow fields like title, content, and author to the Blogs API endpoints.
Run test calls, verify responses, and enable automated publishing rules.
No extensive coding is required. The Outgrow connector provides a no-code interface to map fields and set up workflows. You can connect and configure in minutes. For advanced use, you can add simple conditional logic using triggers.
The available endpoints cover blog creation, updating, slug checks, and retrieving categories and authors. You can publish posts with /blogs/posts, update with PUT /blogs/posts/:postId, and fetch categories/authors with GET /blogs/categories and GET /blogs/authors.
Authentication is handled via API tokens. Generate a token in the Blogs API dashboard and supply it in the Authorization header for each request. Rotate tokens regularly for security.
Yes. You can automate publishing from Outgrow by triggering post creation when content is approved, then schedule or publish immediately via the Blogs API.
Test the connection by running sample requests in the Outgrow connector. Validate responses, then enable live automation once the tests pass.
Yes, encryption in transit and token-based authentication helps secure data. Follow best practices and limit scopes to only what’s needed.
You can map custom fields like slug, tags, and metadata. The endpoints support updating title, content, and metadata as part of your automation.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
