Resources · Zapier integration

Microsoft Dynamics 365 CRM Zapier integrationAutomate Microsoft Dynamics 365 CRM with Zapier.

The Microsoft Dynamics 365 CRM Zapier integration gives you 16 triggers, 20 actions and 10 searches. Leads, contacts, accounts, cases, orders and invoices can start a Zap, be created or updated by one, or be looked up along the way.

Premium app Zapier reserves this app to its paid plans.

See the 46 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Microsoft Dynamics 365 CRM Zapier integration does for you

Microsoft Dynamics 365 CRM holds your leads, accounts, deals and support cases. Through Zapier it plugs into a Zap: the automation that runs every time an event happens in one app and makes something happen in another. New or changed records in Dynamics can set things off elsewhere, and your other apps can write straight into the CRM without anyone copying fields by hand.

New leads announced where your team works. New Lead starts a Zap each time a lead is created, and the next step posts it in your team chat so nobody has to refresh the CRM.

Cases opened from outside the CRM. A message comes in through your form tool, and Create Case/Incident opens the case in Dynamics, with Find Contact placed before it to attach the right person.

Records kept in step. When an invoice changes in your billing tool, Find Invoice locates it in Dynamics and Update Invoice writes the change, because every update action needs the ID of the record it touches.

What Zapier does not do here: none of the 16 triggers is instant. Zapier checks Dynamics on a timer, so a Zap never fires the moment a record changes. The app is also premium, so even a two-step Zap needs a paid plan. For anything the listed operations do not cover, the API Request (Beta) action sends a raw request with your connection, which is technical ground.

Running Dynamics with n8n instead? See our Microsoft Dynamics 365 CRM n8n integration page.

Vocabulary

Zapier words in one minute

Eight terms come back all over this page. One plain line each.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Dynamics 365 has 16, from a new lead to an updated quote.
Action
What the Zap does once started: the step that creates, updates or sends something. Dynamics 365 has 20.
Task
The unit Zapier bills: one action completed successfully. A trigger never costs one, however often it checks.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. All 16 Dynamics triggers work this way.
Search step
A step that looks up a record that already exists, so the steps after it can use what it found, such as its ID.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Premium app
An app Zapier keeps for paid plans and free trials. Dynamics 365 CRM is one, so the free plan cannot use it.
Cost

What a Dynamics 365 Zap really costs

Microsoft Dynamics 365 CRM is a premium app on Zapier: it needs a paid plan, or a free trial.

  • Premium appYes, paid plan or trial
  • Triggers16, all polling
  • BilledEach successful action
  • Not billedTriggers, checks, failed actions

The trigger never costs a task, however often Zapier checks Dynamics. Each action that succeeds counts as one task, and a failed one is not counted. A Zap that creates a case and then updates the contact uses two tasks per run. Adding a filter or a search step makes it a multi-step Zap, which a paid plan covers anyway here. The grid below gives the polling interval per plan; the Free line is there for reference only, since this app is not available on it.

Connect

Connect Microsoft Dynamics 365 CRM to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your Dynamics account linked to Zapier once, then reused by every Dynamics step in your Zaps.

  2. 02

    Find Microsoft Dynamics 365 CRM

    Search for Microsoft Dynamics 365 CRM in the dialog, pick it from the results, then click Add connection. A new tab opens, and that is where you finish linking the account.

  3. 03

    Sign in and grant access

    Sign in to Dynamics in that tab and grant Zapier access. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Zap: new cases posted to your team chat

GoalWhen a new case is created in Dynamics 365, keep only the cases that meet your condition, then post a message in your team chat.

  1. 01

    Create the Zap with New Case/Incident

    Start a new Zap, pick Microsoft Dynamics 365 CRM and the New Case/Incident event, then select your Dynamics connection when asked.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent cases of the connected account. Pick a real one so the mapping uses true data.

  3. 03

    Add the filter

    Click the plus icon, add Filter and fill the field, the rule and the value. Use a text rule on a text field, or it never passes. A filter makes the Zap multi-step, which needs a paid plan, already required by this app.

  4. 04

    Add the chat message

    Add your team chat app as the action and map the case details you picked at test into the message, so the team reads them without opening Dynamics.

  5. 05

    Test, then publish

    Test each step and read what came back before going further. When the message looks right, click Publish to switch the Zap on.

Triggers

The 16 Microsoft Dynamics 365 CRM triggers

