LanguageENES
Microsoft Dynamics 365Coming soon · 26 SeptemberAvailable on Business

Send chatbot leads to Dynamics 365

A row in Dataverse, in the table your environment already has

A lead from the chat becomes a row on the table you pick -- Lead, Contact, Account, Opportunity or one of your own -- with the columns read from your environment rather than from a template.

What it does

Your environment's columns

The mapper reads the table definition, so it offers the columns your customiser created, with the ones Dataverse will not accept from a form left out rather than offered and refused.

One environment per connection

Production, sandbox and developer live on different hosts, and a token for one is refused by another. The connection asks which URL it is for, so the answer is never a guess.

Every table, sales ones first

Lead, Contact, Account and Opportunity at the top, then your custom tables, then the rest, grouped so the picker stays usable in an org with eight hundred of them.

How to connect it

Read the full guide
  1. 1

    Register an app in Entra

    An app registration with a client secret. Note the directory and application ids; the secret is shown once.

  2. 2

    Add it as an application user

    Inside the Power Platform admin centre, with a security role. Skipping this is the one failure that looks like a bad secret and is not: the token is valid and every call answers 403.

  3. 3

    Connect Dynamics

    Paste the environment URL and the three values. We verify by reading the organisation's own name back.

  4. 4

    Map the columns

    Auto-map, then check it. A Lead needs a surname, and one is filled in when the mapping leaves it out.

Questions people ask

Which licence does the application user need?

An application user does not consume a user licence, but it does need a security role with Create on the table you choose. Without the role the call is refused and the message names the table.

Can it write to a custom table?

Yes. Anything the environment exposes to advanced find shows up in the picker, custom tables included, under their display name.

What about choice columns and lookups?

Not yet. A choice wants an option value and a lookup wants a row id, and a mapped string is neither. They are left out of the mapper rather than offered and dropped on send.

Does it work with Business Central?

No. Business Central is a different API and is not what this connects to. This is Dataverse: Sales, Customer Service, Field Service and anything custom built on the same tables.

What teams use it for