--- title: "Microsoft Dynamics Quick Reference for Intelligent Workflows" slug: "ms-dynamics-quick-reference-for-intelligent-workflows" description: "Use workflows with Microsoft Dynamics for powerful workflows, account creation, and contact management." updated: 2026-05-12T14:58:34Z published: 2026-05-12T14:58:34Z canonical: "support.6sense.com/ms-dynamics-quick-reference-for-intelligent-workflows" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.6sense.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Dynamics Quick Reference for Intelligent Workflows 6sense integration with Microsoft Dynamics gives you powerful orchestration features using Intelligent Workflows. This page covers the basics for new users. ## Integrate 6sense and AI Email with Microsoft Dynamics To use workflows with Microsoft Dynamics, the integration must already exist. The user who sets this up must have permissions on the relevant objects in Microsoft Dynamics. Refer to [Integrate 6sense with Microsoft Dynamics 365](/v1/docs/integrate-6sense-with-microsoft-dynamics-365). If you plan to use a Microsoft Dynamics contact list with AI Email to periodically import and enroll new contacts in an AI Email campaign, there are more integration steps. Refer to [Integrate AI Email with MS Dynamics](/v1/docs/integrate-ai-email-with-dynamics). ## Popular AWF use cases for Microsoft Dynamics Add to a Dynamics campaign over a set period of time, then remove them from the workflow. ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-07 at 6.56.29 PM.png) Create accounts from 6sense in your Microsoft Dynamics and add them to a Dynamics campaign. ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-07 at 6.34.33 PM.png) ## Popular DWF use cases for Microsoft Dynamics Purchase contacts from 6sense and save the contacts to Microsoft Dynamics. ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-10 at 1.07.59 PM.png) ## Decision node condition filters for Microsoft Dynamics When Microsoft Dynamics is integrated with 6sense, you can use its fields in filters for decision nodes. ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-07 at 7.28.06 PM.png) ## Action nodes that support Microsoft Dynamics ### AWF and DWF Create Accounts in CRM node The **Create Accounts in CRM** node, available in both AWF and DWF, creates accounts in Microsoft Dynamics from accounts in 6sense. #### Account identification and duplication rules 6sense identifies accounts by name, country and domain. This means that 6sense considers “XYZCorp, USA” and “XYZCorp, Canada” to be separate accounts. Therefore, if you have one name/country/domain in your CRM, and the new account from 6sense uses another, 6sense creates the other. However, you may want to treat both of these accounts as the same account in your CRM; in which case you can set custom duplicate prevention rules in 6sense so that 6sense does not create a new account if you want to use the existing account. To set up duplication prevention rules, see [Custom Match Rules](/v1/docs/custom-match-rules). #### Create Accounts dependencies for Microsoft Dynamics - Integration with Microsoft Dynamics. - Pre-configured [custom match rules](/v1/docs/custom-match-rules) for account creation, to prevent duplicates. - A pre-configured [mapping profile](/v1/docs/mapping-profiles) that includes the name, display domain, and country fields. - 6sense credits allocated. See [Distribute Credits Between Applications](/v1/docs/distribute-credits-between-applications). #### Create Accounts properties for Microsoft Dynamics Most Create Accounts in Dynamics node are [the same as other Create Accounts in [CRM] nodes](/v1/docs/audience-workflow-action-nodes#properties5). Dynamics-specific properties include: - Make sure you select a **Mapping profile** for your Microsoft Dynamics system. - You can override which fields to enrich when creating an account *for this node only*. - For **Advanced Options**, you can set the batch size per API call. By default, it is 1000 for MS Dynamics. Reducing the batch size may inversely affect the number of API calls. For example, decreasing the batch size from 200 to 50 results in 4x more API calls. The smaller the batch size, the longer the processing times. Changes to this setting take effect the next time the action node runs. ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-07 at 6.47.25 PM.png) ### AWF Push to Dynamics Campaign node The Push to Dynamics Campaign people-level action node pushes contacts or leads from a segment to a Microsoft Dynamics campaign. #### Push to Campaign dependencies for Microsoft Dynamics - A configured Microsoft Dynamics campaign. - A configured Microsoft Dynamics marketing list. #### Push to Campaign properties for Microsoft Dynamics Most Push to Dynamics Campaign node are [the same as other Push to CRM nodes](/v1/docs/audience-workflow-action-nodes#peoplelevel-channel-action-node-properties). ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-07 at 6.37.47 PM.png) Dynamics-specific properties include: - **Destination details**: Select whether to push **Contacts** or **Leads**. - **Push CRM leads/contacts to Dynamics campaign**: Select the name of the Microsoft Dynamics campaign. - **Push CRM leads/contacts to Dynamics marketing list**: Select the name of the Microsoft Dynamics marketing list. - **Advanced Options**: - **Batch size (1000)**: The Batch Size per API call. The smaller the batch size, the more time it takes to run the workflow. ### AWF and DWF Purchase Contacts and Save to Dynamics CRM nodes A workflow can purchase contacts from 6sense and save them to Microsoft Dynamics. Purchases use [6sense credits](/v1/docs/credits-overview). #### Purchase Contacts node The Purchase Contact node allows you to purchase contacts from 6sense. *You must connect a Save Purchased Contacts to Dynamics CRM node to this node*, to ensure that these purchased contacts are saved. **Purchase Contacts dependencies for Microsoft Dynamics** - Integration with Microsoft Dynamics. - 6sense credits allocated. See [Distribute Credits Between Applications](https://support.6sense.com/v1/docs/distribute-credits-between-applications). - The Predictive add-on is required for: - Using the optional **Records match persona map** property. - Using certain filter conditions - A timer node is not allowed in-between the Purchase Contacts and Save Purchased Contacts… node. - In Data Workflows, Purchase Contacts nodes are only accessible in workflows that start from a: - Segment - Account - Must be followed in a workflow by a Save Purchased Contacts node. **Purchase Contacts properties for Microsoft Dynamics** Purchase Contacts properties for Microsoft Dynamics are the same as for other CRMs. Refer to [Audience Workflows Action Nodes](/v1/docs/audience-workflow-action-nodes#properties). ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-10 at 1.17.27 PM.png) #### Save Purchased Contacts to Dynamics CRM node The Save Purchased Contacts node must directly follow the Purchase Contacts node. **Save Purchased Contacts dependencies for Microsoft Dynamics** - Integration with Microsoft Dynamics. - A pre-configured [mapping profile](https://support.6sense.com/v1/docs/mapping-profiles). - Must be preceded in a workflow by a Purchase Contacts node. **Save Purchased Contacts properties for Microsoft Dynamics** Save Purchased Contacts properties for Microsoft Dynamics are the same as other CRMs. Refer to [Audience Workflows Action Nodes](/v1/docs/audience-workflow-action-nodes#save-purchased-contacts-to-crm-map-andor-csv-nodes). ![](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Screenshot 2026-04-10 at 1.36.44 PM.png) ## AWF and DWF templates All templates that use CRM nodes support Microsoft Dynamics as the CRM. ***Document changelog*** May 12 2026: First published Application Programming Interface; a set of rules that allows different software applications to communicate with each other.