Skip to content

Integration · CRM and sales

Microsoft Dynamics 365 and Meteor AI agents

Connect Microsoft Dynamics 365 to Meteor: create and update leads, opportunities and any Dataverse entity without piling up duplicate records.

How does Microsoft Dynamics 365 connect to Meteor?

Meteor connects to Microsoft Dynamics 365 through the Dataverse Web API and gives your Met 8 tools: search leads before creating so you do not duplicate them, create and update leads, and work with any other entity (opportunities, accounts, contacts, tasks, cases), including OData queries and operations that create or update depending on whether the record already exists.

What it automates

What a Meteor Met does with Microsoft Dynamics 365

Get the conversation into the corporate CRM

A prospect writes over WhatsApp and your Met looks them up in Dynamics. If they exist it updates them, if not it creates them, keyed on email or phone. Your rep finds them where they already work.

Stop filling the CRM with duplicates

The create-or-update tools exist for exactly this. A repeat conversation does not produce a repeat lead.

Move the opportunity, not just the lead

With the generic Dataverse tools your Met can create an opportunity, relate it to the account and move its stage as the conversation progresses.

Check before you answer

Before promising anything, your Met queries the right entity with OData parameters and answers with what the CRM actually says.

8 tools

Everything your Met can ask Microsoft Dynamics 365 for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool What it does
dynamics_search_leads Finds leads by exact email or by text across name, company or topic.
dynamics_create_lead Creates a lead with the fields you pass, using Dataverse logical names.
dynamics_update_lead Updates an existing lead to reflect a change in qualification or status.
dynamics_upsert_lead Creates or updates, deduplicating by email and, when there is no email, by phone.
dynamics_create_record Creates a record in any Dataverse entity, not only leads.
dynamics_update_record Updates any record by its identifier, to change stage, status or owner.
dynamics_query_records Queries any entity with OData parameters to filter, sort and expand.
dynamics_upsert_record Creates or updates a record in any entity, deduplicating by the field you choose.

The limits

What the Microsoft Dynamics 365 integration does NOT do

We would rather say it here than have you find out during rollout.

Before you start

What you need to connect Microsoft Dynamics 365

  1. 1

    Your Dynamics environment URL

    It is your organization address, with no trailing slash.

  2. 2

    Directory and application IDs in Entra ID

    You get both when you register an application in Microsoft Entra ID with permission on the Dataverse Web API.

  3. 3

    The client secret of that registered app

    You generate it in the same Entra ID app, and it is stored encrypted per workspace. It is what authenticates every call.

Frequently asked questions

Questions about Microsoft Dynamics 365 and Meteor

No. Alongside the lead specific tools there are generic operations on any Dataverse entity, so it can create and move opportunities, accounts, contacts, tasks or cases.

Through the create-or-update operations. They look the record up by a key field (email or phone on leads, whichever field you choose elsewhere) and only create when nothing matches.

Yes, you use Dataverse logical names. That is what lets your Met work against your real data model instead of a fixed mapping that breaks with every customization.

You need someone with those rights to register an application in Entra ID and grant it access to the Web API. After that the integration runs as that app, not as a person's account.

CRM and sales

Other integrations in the same family

Want to see a Met running Microsoft Dynamics 365?

We will show you with your own account connected, not with a canned demo.