Skip to content
Open the app

Dynamics 365 Sales ​

Kadmo for Dynamics 365 Sales adds a Run Kadmo playbook button to leads and opportunities. A seller picks a workspace and a playbook, adds a note, and Kadmo creates a task from the record and runs the playbook on it. A note on the record's timeline says the run started, and a second note says how it ended, with the agent's verdict and summary and links to the files it published. The solution runs on Kadmo's Power Automate connector and the Kadmo API. This page covers getting it, installing it, the roles and settings, what a seller sees, the limits and troubleshooting.

Get the solution ​

Microsoft has not listed Kadmo for Dynamics 365 Sales on Microsoft Marketplace yet. Until it does, ask Kadmo support (support@kadmo.ai) for the solution. You get two managed solutions, which you import in this order:

  1. Kadmo connector: Kadmo's connector, packaged as a solution of its own.
  2. Kadmo for Dynamics 365 Sales: the button, the dialog, a table for the requests, two security roles, two settings and two cloud flows.

You can also get a Package Deployer package that installs both in order.

The solution needs an environment with Dynamics 365 Sales, in Unified Interface, and a Kadmo account.

Install ​

You need to be an admin of the environment.

  1. Import Kadmo connector, then share the connector with whoever makes the Kadmo connection.
  2. Make two connections as a user made for Kadmo, not as a person:
    • a Kadmo connection with an API token of a Kadmo member made for this connection (see The token);
    • a Dataverse connection.
  3. Import Kadmo for Dynamics 365 Sales and pick the two connections when the import asks for them.
  4. Give the user the Dataverse connection is made as the roles Basic User and Kadmo connection.
  5. Give Kadmo user to every seller who may press the button.
  6. Check that both flows, Kadmo: answer a request and Kadmo: note the result, are on. If one is off, the owner of the connections turns it on.

Roles ​

RoleForWhat it allows
Kadmo userSellersTogether with a Sales role, it is enough to see the button and press it: it lets a seller create and read their own requests and read the two settings
Kadmo connectionThe user of the flows' Dataverse connectionThe least the flows need: read and update every request, write notes on leads and opportunities, and read users' names. It holds no admin, maker or customizer privilege

A holder of Kadmo user runs playbooks as the Kadmo connection's member, in any workspace and with any playbook that member may use, and a run can spend credit. The role is the gate in Dynamics 365. The member you make for the connection is the gate in Kadmo.

Settings ​

Two environment variables set what the dialog offers first. Set them under Solutions › Default solution › Environment variables, or give them a value at import.

SettingValue
Kadmo default workspaceA workspace's slug or name in Kadmo
Kadmo default playbookA playbook's slug or name in Kadmo

The dialog reads both each time it opens, so a change shows at the next press. Case does not matter. A setting that is empty, or names a workspace or playbook the seller's lists do not hold, offers what the seller ran last.

Run a playbook ​

  1. Open a lead or an opportunity in Sales Hub. In a view, select exactly one row.
  2. Press Run Kadmo playbook on the command bar.
  3. Pick the workspace and the playbook, add a note if you like, and press Run.

The dialog waits for the flow, says Kadmo started with a link to the run, and closes. The first open of a session can take a little longer while the flow fetches the lists.

The task Kadmo creates is an internal task in the chosen workspace. Its title names the lead or the opportunity, and its description names who asked, when, and from which record. These fields of the record go to Kadmo: the company, the contact, the topic, the stage and the estimated value. Nothing else leaves Dynamics 365.

The notes on the timeline ​

NoteWhenWhat it says
Kadmo started playbookThe run has startedThe task's key, a link to the run, who asked
Kadmo finished playbookThe run has endedThe agent's verdict and summary, links to the files the run published, its evidence and its pull requests, and Open the run in Kadmo
Kadmo paused playbookA step of the run failed, and Kadmo paused the runThe error, and a link to the run, where you can resume it. If the run later ends, its end gets a note of its own
Kadmo stopped playbookThe run was cancelledA link to the run

The result note comes 30 seconds to a few minutes after the run ends. Each end gets one note. The links open Kadmo's pages, which ask a seller who is not a member of your Kadmo account to sign in. The note's author is the user of the flows' Dataverse connection, and its text names who asked.

The request behind each press is listed in Active Kadmo requests, with its status: Started, Waiting, Finished, Paused, Stopped or Failed.

Limits ​

  • Some ends get no result note. The result note is written when a job of the run ends. A run that ends without one gets no result note, and its request keeps its status. That happens when:

    • a verdict arrives after the last step's job;
    • someone overrides a halted last step;
    • someone marks the task as done, or cancels it, while no job runs.

    The start note's link shows the run's end in Kadmo.

  • One record at a time. From a view the button takes exactly one selected row.

  • Every job starts the result flow. Each job of the connection's member that has a task and a run starts Kadmo: note the result. A job not started from Dynamics 365 ends there, and its flow run shows as cancelled in the run history. Each run counts against the Power Platform request limits of the flow's owner.

  • Licences. Kadmo's connector is a premium connector, and the flows' owner may need a Power Automate plan that includes premium connectors.

  • Uninstalling the solution deletes the table and its requests. The notes on records stay.

  • Unified Interface in the browser, English only.

Troubleshooting ​

What you seeWhy, and what to do
The button is missingThe seller lacks Kadmo user, or more than one row is selected in a view
The dialog says the flow may be offKadmo: answer a request is off, or its connections are broken. Turn it on, or fix the connections
The dialog shows a sentence from KadmoKadmo refused the request: the token is revoked (401), the trial has ended or the credit is gone (402), or the workspace or playbook is not the member's (404). See Troubleshooting
The start note is there, but no result noteWait a few minutes after the run ends. Check that Kadmo: note the result is on and that its subscription is active under Integrations › Outgoing webhooks in Kadmo. A run that ended without a job (see Limits) gets no result note
The default playbook is not offered firstThe setting names a playbook the member's list does not hold. Use its slug or its exact name