Authenticate your Blogs API connection using an API key with read/write access. In most setups you’ll grant endpoints under blogs/* and posts, and verify the required scope for your environment.
Connect Pendo Feedback using your credentials in the Zapier app connector, enabling triggers from feedback to call Blogs API.
GET emails/builder – Read email templates; POST emails/builder – Create email templates; POST /emails/builder/data – Attach data to email templates; DELETE /emails/builder/:locationId/:templateId – Remove a template; GET emails/schedule – Read email schedules; GET /blogs/categories – Retrieve blog categories; GET /blogs/authors – Retrieve blog authors; GET /blogs/posts/url-slug-exists – Check if a blog slug exists; POST /blogs/posts – Create a blog post; PUT /blogs/posts/:postId – Update a blog post;
Trigger: when a new feedback submission is created in Pendo Feedback
Actions: create a new blog post in Blogs API using the feedback data for title and content; assign author and category; publish instantly or on a schedule
POST /blogs/posts
title, content, author, category, slug, tags, published_at
Trigger: when a feedback item is updated in Pendo Feedback
Actions: update blog post via PUT /blogs/posts/:postId with new title, content or tags
PUT /blogs/posts/:postId
postId, title, content, tags
Trigger: when a feedback item is deleted in Pendo Feedback
Actions: delete blog post via DELETE /blogs/posts/:postId
DELETE /blogs/posts/:postId
postId
Rapid automation without coding to publish blog content from feedback data
Time savings by eliminating manual post creation and updates
Consistent content structure and streamlined publishing workflows
Key elements and processes you’ll encounter when connecting APIs: endpoints, triggers, actions, and data fields.
An application programming interface that enables software components to communicate.
An HTTP method used to create a new resource on the server.
A specific URL path for a resource in an API.
The process of verifying identity to access APIs.
Automatically generate a weekly blog post from recent feedback insights and publish via Blogs API.
Publish author bios and contributor spotlights when new feedback contributors join a project.
Link feature requests in Pendo Feedback to product update posts in Blogs API.
Connect both services in your integration tool, selecting the proper scopes and permissions for Blogs API and Pendo Feedback.
Match blog post fields to feedback data fields like title, content, author, and category.
Run tests to verify post creation and updates; then deploy to production.
No coding is required for a basic connection. Use a no-code automation tool to set up triggers from Pendo Feedback to create blog posts in Blogs API. For advanced flows, you can add custom scripts or webhooks as needed. Always start with a sandbox environment to validate data mappings.
You’ll typically use POST /blogs/posts to create new posts, GET /blogs/posts/url-slug-exists to check slugs, and PUT /blogs/posts/:postId to update existing content. Additional endpoints like GET /blogs/categories and GET /blogs/authors help you enrich posts with taxonomy and author data.
Authenticate via API keys or OAuth depending on your provider. In Zapier, connect Blogs API with the key or token, and ensure the connection scope includes posts and categories. For Pendo Feedback, use your own credentials or the app’s connection.
Yes. When a feedback item changes, trigger an update to the corresponding blog post using PUT /blogs/posts/:postId and re-publish if needed. Make sure to preserve post IDs to maintain link integrity.
Deleting a feedback item can trigger a post deletion if you map the delete action. Use DELETE /blogs/posts/:postId to remove the associated blog post from your site. Consider archiving instead of hard delete for safety.
Test in a staging environment, review error messages, and monitor the workflow logs. Look for rate limits, authentication failures, and field validation errors. Implement retries and backoff where appropriate.
Consult the integration tool’s documentation and the API provider’s references. Check endpoint availability, request limits, and required fields. If issues persist, reach out to support teams for guided troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
