Microsoft Dynamics CRM n8n integrationAutomate Microsoft Dynamics CRM with n8n.
Where does a CRM write step belong in a workflow? The Microsoft Dynamics CRM n8n integration answers with one resource, Account, and 5 operations on it: create, get, get many, update, delete. Create and update each open 36 optional fields. No trigger node ships with this one.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Microsoft Dynamics CRM n8n integration actually do?
It puts your Dynamics account data inside an n8n workflow, where the other tools already are. n8n is a workflow builder: you chain nodes, each node does one step, and data moves between them as JSON items. The Dynamics node is the step that reads or writes Account records. One resource, 5 operations, and a credential you set up once and pick from a dropdown afterwards.
Take a signup that has to become a real account. New rows land in Google Sheets, a Schedule Trigger reads them on a fixed interval, and account.create writes each company into Dynamics with its Name. Email, phone and website ride along in the optional collection, so nobody retypes them on Monday.
Second pattern: the account digest. account.getAll with Return All switched on walks the API pages and brings back the whole list, or a Query narrows it to the segment worth reading. The result goes to Slack as one message, which is usually enough to kill a weekly meeting.
Third, keeping a record honest. Something shifts upstream, a renewal, a bounced address, a support thread. account.get reads the current state, an IF node decides whether it matters, account.update writes back only the fields that moved, and Gmail sends the confirmation to the owner of the change.
The node ships with one resource and 5 operations. Anything outside that catalog goes through the HTTP Request node, which calls any endpoint of the API and reuses the same credential through predefined authentication. Same credential, same workflow, no second login to manage.
Two things to know before you build. Account ID is required on get, update and delete, so any workflow touching an existing account has to carry that value from an earlier step. And with Return All off, n8n stops at Limit: a partial list looks exactly like a complete one three nodes later. If you are weighing platforms first, the n8n review goes through the trade-offs, and n8n training covers expressions and error handling in more depth.
How do you connect Dynamics CRM to n8n?
- 01
Register an application with Microsoft
Open the Microsoft Application Registration Portal and select Register an application. Give it a name, then under Supported account types pick accounts in any organizational directory plus personal Microsoft accounts. Copy the OAuth Callback URL shown on the n8n credential screen, paste it into Redirect URI, choose Web as the platform, and register. Copy the Application (client) ID into n8n as Client ID.
- 02
Generate a client secret
On the application page, open Certificates & secrets and select New client secret. Describe it, something like
n8n credential, then add it. Copy the string in the Value column, not the identifier next to it, and paste it into n8n as Client Secret. Select Connect my account, sign in to the Microsoft account, and allow the app to access your info. OAuth2 is the supported authentication method here. - 03
Check the prerequisites, then reuse the credential
Three things have to be true: a Microsoft Azure account exists, at least one user account has access to the service, and if a corporate Microsoft Entra account manages that user, an administrator has enabled the option letting users consent to apps accessing company data on their behalf. Once the credential is saved under Credentials in n8n, every workflow offers it in the node dropdown. You create it once.
What can the Microsoft Dynamics CRM node do?
The Microsoft Dynamics CRM node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Account
5 operationsCreate an account
account.createWhat you see in n8n
Notes & use cases
Writes a new account into Dynamics. One field is required, and everything else rides along in an optional collection.
Key parameters
- Name: required, the company or business name. From an earlier node it reads as an expression,
{{ $json.field }}, which n8n resolves at runtime. - Additional Fields: 36 optional fields, among them Email Address 1 (the primary email address for the account), Telephone 1 (the main phone number) and Website URL.
- Return Field Names or IDs: the fields the response will include, chosen from the list or set with an expression.
Delete an account
account.deleteWhat you see in n8n
Notes & use cases
Removes an account from Dynamics. It takes a single input and nothing else, which makes it the easiest node in a workflow to fire by accident.
Key parameters
- Account ID: required, the identifier of the account to remove. Carry it from whichever step found the record, usually as an expression such as
{{ $json.field }}.
Get an account
account.getWhat you see in n8n
Notes & use cases
Reads a single account and hands it to the next node. This is how a workflow checks the current state before it decides anything.
Key parameters
- Account ID: required, the account to read, most often supplied by the previous step through an expression like
{{ $json.field }}. - Return Field Names or IDs: choose the fields from the list, or specify IDs with an expression.
Get many accounts
account.getAllWhat you see in n8n
Notes & use cases
Pulls accounts out of Dynamics in a single node, which is where exports, reports and syncs start.
Key parameters
- Return All: on, n8n chains the API pages and brings back every account; off, Limit caps the number of results returned.
- Query: a query that filters the results, for when you want one segment rather than the whole base.
- Return Field Names or IDs: pick the fields from the list, or specify IDs with an expression.
Update an account
account.updateWhat you see in n8n
Notes & use cases
Changes an account that already exists. The node sends the fields you add to the Update Fields collection, and nothing you leave out.
Key parameters
- Account ID: required, the account to modify, typically an expression like
{{ $json.field }}from the step just before. - Update Fields: the same 36 fields as create, including Credit Limit (a useful reference when you address invoicing and accounting issues with the customer), Number Of Employees and Industry Name or ID.
Need help automating Microsoft Dynamics CRM with n8n?
A person reads every message.
Questions people ask next
01Is the Microsoft Dynamics CRM n8n integration free?
02What credentials does the Dynamics CRM node need?
03What are the limits of the Dynamics CRM node in n8n?
04Can n8n react to a new account in Dynamics in real time?
05n8n or Make for Microsoft Dynamics CRM?
Get our weekly integration tips.
No spam. Unsubscribe anytime.
