Resources · Make integration

Microsoft Dynamics 365 - CRM Make integrationAutomate Microsoft Dynamics 365 - CRM with Make.

Can Make keep your Dynamics records in step with the rest of your stack? The Microsoft Dynamics 365 - CRM Make integration gives you 9 modules: 1 trigger, 7 actions and 1 search. This guide shows sales and ops teams how to connect the account and build a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Microsoft Dynamics 365 - CRM integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft Dynamics 365 - CRM Make integration do?

The Microsoft Dynamics 365 - CRM Make integration lets a Make scenario, the automation you build as a chain of modules, read and write your CRM records without code. It can spot new records, look records up, create them, change them and remove them, then pass each one to any other app you connect.

A CRM that updates itself when a deal moves elsewhere. When a quote gets signed in another tool, Search Records finds the matching account and Update a Record writes the new status on it. Nobody retypes anything, and the sales rep sees the change in Dynamics.

New records announced to the right people. Watch Records picks up each record created in Dynamics, and the next module posts it to a team chat or adds a row to a shared sheet. Support hears about a new customer without opening the CRM.

Clean data before it piles up. Search Records lists the records that match a condition, and Delete a Record removes the ones you truly no longer need. Try it on one record first, and treat every delete as final.

Two limits to know before you start. The app is reserved to the Make Enterprise plan, so a Free account will not run it; the Make pricing page explains the plans. And the connection asks for an app registration in Azure, which usually means an admin. If you are still weighing tools, the n8n vs Make comparison lays out both, and the Make training helps you get fluent in the editor.

Connect

How do you connect Microsoft Dynamics 365 - CRM to Make?

  1. 01

    Register an app in Azure

    In the Azure Portal, open Azure Active Directory and copy the Tenant ID. Then go to Applications, click New Registration, give the app a name, pick the account type, choose Web as the platform with the redirect URI from the Make doc, and click Register.

  2. 02

    Create a secret and grant permissions

    On the app screen, note the Client ID. Click Add a certificate or secret, then New client secret, pick an expiry and click Add; copy the value right away. Under API Permissions, add Dynamics CRM and click Grant Admin consent for your organization.

  3. 03

    Add the connection in Make

    In your scenario, add a Microsoft Dynamics 365 - CRM module and click Add next to the Connection field. Fill in the details you saved from Azure, click Save, then Accept to confirm the dialog. That connection, your CRM account linked to Make, now serves every module of the app.

First scenario

Your first scenario with Microsoft Dynamics 365 - CRM

GoalWhen another app sends new information about a customer, Make finds that customer in Dynamics and updates the record.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where the customer news comes from: a form tool, a signing tool, a spreadsheet.

  2. 02

    Find the customer with Search Records

    Click the + on the right of that module and add Search Records from Microsoft Dynamics 365 - CRM. Click Add to create the connection, then map the value that identifies the customer from the first module.

  3. 03

    Change it with Update a Record

    Add Update a Record after the search. Map the record returned by Search Records, then map the new values from the first module into the fields you want to change. Each record found becomes one bundle, one item passed along the chain.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the first app. Open the bubbles above each module to read the bundles it received, and check in Dynamics that the right record changed.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What can start a Microsoft Dynamics 365 - CRM scenario?

1 module starts a scenario when something happens in Microsoft Dynamics 365 - CRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Microsoft Dynamics 365 - CRM as soon as it happens.

Microsoft Dynamics 365 - CRM1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a new record has been created.”

Watch Records hands your scenario every record newly created in Dynamics, one bundle per record, so the rest of the chain can react to each fresh entry without anyone exporting a list. It is the only trigger of the app, and it looks at creations, not at edits.

How it fires
scheduled. Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
a new customer record should reach another team or tool, like a welcome sequence or a support workspace.
Watch out
a record changed later will not wake it up; to follow changes, pair Search Records with a schedule instead.
Modules

What can Make do in Microsoft Dynamics 365 - CRM?

Microsoft Dynamics 365 - CRM gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft Dynamics 365 - CRM1

Create a Record

Action

In Make“Creates a new record.”

Create a Record adds a brand new entry to Dynamics from data that arrives in the scenario, so a lead captured elsewhere lands in the CRM with no copy and paste.

When to use it
a web form, an event sign-up or an import sheet brings in people who do not exist in the CRM yet.
Watch out
the doc says nothing about duplicate checks, so run Search Records first whenever the person might already be in the CRM.
Microsoft Dynamics 365 - CRM2

Delete a Record

Action

In Make“Deletes an existing record.”

Delete a Record removes one existing entry from Dynamics, which keeps the CRM free of test entries, spam leads or records your team decided to drop.

When to use it
a cleanup scenario where Search Records has already isolated exactly the records to remove.
Watch out
the doc offers no way to restore a deleted record, so test on a single record with Run once before letting it loose on a whole search result.
Microsoft Dynamics 365 - CRM3

Get a Record

Action

In Make“Retrieves an existing record.”

Get a Record fetches the full content of one entry you already know how to identify, so later modules can use its details in an email, a document or another app.

When to use it
an earlier module gives you the record reference, and you need everything stored on it rather than a list of matches.
Watch out
it reads one record only; when you do not have the reference, Search Records is the right pick.
Microsoft Dynamics 365 - CRM4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Dynamics API through the same connection, which covers the jobs the ready-made modules leave out.

When to use it
you need an operation Dynamics offers but none of the listed modules performs, and your team or developer knows which API request does it.
Watch out
you write the request yourself, so this module suits people comfortable reading API documentation more than first-time builders.
Microsoft Dynamics 365 - CRM5

Update a Record

Action

In Make“Updates an existing record.”

Update a Record changes values on an entry that already exists, so the information your team reads in the CRM stays accurate when something happens outside it.

When to use it
a deal gets signed, a ticket closes or a payment clears in another tool, and the customer record in Dynamics should reflect it.
Watch out
you need the record to target; place Search Records or Get a Record before it to supply that reference.
Microsoft Dynamics 365 - CRM6

Search Records

Search

In Make“Searches for records or lists them all.”

Search Records finds the entries that match what you ask for, or lists them all, and sends each result on as its own bundle for the next module.

When to use it
checking whether a contact already exists before creating one, or pulling the set of records a cleanup or report should cover.
Watch out
it can return zero, one or many records, and every module after it runs once per result, which multiplies operations.
Microsoft Dynamics 365 - CRM7

Records

ActionIn the docs only

Records appears in the Make directory as an action of this app, but neither the directory nor the doc describes what it does, so its exact behavior is not documented.

When to use it
only after opening it in the editor and reading the fields it asks for, when none of the described modules fits your case.
Watch out
test it with Run once on harmless data before trusting it in a live scenario.
Microsoft Dynamics 365 - CRM8

Other

ActionIn the docs only

Other is listed as an action of the app with no official description, which leaves its purpose unclear from the documentation alone.

When to use it
as a last look before reaching for Make an API Call, once you have checked in the editor what it offers for your records.
Watch out
nothing in the doc tells you what it changes in Dynamics, so a Run once test on a sample record is the safe first step.
Need help

Need help automating Microsoft Dynamics 365 - CRM with Make?

A person reads every message.

FAQ

Questions about the Microsoft Dynamics 365 - CRM Make integration

01Is the Microsoft Dynamics 365 - CRM Make integration free?
No. Make marks Microsoft Dynamics 365 - CRM as an enterprise app, and the doc confirms it is available on the Make Enterprise plan. The Free plan covers the 3,000+ standard apps with 2 active scenarios and a 15 minute minimum between scheduled runs, but enterprise apps stay out of it. On the Enterprise plan, usage is counted in credits, one operation for each module run on a bundle. Make does not publish a price for the app itself, and this page does not quote any.
02What do you need to connect Microsoft Dynamics 365 - CRM to Make?
You need access to the Azure Portal with enough rights to register an application and grant admin consent. The steps are to copy the Tenant ID, register a new app with the Web platform and the redirect URI from the Make doc, create a client secret, then add the Dynamics CRM permission. In Make, click Add next to the Connection field, enter those details, save and accept. If you get a 401 error, the Host URL may end with a slash.
03Does the Microsoft Dynamics 365 - CRM trigger in Make work in real time?
No. Watch Records is a scheduled trigger, marked with the clock badge in the editor. Make checks Dynamics for new records each time the scenario runs, every 15 minutes by default, and paid plans allow an interval down to 1 minute. There is no instant trigger for this app, so Dynamics does not call Make through a webhook. Watch Records also reacts to newly created records only; changes to existing ones need a search on a schedule.
04What if the Microsoft Dynamics 365 - CRM module you need is missing in Make?
It depends on the job, but the app includes Make an API Call, which uses your existing connection to reach any endpoint of the Dynamics API. That covers operations the 9 listed modules leave out, provided you know which request to send. Two modules, Records and Other, have no official description, so open them in the editor before relying on them. If the blocker is the plan rather than a module, remember the app only runs on Make Enterprise.
05Should you use Make or n8n for Microsoft Dynamics 365 - CRM?
It depends on your plan and your team. On Make, this app requires the Enterprise plan, which settles the question for many smaller teams before any feature comparison. n8n often has a node for the same app, so it is worth checking there as well. Beyond that, compare what matters to you: which modules you need, who will build and maintain the scenarios, and how your company already buys software. Neither tool is simply better for every Dynamics setup.
Same platform

Other docs you might need on this stack.

Browse all integrations