16 events start a Zap when something happens in Microsoft Dynamics 365 CRM. Zapier checks for them at the interval your plan allows.

1

New Account

Polling trigger

In Zapier“Triggers when a new account is created.”

Starts the Zap each time an account is created in Dynamics 365, so the company record can travel to your other tools without retyping.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
your billing or project tool needs a matching company each time sales creates one in the CRM.
Watch out
accounts created before the Zap was published are not picked up.
2

Updated Account

Polling trigger

In Zapier“Triggers when an account is updated.”

Watches existing accounts and starts a Zap when one of them is changed, which keeps copies of company data elsewhere honest.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a change on an account has to reach the copy of that company kept in another app.
Watch out
as a general precaution, a Zap that writes into the place its own trigger watches can set itself off again.
3

New Contact

Polling trigger

In Zapier“Triggers when a new contact is created.”

Fires for every contact added to the CRM, the starting point for welcome messages or mailing list sign-ups in other apps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
each new contact should land in your email tool with the right list attached.
Watch out
a large import of contacts can be held back by Zapier's flood protection.
4

Updated Contact

Polling trigger

In Zapier“Triggers when a contact is updated.”

Reacts when a contact record changes in Dynamics 365, and hands the new version to your next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a contact edited in the CRM has to be edited the same way in another tool that stores it.
Watch out
add a filter if only some changes matter, since every update starts the Zap.
5

New Custom Entity

Polling trigger

In Zapier“Triggers when a new custom entity is created.”

Covers the record types your organisation added to Dynamics on top of the standard ones, and starts the Zap when a new one is created.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
your team tracks something specific, such as a custom record type, and wants it mirrored elsewhere.
Watch out
the Custom Entity field is required: you name the entity to watch.
6

New Case/Incident

Polling trigger

In Zapier“Triggers when a new case/incident is created.”

Opens a Zap when a support case is logged in the CRM, which is how a new issue reaches people who never open Dynamics.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
the support channel in your team chat should see each case as it is logged.
Watch out
the check is on a timer, so a case can sit a little before the Zap notices it, depending on your plan.
7

Updated Case/Incident

Polling trigger

In Zapier“Triggers when a case/incident has been updated.”

Follows cases after they are opened: each change to one starts the Zap with the latest version of the record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
the person who reported an issue should hear when its case moves forward.
Watch out
a filter on the field you care about keeps minor edits from sending messages.
8

New Invoice

Polling trigger

In Zapier“Triggers when a new invoice is created.”

Picks up every invoice created in Dynamics 365 and passes it on, ready for accounting or reporting tools.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
finance keeps a spreadsheet of issued invoices and wants a row for each one.
Watch out
invoices issued before the Zap was published stay out; moving that history is a separate job.
9

Updated Invoice

Polling trigger

In Zapier“Triggers when an invoice is updated.”

Notices when an existing invoice is modified and sends the changed record down the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a status change on an invoice should update the matching line in your accounting sheet.
Watch out
what a single edit sends down the Zap is something to check at test, before you map fields.
10

New Lead

Polling trigger

In Zapier“Triggers when a new lead is created.”

The trigger most teams start with: a lead is created in the CRM, and the Zap takes it from there.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
sales wants each new lead announced in chat or copied into a follow-up sheet.
Watch out
testing brings back the three most recent leads; pick a complete one before you map fields.
11

Updated Lead

Polling trigger

In Zapier“Triggers when a lead has been updated.”

Starts a Zap when a lead already in Dynamics is edited, so its new state can be acted on elsewhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a change on a lead should create follow-up work in another app.
Watch out
a filter in its generic form, field, rule, value, lets only the changes you care about go on.
12

New Opportunity

Polling trigger

In Zapier“Triggers when a new opportunity is created.”

Fires when a deal is opened in Dynamics 365 and hands the new deal to your next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
management tracks the pipeline in a spreadsheet and wants a row per new deal.
Watch out
a bulk import of old deals can trip Zapier's flood protection.
13

Updated Opportunity

Polling trigger

In Zapier“Triggers when an opportunity has been updated.”

Watches deals in progress and starts the Zap whenever one of them is updated.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
an updated deal should lead to the next record in the chain, such as an order.
Watch out
add a filter (field, rule, value) if only some updates should go on.
14

New Order

Polling trigger

In Zapier“Triggers when a new order is created.”

Catches each order created in the CRM and sends it on to the tools that prepare, ship or invoice it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
your operations team works from a sheet and needs one line per new order.
Watch out
the same order does not start the Zap twice, since Zapier tracks what it has already seen.
15

