To connect Deskpro to Blogs API you’ll need valid credentials. Use an API key or OAuth token granted by Blogs API, then configure the credentials in Deskpro’s integration settings. Keep tokens confidential and rotate them regularly.
Deskpro authenticates with Blogs API by sending your stored credentials with each request. Ensure the integrated app has the required scopes to read and write posts, categories, and authors.
Endpoints covered include: GET emails/builder, GET emails/builder.write, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, emails/schedule.readonly, GET emails/schedule, blogs/post.write, POST /blogs/posts, blogs/post-update.write, PUT /blogs/posts/:postId, blogs/check-slug.readonly, GET /blogs/posts/url-slug-exists, blogs/category.readonly, GET /blogs/categories, blogs/author.readonly, GET /blogs/authors
Trigger: when a new approved Deskpro article or knowledge base item is created, automatically publish a blog post via POST /blogs/posts.
Actions: map Deskpro fields to blog post fields, then call POST /blogs/posts; verify slug with GET /blogs/posts/url-slug-exists; assign categories as needed.
POST /blogs/posts
Required fields: title, content, author, slug, category
Trigger: updates to a Deskpro article trigger a corresponding update to the blog post via PUT /blogs/posts/:postId.
Actions: propagate changes from Deskpro to the blog post fields and push updates via PUT, keeping both in sync.
PUT /blogs/posts/:postId
Fields: postId, title, content, slug
Trigger: schedule posts to publish at predefined times or based on Deskpro status changes.
Actions: schedule posts via Blogs API, update calendars, and notify teams in Deskpro.
POST /blogs/posts
Fields: title, content, scheduleTime, slug
No code content automation: publish from Deskpro without writing code.
Unified content workflows across Deskpro and your blog.
Secure, scalable integration with built in authentication and error handling.
A quick glossary of terms and core processes used in the Deskpro–Blogs API integration to help you implement and troubleshoot.
Application Programming Interface: a set of rules and tools that lets applications talk to each other.
An HTTP method used to create a new resource on the server.
An HTTP method used to retrieve data from the server.
A URL-friendly version of a title used in a blog post URL.
Automatically convert resolved tickets and knowledge articles into fresh blog content to keep readers informed.
Send live publish alerts to Slack, Teams, or Deskpro to keep teams aligned.
Aggregate top Deskpro insights into a weekly blog post to drive steady readership.
In Deskpro, open Integrations, add Blogs API, and generate an API key or OAuth token to authorize calls.
Map Deskpro fields to blog fields (title, content, author, category). Choose endpoints like POST /blogs/posts and GET /blogs/posts/url-slug-exists for slug checks.
Run tests in a staging environment, review logs for errors, then enable live sync.
No coding is required to get started. Use Deskpro’s built in integrations and the Blogs API endpoints to connect and automate workflows. Start with creating an integration, then map fields and choose the endpoints you will use for post creation and updates. The workflow is designed so non developers can set up and run with just a few clicks. If you need more customization, you can extend mappings or add conditional steps without writing code.
The core endpoints you will likely use are POST /blogs/posts to create new blog posts and PUT /blogs/posts/:postId to update existing ones. You can check slug availability with GET /blogs/posts/url-slug-exists and fetch or update related data via GET /blogs/authors, GET /blogs/categories, and GET /blogs/categories. Deskpro field mappings ensure title, content, author, category, and slug align with your blog schema.
Test in a staging environment by triggering a new Deskpro item and verifying a corresponding blog post is created. Review API responses and error logs for authentication or field mapping issues. Use the slug check and sample data to confirm formatting before going live.
Yes. You can schedule posts by including a scheduleTime on create requests to POST /blogs/posts. You can also plan recurring publishing windows and verify the schedule in Blogs API dashboards. Deskpro can notify teams when a post goes live.
Security is handled via standard API credentials, scoped access, and secure storage in Deskpro. Rotate tokens regularly, use least privilege scopes like emails/builder.readonly or blogs/*read only when appropriate, and monitor for unusual activity in your integration logs.
To update existing posts, send a PUT request to /blogs/posts/:postId with the changed fields. Ensure postId is correct and that the fields you update match your blog schema. Persist changes from Deskpro by re-synchronizing field mappings as needed.
Monitor errors in Deskpro’s integration logs and Blogs API dashboards. Enable verbose logging during setup, review authentication errors, and verify field mappings. Set up alerting to notify your team when a failure occurs.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
