Flowon Logic Conductor
Overview
Flowon Logic Conductor turns the business logic you have already modelled in Flowon into callable AI tools - automatically. It is a Model Context Protocol (MCP) server that inspects the Logic Flows and Logic Blocks in your Flowon projects and generates one MCP tool per action at startup. Every rule, calculation, validation, and workflow you have built becomes a typed tool that any MCP-compatible AI agent can invoke.
Where Flowon Logic Assist lets an AI build and change your Flowon configuration, Flowon Logic Conductor lets an AI run it. You do not write tool wrappers, JSON schemas, or integration code. If a Logic Flow or Logic Block is marked as an action, Conductor exposes it - with its inputs, outputs, title, and description carried straight through from the artifact definition.
The result: the day after you model your logic in Flowon, your organization is agentic-ready. Your rules and workflows are already available as governed, typed tools - executed under the calling user's Dynamics identity, with Dataverse security fully applied.
Key Capabilities
| Capability | Description |
|---|---|
| Auto-generate | Emits one MCP tool for every action-enabled Logic Flow and Logic Block in the configured projects |
| Typed I/O | Derives each tool's parameters and return shape from the artifact's declared Input and Output arguments |
| Execute | Runs Logic Flows and evaluates Logic Blocks live against Dataverse, returning structured results |
| Zero glue code | No hand-written tool wrappers - names, titles, and descriptions come from the Flowon definition |
| Governed | Runs under the user's identity via Microsoft Entra On-Behalf-Of; Dataverse row-level security applies to every call |
Logic Assist vs. Logic Conductor
Both are MCP servers for Flowon on Dataverse, but they serve opposite sides of the lifecycle. They are designed to be used together.
| Flowon Logic Assist | Flowon Logic Conductor | |
|---|---|---|
| Purpose | Author and manage Flowon configuration with AI | Expose and run existing Flowon logic as AI tools |
| When | Design time - building the solution | Run time - operating the solution |
| Tools | A fixed catalogue of CRUD tools (create/read/update logic, flows, processes, metadata) | A dynamic set of tools, one per action artifact in your projects |
| AI acts as | Builder - creates and edits artifacts | Operator - invokes rules and workflows |
| Outcome | The solution gets built | The solution becomes agentic-ready |
What is MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants (such as Claude, GitHub Copilot, and others) call external tools through a formal contract: a defined set of tools with precise inputs, outputs, and descriptions.
Flowon Logic Conductor implements this protocol so that your Flowon logic - not a generic data API, but the actual rules and workflows your business runs on - is presented to AI agents as first-class tools. Instead of teaching an agent how to reproduce a business rule, you expose the rule itself and let the agent call it.
How It Works
At startup, Flowon Logic Conductor:
- Connects to your Dataverse environment using the Microsoft Power Platform Dataverse Client
- Reads the action Logic Flows and Logic Blocks in the projects named by
FLOWON_PROJECTS - Generates one MCP tool per artifact, mapping the artifact's Input arguments to typed tool parameters and its Output arguments to the tool's return shape
- Serves those tools over MCP, executing each Logic Flow (run) or Logic Block (evaluate) on demand
┌────────────────────────────────────────────────────────────────────────┐
│ TOOL GENERATION AT STARTUP │
├────────────────────────────────────────────────────────────────────────┤
│ │
│ Flowon projects (FLOWON_PROJECTS) │
│ ───────────────────────────────── │
│ Action Logic Flows ┐ │
│ Action Logic Blocks ┘──► Conductor ──► MCP tools │
│ │
│ "Approve Credit Limit" ──► approve_credit_limit(customerId, ...) │
│ "Calculate Discount" ──► calculate_discount(orderTotal, tier) │
│ "Validate Order" ──► validate_order(order) │
│ │
│ Each tool carries the artifact's title, description, typed inputs │
│ and outputs - straight from the Flowon definition. │
│ │
└────────────────────────────────────────────────────────────────────────┘
See How Tool Generation Works for the naming rules, type mapping, and execution semantics.
Product Scope
Flowon Logic Conductor requires Logic Composer to be installed and licensed in the connected environment, and it only exposes Logic Flows and Logic Blocks that are marked as actions. Marking an artifact as an action is what opts it in to being surfaced as a tool - so you stay in control of your agentic surface area.