Dynamics 365 integration

Dynamics 365 lead source, set at submission.

Every Dynamics 365 lead gets a Lead Source option set, and somebody has to pick the option. Lead Source reads the real channel, the entry page and the page path when the buyer submits, and a Zap creates the Dynamics lead with that answer already chosen.

Connects via the Dynamics 365 Zapier connector Creates or updates leads and contacts One line of code
Salesforce
HubSpot
Pipedrive
Gmail
Twilio
Google Ads
Gravity Forms
Jotform
Webflow
Wix
Calendly
Typeform
What Dynamics captures, and what it misses

Dynamics has a Lead Source option set. It holds one option.

In Microsoft Dynamics 365 the lead table and the opportunity table both carry a Lead Source option set. An admin configures the options once and each record gets exactly one of them. For a sales org living on the Microsoft stack, that makes a tidy chart. It also means the field can say Web and stop there, with no campaign, no entry page and no record of which pages the buyer opened first.

What the option set holds

One configured option

  • A single option: Web, Trade show, Partner, Other
  • Picked as the lead is created, by a mapped form or a seller
  • Tidy for a dashboard, blunt for a spend review
What it leaves out

The detail behind the option

  • The campaign or search behind the click
  • The landing page they arrived on
  • The pages they read before submitting, ending on the page that converted them

Lead Source reads the channel, entry page and page path as the buyer hits submit, then passes the lot to Zapier. The Dynamics lead turns up with the right option already selected.

How the connection works

Your site records it. A Zap creates the Dynamics lead.

The Microsoft Dynamics 365 app on Zapier is live and works with both Dynamics v9 and Dynamics 365. Zapier lists it as Premium.

  1. 01
    Recording starts with the buyer's opening page view: the real source, the campaign, the entry page, and each page the buyer opens after it.
  2. 02
    The buyer sends the form. Lead Source saves the lead for your dashboard and passes it straight to Zapier.
  3. 03
    The Zap calls Create Lead, Update Lead when the lead already exists, or Create Contact if your org works from contacts. Each captured value goes into a field that action offers.
  4. 04
    Dynamics has the lead, option set filled, before it is routed to a seller. Nobody in sales picks anything.

A tidy option set still needs the right option picked

Dynamics supplies the option set. Form tracking picks the option while the buyer is still on the form, the one moment anyone actually knows it.

See CRM lead source →
The captured record

What lands in Dynamics 365.

A sample Dynamics lead, as the Zap creates it from one form submission.

SAMPLE · captured lead → Dynamics lead at submission
Dynamics lead created
Sarah Donnelly
Procurement · Meridian Manufacturing
Lead SourceOrganic Bing
searchindustrial coatings
landed/industrial-coatings
journey/industrial-coatings → /case-studies → /quote
tableLead
Real source on the lead before it routes.
Safe setup pattern

From snippet to record, in three steps.

Only the verified Dynamics Zapier actions, mapped into the lead they create.

01

Put the script on your form pages

Each page that carries a form needs the Lead Source script, pasted just ahead of </head>. From then on, every visitor's source, entry page and path are on record.

02

Connect Lead Source to Dynamics in Zapier

In Zapier, set Lead Source as the trigger and pick Microsoft Dynamics 365 Create Lead as the action. Premium apps need a paid Zapier plan, and this is one.

03

Point the source at the option set

Send the captured source to the Lead Source option set, or to a text field if your options are too coarse, and put the campaign and entry page next to it. Then fill in your own form with a UTM on the URL and open the new lead in Dynamics to check the option it got.

Checked against the Microsoft Dynamics 365 app on Zapier, 30 June 2026. Four actions are there: Create Lead, Update Lead, Create Contact and Update Contact. The app is Premium and covers Dynamics v9 and Dynamics 365. Writing to arbitrary custom fields on standard records was not part of that check.

When this isn’t the right fit

Three reasons to hold off on Dynamics.

Read these before you build the Zap. Any one of them changes the plan.

  • Your Zapier account is on the free plan. Microsoft Dynamics 365 is a Premium app there, so the Zap will not run until you upgrade.
  • Your org runs lead capture through native Dynamics Marketing or Power Automate flows you would rather not duplicate. Map the path that owns the record.
  • Your team built one particular custom column and the source must go there. We write to what the four actions expose, and arbitrary custom-field writes have not been checked.
Common questions

Questions, answered.

Does Dynamics 365 already track lead source?

Yes, one option per record. The lead and opportunity tables in Dynamics 365 each have a Lead Source option set, and a record holds one option from a list your admin configures. That is a channel and nothing finer. Lead Source sets the option through a Zap, using what it read when the form was sent, and sends the campaign and entry page along with it.

Do I need a paid Zapier plan to connect Dynamics 365?

Yes. Zapier classes Microsoft Dynamics 365 as a Premium app, and Premium apps need a paid Zapier plan before a Zap can use them.

Which Dynamics versions does the connector cover?

Dynamics v9 and Dynamics 365. On either, the source goes in through four Zapier actions: Create Lead, Update Lead, Create Contact and Update Contact.

See your real Dynamics 365 lead sources.

Free to start. Connect Dynamics 365 through Zapier in minutes.

Track your Dynamics leads free →

Free to start · no card