Updated Order

Polling trigger

In Zapier“Triggers when an order is updated.”

Reacts to changes on existing orders, so the people downstream see the latest version rather than the first one.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a change on an order has to reach the team or tool that works from it.
Watch out
an order edited several times means several runs, so filter on the change that matters.
16

Updated Quote

Polling trigger

In Zapier“Triggers when a quote is updated.”

The only quote trigger in the list: it fires when a quote is changed, not when one is created.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a revised quote should be flagged to the account manager in chat.
Watch out
there is no new-quote trigger and no quote action, so quotes can only start a Zap through their updates.
Actions

The 20 Microsoft Dynamics 365 CRM actions

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

1

Create Account

Action

In Zapier“Creates a new account.”

Adds a company to Dynamics 365 from data held in another app.

When to use it
a new customer recorded in another app should become an account in the CRM.
Watch out
run Find Account first if the company may already exist, to avoid duplicates.
2

Create Campaign

Action

In Zapier“Creates a new campaign.”

Sets up a campaign record in the CRM from the tool where you plan your marketing.

When to use it
each campaign planned in your calendar should exist in Dynamics before responses come in.
Watch out
use Find Campaign first if the name might already be taken.
3

Create Contact

Action

In Zapier“Creates a new contact.”

Creates a person record in the CRM with the details your earlier step collected.

When to use it
every new form entry should exist as a contact.
Watch out
the find-or-create version of Find Contact does the same job while avoiding a second copy.
4

Create Campaign Response

Action

In Zapier“Creates a new campaign response.”

Logs a response to a campaign, the trace that someone reacted to it.

When to use it
a reply to your email campaign should count as a response on the matching campaign.
Watch out
Find Campaign can bring the campaign's details in the step just before.
5

Create Case/Incident

Action

In Zapier“Creates a new case/incident.”

Opens a support case in Dynamics 365 from a message or form received in another app.

When to use it
issues reported through your help form should be tracked as cases.
Watch out
the Customer type field is required, so decide which kind of customer the case belongs to.
6

Create Custom Entity

Action

In Zapier“Creates a new custom entity.”

Creates a record in one of the custom types your organisation added to Dynamics 365.

When to use it
your company tracks a specific record type and wants new ones created from another app.
Watch out
the Custom Entity field is required, so name the entity before mapping anything else.
7

Create Invoice

Action

In Zapier“Creates a new invoice.”

Writes a new invoice into the CRM so sales and finance share the same record.

When to use it
an invoice issued in your accounting tool should also appear on the customer's record in Dynamics.
Watch out
check the result at test before publishing, since an invoice is not something to create twice.
8

Create Lead

Action

In Zapier“Creates a new lead.”

Turns an inbound request from another tool into a lead inside Dynamics 365.

When to use it
requests from your website form should reach sales as leads, not as emails.
Watch out
run Find Lead first, or its find-or-create version, if the person may already be a lead.
9

Create Opportunity

Action

In Zapier“Creates a new opportunity.”

Opens a new deal in the CRM, ready for the sales team to work on.

When to use it
an event recorded in another app should open a deal in the CRM.
Watch out
check at test which fields the step asks for before you map anything.
10

Create Order

Action

In Zapier“Creates a new order.”

Records an order in Dynamics 365 from a purchase made elsewhere.

When to use it
a sale recorded in another tool should exist as an order in the CRM.
Watch out
map the customer carefully and read the test result before publishing.
11

Update Account

Action

In Zapier“Updates an account.”

Changes the details of a company that already exists in the CRM.

When to use it
an address corrected in your billing tool should be corrected in Dynamics too.
Watch out
the Account field asks for the account's ID; get it from a trigger or from Find Account.
12

Update Campaign Response

Action

In Zapier“Updates an existing campaign response.”

Modifies a campaign response that is already logged in the CRM.

When to use it
a respondent who later books a meeting should see their response updated.
Watch out
use Find Campaign Response beforehand to target the right one and get what the update needs.
13

Update Contact

Action

In Zapier“Updates a contact.”

Edits an existing contact with fresher information from another app.

When to use it
someone updates their profile on your site and the CRM should match.
Watch out
the Contact field needs the contact's ID, which Find Contact can supply.
14

Update Custom Entity

Action

In Zapier“Updates a custom entity.”

Changes a record of one of your custom types in Dynamics 365.

