Best Practices
Because Flowon Logic Conductor generates tools directly from your artifacts, the quality of the agent experience is decided in Flowon - in how you name, describe, and shape your action Logic Flows and Blocks. These practices help you expose clear, safe, and useful tools.
Design Actions as Tools
┌──────────────────────────────────────────────────────────────────────┐
│ WHAT MAKES A GOOD TOOL │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ 1. A CLEAR, ACTION-ORIENTED NAME │
│ The artifact name becomes the tool name. Prefer verbs: │
│ "Approve Credit Limit", "Calculate Discount", "Validate Order". │
│ │
│ 2. A DESCRIPTION THAT SAYS WHEN TO USE IT │
│ The artifact Description is what the agent reads to decide │
│ whether to call the tool. Describe what it does and when. │
│ │
│ 3. DESCRIBED, TYPED INPUTS │
│ Every Input argument becomes a parameter. Give each one a │
│ description and the right type so the agent supplies good data. │
│ │
│ 4. MEANINGFUL OUTPUTS │
│ Return the values the agent (or user) actually needs to act on, │
│ with clear Output argument names. │
│ │
└──────────────────────────────────────────────────────────────────────┘
Write for the agent, not just the developer
The tool's title, description, and parameter descriptions come straight from the artifact's metadata. Vague or empty descriptions produce tools an agent cannot use well. Treat the Description field as the tool's instructions.
Prefer explicit, typed inputs
Model inputs with specific types - an Entity Reference rather than a raw string ID, an Option Set rather than a free-text status, a typed number rather than a string. Conductor surfaces these as typed parameters, which keeps the agent's calls valid. See the type mapping.
Control Your Agentic Surface Area
Only mark intended artifacts as actions
The action flag is the opt-in switch that turns an artifact into a tool. Keep internal helper blocks and sub-flows as non-actions so they stay off the agentic surface. Promote a flow or block to an action only when you intend an agent to call it directly.
Scope FLOWON_PROJECTS deliberately
Expose only the projects whose logic an agent should be able to run. A focused project list keeps the tool catalogue small, relevant, and easy for the agent to reason about - and reduces the blast radius of an over-eager call.
Restart to refresh the catalogue
Tools are generated at startup. After adding, removing, or editing action artifacts - including their names, descriptions, or arguments - restart the server so MCP clients pick up the new catalogue.
Security and Governance
Run under the user's identity
In Secure HTTP mode, every tool call executes under the calling user's Dynamics identity via the Microsoft Entra On-Behalf-Of flow. Dataverse row-level security, business-unit scoping, and team membership apply to each Logic Flow run and Logic Block evaluation - an agent can only do what the user is permitted to do.
One instance per environment
Run a separate Conductor instance per Dataverse environment (Development, UAT, Production). Agents then invoke only the logic deployed to the environment they are connected to.
Use With Flowon Logic Assist
Flowon Logic Conductor and Flowon Logic Assist are two halves of the same story:
- Use Logic Assist to have AI help you build and refine Logic Flows and Blocks.
- Mark the finished artifacts as actions.
- Use Logic Conductor to expose and run those artifacts as tools.
The logic you author with Assist becomes the tools you operate with Conductor - and your organization is agentic-ready without writing a line of integration code.