Use the API key and token provided in your Blogs API dashboard to authorize requests. Store credentials securely and rotate them regularly.
Authorize Experience-com to access your Blogs API data using the configured OAuth or API key pairing. Keep tokens confidential.
Key endpoints: GET emails/builder; GET emails/schedule; POST emails/builder/data; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; GET /blogs/categories; GET /blogs/authors.
Trigger: New or drafted post in Experience-com triggers a publish or update in Blogs API.
Actions: Use POST /blogs/posts to create content, PUT /blogs/posts/:postId to update, and use the slug check when necessary.
Methods: POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists to validate slugs.
Key fields: title, content, slug, category, author, status
Trigger: schedule or on demand to refresh category and author data in Experience-com.
Actions: GET /blogs/categories and GET /blogs/authors to pull metadata for filters and display.
Methods: GET /blogs/categories; GET /blogs/authors
Fields: id, name, slug
Trigger: schedule based publishing in Blogs API.
Actions: Use POST /blogs/posts to schedule content and POST /emails/builder/data to notify teams when a post goes live.
Methods: POST /blogs/posts; POST /emails/builder/data
Fields: postId, scheduledTime, notifyList
No-code content automation: create, edit, and publish posts without writing code.
Unified automation: combine blog actions and email notifications in one workflow.
Real-time data sync for categories and authors to keep experiences fresh.
Key elements and processes used in this integration include endpoints for blogs, email templates, scheduling, and data mapping between Blogs API and Experience-com.
A URL path for accessing a specific resource in the REST API.
A URL-friendly identifier for a blog post.
HTTP method used to create or update resources.
An event that starts a sequence of actions in a connected app.
Automatically compile a weekly roundup post from top categories and authors and publish.
Notify subscribers when a new post goes live using Email Builder.
Use templates to generate posts from data like title, slug, and summary.
Obtain your API key for Blogs API and verify access to endpoints such as GET /blogs/categories.
Map Experience-com fields to Blogs API fields like title, content, slug, category, and author.
Create a test workflow that creates a post via POST /blogs/posts and notifies the team when it goes live.
To authenticate, use the API key and token with your requests. Include the key in the Authorization header and scope to emails/builder.readonly for read actions and blogs/post-update.write for updates. If using a separate OAuth flow, follow the provider’s steps to obtain a token and refresh it as needed. Test endpoints like GET /blogs/categories to confirm access.
Essential endpoints for publishing posts include POST /blogs/posts to create content, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to validate slugs. You may also use GET /blogs/categories and GET /blogs/authors to enrich posts with metadata.
Yes, you can fetch categories and authors in separate calls or with parallel requests in a workflow. Use GET /blogs/categories for the list of categories and GET /blogs/authors for author data.
Required fields for creating a post typically include title, content, slug, and at least one category or author. Use the slug check endpoint to avoid duplicates.
Scheduling posts involves setting a publish date in the post payload and, if needed, a separate notification step using the Email Builder. The workflow can trigger email alerts when a post goes live.
No code is not strictly required. This integration is designed for no code connectors like the Apps that orchestrate Actions and Triggers. You can automate many tasks without writing code.
For terminology, see the glossary terms below which define endpoints, slugs, and workflows used in this integration.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
