AI & agents

How Logic Conductor works

Learn how Logic Conductor turns exposed blocks, flows and business processes into tools, how inputs and outputs map, and what each kind of call does.

Applies toDataverse

Logic Conductor doesn’t have a fixed list of tools. When it starts, it reads the projects your administrator configured, finds every logic block, logic flow and business process with Expose as MCP Tool turned on, and creates one tool for each. Everything about the tool comes from the artifact you designed, so the quality of the tool is the quality of your design.

flowchart TD
  B[Blocks] --> C[Logic Conductor]
  F[Flows] --> C
  P[Business processes] --> C
  C --> T[One tool per<br/>exposed artifact]
  T --> A[AI assistant<br/>or agent]

Anatomy of a tool

Part of the tool	Comes from
Name	The artifact name, lowercased, with spaces replaced by underscores. With several projects exposed, the project name comes first. For business processes, `start_` comes first.
Title	The artifact’s title.
Description	The artifact’s description. For a business process, Conductor adds a sentence saying that the tool starts the process for an existing record of the process table.
Inputs	One input per input argument, with the argument’s name and description. A business process tool has one input: the ID of the record to start the process on.
Outputs	One field per output argument. Flow tools also return a run status.

Artifact	Projects exposed	Tool name
Block Calculate Discount	One	`calculate_discount`
Flow Approve Credit Limit in project Sales	Several	`sales_approve_credit_limit`
Business process Case Escalation	One	`start_case_escalation`

Inputs

Each input argument becomes a typed input, so the AI has to supply a value of the right kind.

Argument type	What the AI passes
Text	Text
Whole number	A whole number
Decimal, floating point or Currency	A number
Yes/No	`true` or `false`
Choice	The option’s number value. Two-option choices take `true` or `false`.
Date and time	A date and time
Lookup	The ID of the record. The table is fixed by the argument.
Unique identifier	The identifier as text
Image	The image as Base64 text
Row	A structured record with the columns the argument defines
List	A list of values of the item type

Outputs

Output arguments come back as fields of a structured result.

Output type	Returned as
Lookup	The record’s ID and name
Image	Base64 text
Row	A structured record with its columns
List	A typed list. Blocks and flows can return lists only when they are not exposed as a Dataverse action.
Everything else	Its plain value

What each kind of call does

Logic block tools calculate. The block is evaluated with the inputs and its outputs are returned. Nothing is written to Dataverse, so an AI can call block tools freely.

Logic flow tools run the flow for real, as the caller. The result includes the outputs and a run status:

Run status	Meaning
Success	The flow completed.
Success with error	The flow completed but reported an application error, for example through its error handling. The outputs that were set are returned.
(call fails)	The flow failed with an unhandled error. The AI receives an error message naming the flow and project, and can explain it to the user.

Business process tools start the process on the record you pass and return the new process instance’s ID and subject. The process’s precondition (who can start it and when it may start) is checked on every start, including starts from an AI. If the check fails, the process doesn’t start and the call returns an error.

Security

Every call runs as the signed-in caller, with their Dataverse security roles, business unit and team membership. A tool can only read and change what that person could read and change in Dataverse.

When changes appear

Conductor builds its tools when it starts. After you turn Expose as MCP Tool on or off, or change an exposed artifact’s name, description, inputs or outputs, Logic Conductor must be restarted before AI clients see the change. Ask your administrator to include a restart in your release steps.