Obtain an API key from the Blogs API console, grant Privyr the requested scope emails/builder.readonly and blog related permissions, then store the credentials securely in Privyr.
In Privyr, create or select the Blogs API integration and paste the API key. If using OAuth, complete the authorization flow as prompted and confirm permissions.
Key endpoints include: GET emails/builder, POST emails/builder, GET emails/schedule, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, POST blogs/post-update.write, GET /blogs/categories, GET /blogs/authors, GET /blogs/categories, GET /blogs/posts, GET /blogs/authors, GET /blogs/posts, GET /blogs/check-slug/readonly, GET emails/builder, POST /emails/builder/data.
When a new blog post is published in Blogs API, Privyr can trigger a workflow to notify teams, create or update a contact, and push post details to the CRM.
Actions include creating or updating contacts, adding a post reference, and sending a notification via email or chat.
Common method paths include POST /blogs/posts to publish, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to check slug availability.
Key fields to pass include postId, title, slug, author, and publishedAt.
Schedule a regular pull from Blogs API to sync new posts and updates into Privyr at defined intervals.
Actions include updating lead records, posting summaries to conversations, and triggering alerts for new content.
Examples: GET /blogs/posts, GET /blogs/categories, GET /blogs/authors
Key fields: postId, category, author, publishedAt.
Privyr users can look up posts by slug or title to pull content into messages in real time.
Actions: fetch content, display excerpts, attach links, or draft messages.
Examples: GET /blogs/posts/url-slug-exists to verify, GET /blogs/posts to fetch by slug.
Key fields: slug, postId, title.
Fully no code integration between Privyr and Blogs API.
Faster go live with drag and drop flows.
Centralized data and consistent messaging across Privyr and Blogs API.
Understand the core elements: endpoints, triggers, actions, authentication and data mapping. The processes include setting up scopes, mapping fields, testing, and monitoring data flows.
A blog article that can be created, updated, or retrieved via the API.
A URL friendly identifier used to fetch a post or check its existence.
A defined URL path that performs an action or returns data via the API.
The process to prove identity to the API, typically via API keys or tokens.
Trigger alerts in Privyr when a new post is published, including the post title and a link.
Fetch a brief summary and attach it to Privyr messages for faster responses.
Use slug existence to route posts to specific campaigns or customer journeys.
Create API credentials in the Blogs API console and paste them into Privyr with proper scope for emails and posts.
Select endpoints from the list and map fields like postId and slug to Privyr fields.
Run tests, validate triggers, and go live with monitoring and alerts.
No coding is required for the basic Privyr and Blogs API connection. Privyr provides a no code bridge that lets you select endpoints, set scopes, and map fields using a guided UI. This keeps setup accessible for non developers. You can test a simple trigger to verify the flow without writing code. For advanced users, optional custom fields and payload shaping are available.
Essential endpoints usually include retrieving posts, checking slug existence, and publishing or updating posts. For a basic flow you might use GET /blogs/posts, GET /blogs/posts/url-slug-exists, and POST /blogs/posts. You can gradually add scheduling for updates and additional endpoints as needed.
The integration uses API keys or OAuth tokens to authenticate requests. Use least privilege scopes such as emails/builder.readonly and blogs basic read write scopes. Privyr stores tokens securely and provides rotation options. Regularly rotate credentials and monitor access logs for unusual activity.
Yes. Privyr workflows support test mode and sandbox credentials. Use test data and mock endpoints to validate triggers, mappings, and actions before going live. This minimizes risk to real customer data while you refine your automation.
Field mapping involves aligning Blogs API fields like postId, title, slug, author, and publishedAt with Privyr contact and message fields. Use the Privyr UI to map each field, then run a test to confirm data appears correctly in messages or CRM records.
If you need to disconnect or reconfigure, remove the Blogs API integration from Privyr, revoke API keys if necessary, and re-add with updated credentials. Save changes and re-run tests to ensure the new configuration works as expected.
API credentials are created in the Blogs API console. Store keys securely in Privyr and use the rotate option on a schedule you define. If credentials are compromised, generate new keys, update Privyr immediately, and revoke old tokens.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