When to use it
a custom record has to follow a change made in another system.
Watch out
the Custom Entity Action field is required; check at test what it expects for your entity.
15

Update Case/Incident

Action

In Zapier“Updates a Case/Incident.”

Edits an open case, for example to record progress made in another tool.

When to use it
progress logged in another tool should update the customer's case.
Watch out
the Case/Incident field needs the case ID; no search for cases exists, so it must come from a trigger.
16

Update Invoice

Action

In Zapier“Updates an invoice.”

Changes an invoice already recorded in Dynamics 365.

When to use it
a payment confirmed in your accounting tool should be reflected on the CRM invoice.
Watch out
the Invoice field requires the invoice's ID, which Find Invoice can return.
17

Update Lead

Action

In Zapier“Updates a lead.”

Writes new values onto a lead already in Dynamics 365.

When to use it
a lead who books a call in your scheduler should be marked accordingly.
Watch out
the Lead field requires the lead's ID; Find Lead gets it by email or another field.
18

Update Opportunity

Action

In Zapier“Updates an opportunity.”

Moves an existing deal forward by changing its fields from outside the CRM.

When to use it
a change recorded in another tool should be written onto the deal.
Watch out
the Opportunity field needs the deal's ID, found with Find Opportunity.
19

Update Order

Action

In Zapier“Updates a order.”

Adjusts an order that already exists, keeping the CRM in line with what actually happened.

When to use it
a change recorded in another tool should land on the matching order.
Watch out
the Order field takes the order's ID; fetch it with Find Order.
20

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw HTTP request to Dynamics with your connection's sign-in already attached.

When to use it
you need something none of the other actions covers, and you know the request to send.
Watch out
HTTP Method, URL and Stop on error are required, and the URL must belong to a domain tied to the app.
Searches

The 10 Microsoft Dynamics 365 CRM searches

10 search steps look for data that already exists in Microsoft Dynamics 365 CRM, so a later step can use it.

A search step finds a record that already exists so the next step can use it, most often its ID for an update. Searches sit at the bottom of the action-event list, under SEARCH. Three settings decide what happens when the result is not a clean single match.

1

Find Account

SearchFind or create

In Zapier“Finds an account by name.”

Looks up a company by name and hands its record to the next step.

When to use it
before creating a contact, you want to attach them to the account that already exists.
Watch out
the editor also lists Find or Create Account; it is this same search with the create box ticked.
2

Find Contact

SearchFind or create

In Zapier“Finds a contact by email address or other searchable field.”

Finds a person by email address or another searchable field, the usual way to get a contact ID.

When to use it
an email arrives and you need the matching contact before updating it.
Watch out
Find or Create Contact is this search with the create box ticked, not a separate operation.
3

Find Custom Entity

SearchFind or create

In Zapier“Finds a custom entity give.”

Retrieves a record from one of your custom types so later steps can read or change it.

When to use it
a custom record must be located before Update Custom Entity runs.
Watch out
the Custom Entity field is required; Find or Create Custom Entity is the same search with creation switched on.
4

Find Campaign

Search

In Zapier“Finds a campaign by name.”

Locates a campaign by its name.

When to use it
a response comes in and you need the campaign it belongs to before logging it.
Watch out
there is no find-or-create version here, so a missing campaign has to be created with Create Campaign.
5

Find Campaign Response

Search

In Zapier“Finds a campaign response.”

Brings back a campaign response already logged in the CRM.

When to use it
you want to update a response rather than log a second one for the same person.
Watch out
no find-or-create version exists; decide with the first setting what happens when nothing is found.
6

Find Multiple Leads

Search

In Zapier“Finds all leads that match the search criteria.”

Returns every lead that matches your criteria instead of only the first one.

When to use it
you want to act on all leads from one company, not just one of them.
Watch out
check at test how the matching leads reach the next step before you map them.
7

Find Invoice

SearchFind or create

In Zapier“Finds a invoice by email address or other searchable field.”

Finds an invoice by email address or another searchable field.

When to use it
a payment notice arrives and you need the invoice ID for Update Invoice.
Watch out
Find or Create Invoice is this same search with the create box ticked; check at test what it needs.
8

Find Lead

SearchFind or create

In Zapier“Finds a lead by email address or other searchable field.”

Looks up one lead by email address or another searchable field.

When to use it
a form entry may come from an existing lead, and you want to update rather than duplicate it.
Watch out
Find or Create Lead is this search with creation switched on, which avoids double leads.
9

