Authenticate using API keys or OAuth, then grant the app the necessary scopes to read and write blog content and author data from Blogs API.
Authorize the connector within Microsoft Dynamics 365 CRM to receive and store blog data, using standard OAuth flows and token rotation to keep access secure.
Key endpoints include: GET /blogs/categories; GET /blogs/authors; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/categories; GET /blogs/authors; POST /blogs/posts; GET /blogs/posts; blogs/post.write; blogs/check-slug.readonly.
Trigger when a new blog post is published or updated in Blogs API to create or update a matching post in Microsoft Dynamics 365 CRM.
Create or update CRM blog records by mapping title, slug, content, author, category, and publish date from Blogs API.
POST /blogs/posts
title, content, slug, authorId, categoryIds, publishedDate
Trigger on author creation or update in Blogs API to reflect changes in CRM contacts or related author records.
Create or update CRM author records by mapping name, bio, avatarUrl, and social links from Blogs API.
GET /blogs/authors
id, name, bio, avatarUrl
Trigger on category creation or update in Blogs API to sync CRM category records.
Create or update CRM category records by mapping id, name, and description from Blogs API; attach to related posts.
GET /blogs/categories
id, name, description
Automate data flows and synchronization without writing custom code, reducing manual data entry.
Keep blog content, authors, and categories consistent across your CMS and CRM in real time.
Speed up content-driven campaigns by surfacing CRM-ready data for workflows, segments, and automation.
Key elements include API endpoints, authentication, triggers, actions, and field mappings. The process moves data securely from Blogs API to Dynamics 365 CRM and back as needed.
Application Programming Interface: a defined set of rules that enables software components to communicate and exchange data.
A specific URL exposed by an API that performs a function or returns data.
The process of verifying identity and obtaining access tokens to call protected API routes.
A URL-friendly version of a post title used in links and SEO.
Create a scheduled workflow that pulls a weekly digest from Blogs API and creates a CRM task with links to the posts for your sales and marketing teams.
Automatically tag posts with campaign identifiers and create or update CRM opportunities or campaigns based on post performance metrics.
Sync categories and authors to CRM for smarter segmentation and personalized outreach in campaigns.
Register your Blogs API credentials and establish scopes for posts, authors, and categories; complete the OAuth flow to obtain access tokens.
Define which endpoints to use and map blog fields (title, slug, content, author, category) to Dynamics 365 CRM fields.
Run verification tests, set up error handling and retries, and monitor data flows to ensure accuracy.
No coding is required to start. Use the Blogs API connector to authenticate with OAuth or API keys and configure the required scopes for posts and authors. The setup guides walk you through mapping fields to your CRM. After configuration, you can run a test to verify the flow. If issues arise, enable automated retries and alerts to keep data in sync.
Essential endpoints include creating and updating posts (POST /blogs/posts, PUT /blogs/posts/:postId), checking slug availability (GET /blogs/posts/url-slug-exists), and retrieving authors and categories (GET /blogs/authors, GET /blogs/categories). These enable CRM records to reflect new posts, authors, and categories accurately. You can tailor which endpoints are active based on your workflow.
Authentication uses OAuth with token rotation or API keys. The connector guides you through granting access scopes, securely storing tokens, and refreshing them before expiry. This ensures protected endpoints like blogs/posts and blogs/authors remain accessible only to authorized systems.
Data can be configured for near real-time syncing or batched at scheduled intervals. Real-time delivery is possible for key events, while batching helps manage rate limits and server load. You can adjust the cadence to fit your operational needs.
Yes. You can sync authors and categories by mapping blogs/authors and blogs/categories endpoints to corresponding CRM records or taxonomy fields. This enables consistent segmentation, attribution, and campaign targeting across platforms.
If a call fails, retries are automatically attempted according to the configured policy. You can also set custom alerts for failures, and review error details in the integration logs to diagnose root causes and adjust mappings or endpoint usage as needed.
Mappings are configured in the connector’s field mapping section. You can map post titles, content, slugs, authors, categories, and dates to CRM fields. If your CRM uses custom fields, add those mappings to ensure data lands in the correct place.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