Find Opportunity

SearchFind or create

In Zapier“Finds an opportunity by subject or other searchable field.”

Finds a deal by its subject or another searchable field.

When to use it
another app sends a deal reference and you need the matching opportunity.
Watch out
Find or Create Opportunity is the same search with the create box ticked; it is not a separate operation.
10

Find Order

SearchFind or create

In Zapier“Finds an order by email address or other searchable field.”

Retrieves an order by email address or another searchable field.

When to use it
a change arrives from another app and must be written onto the right order.
Watch out
Find or Create Order is this search with the create box ticked, so one line covers both.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Dynamics 365 Zap breaks

Zapier links two help articles to this app: one for getting started, and one on the common problems people meet with it.

The cases below come from the required fields and from general Zapier behavior. For anything else, see our Zapier troubleshooting guide.

  • An update without a record ID

    Every Update action requires the ID of the record to change. If no trigger or Find step before it carries that ID, the update has nothing to work on.

  • A search that finds nothing

    By default, a search with no result stops the Zap and skips what depends on it. Switch on the setting to carry on, or tick the create box.

  • A Zap that feeds itself

    As a general precaution, a Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through tasks.

  • A bulk import held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • Old records are not replayed

    A Zap only reacts to what happens after you switch it on. Leads or cases created earlier stay out; moving that backlog is a separate job.

  • The same record twice? No

    On polling triggers, Zapier keeps track of what it has already seen, so the same record does not start the Zap a second time.
Need help

Need help automating Microsoft Dynamics 365 CRM with Zapier?

A person reads every message.

FAQ

Microsoft Dynamics 365 CRM Zapier integration: frequent questions

01Is the Microsoft Dynamics 365 CRM Zapier integration free?
No. Microsoft Dynamics 365 CRM is a premium app on Zapier, reserved for paid plans and free trials. The free plan, with its 100 tasks a month and unlimited two-step Zaps, cannot use it at all. You can try it during a trial, then you need a paid plan. On the plus side, a paid plan also lifts the two-step limit, so filters and search steps come with it. The app page on zapier.com states it too.
02How many tasks does a Dynamics 365 Zap use?
One task per action that succeeds. The trigger is free, and so are Zapier's checks of the CRM, however often they run. A Zap that creates a case and then posts in chat uses two tasks per run. A failed action is not counted. On a busy CRM, multiply your expected records by the number of actions in the Zap. A busy CRM fills a plan faster than a quiet one. Count the actions, not the triggers: whichever of the 16 triggers starts the Zap, it never adds to the bill.
03Does Dynamics 365 work in real time with Zapier?
No. All 16 triggers are polling triggers: Zapier checks Dynamics at a fixed interval set by your plan, every 2 minutes on Professional and every minute on Team and Enterprise. A new lead or case therefore reaches the Zap at the next check, not instantly. On paid plans the check interval can be changed, and a check can also be run by hand from the editor. The app page on zapier.com shows this on each trigger.
04What do you need to connect Microsoft Dynamics 365 CRM to Zapier?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. You connect once from the Apps page of your Zapier account with + Add connection, sign in to Dynamics in the tab that opens and grant access. Every Dynamics step then reuses that connection. Remember the paid plan too, since the app is premium. Then test a trigger to confirm access.
05Why does an Update action in Dynamics 365 fail?
Most often because it has no record ID. Update Account, Update Contact, Update Lead, Update Opportunity, Update Order, Update Invoice and Update Case/Incident each require the ID of the record to change. That ID must come from the trigger or from a search step placed just before, such as Find Contact or Find Order. Cases have no search, so their ID has to come from a case trigger. Run the action test to confirm the ID lands.
06What if the Dynamics 365 operation you want is missing?
First check the Microsoft Dynamics 365 CRM page on zapier.com, which shows the current list of operations. If it is not there, two routes remain inside this integration. A search step with the create box ticked can cover many find-or-create needs. And API Request (Beta) sends a raw request with your connection, provided the URL belongs to a domain tied to the app. That last route is technical: it assumes you know which request to send and how to read what comes back.
07Zapier, Make or n8n for Microsoft Dynamics 365 CRM?
Choose on criteria rather than reputation. On Zapier, the app is premium, so the plan is part of the decision from the first Zap. Every trigger is polling, so the interval of your plan sets how quickly records are picked up. And each successful action is a task, which adds up fast on a busy CRM. Compare those three points with what Make and n8n offer for Dynamics before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations