Build and change flows with AutoFlow Intelligence
AutoFlow Intelligence is rolled out to selected organisations first. If the Create with Intelligence button does not appear in your Flow Workspace, your organisation is not switched on yet – contact mse.
Intelligence builds a flow from a description in your own words, or changes an existing flow the way you ask. It runs inside Business Central with the AI provider you bring – Anthropic, OpenAI, Azure OpenAI / Microsoft Foundry or any compatible endpoint – using your own API key. The result is always a draft that you review and publish yourself.
What it does
- You describe the flow (or the change) in the floating Create with Intelligence button on the Flow Workspace, or Change with Intelligence in the flow editor. While Intelligence works, the button's edge turns.
- The model reads the AutoFlow documentation that belongs to your AutoFlow version and looks at your environment: tables, fields and their relations, option values, page field order, existing flows, credentials and number series. It never sees your business records unless an administrator allows sample records. It knows every trigger and action installed in your environment – also those of other apps and your own extensions – and reads each step's documentation before it uses it. Steps your organisation cannot use (for example early-access steps that are not switched on) are not offered to it.
- If something essential is unclear, it asks you a few questions – with options where possible.
- It builds the flow, validates it with AutoFlow's own checks and hands you the result with a journal: what it built, which assumptions it made, what the environment needs, and every external target (URL, e-mail recipient, credential) the flow uses. Check those before you save.
- Intelligence saves the result right away – as a new draft flow, or as the next draft version of the flow you changed – and shows a card: New flow created as a draft or New draft version created. Open draft opens it, Discard deletes the draft again (the version you started from is current again), Details shows the journal. The journal stays on the version in the version history. Nothing is published: Intelligence drafts, you decide.
Set it up (AutoFlow Admin)
- Open AutoFlow Setup → AutoFlow Intelligence Setup (also reachable from the Flow Workspace menu).
- Provider Profiles → New from Template – choose your provider. The template fills protocol, base URL and model and creates a credential for the API key. For the classify mode of the Intelligence step, add a second profile from the template TypeSafe Jev (classification) with your TypeSafe API key; it only answers classification questions and never builds flows.
- Open the Credential and paste your API key. For Azure OpenAI / Foundry adjust the base URL to your resource and the model to your deployment name.
- Test Connection – the model must call tools; parallel tool calls make sessions faster but are optional.
- Back on the setup: Enable AutoFlow Intelligence. You confirm which data is sent to the provider: metadata of your environment and – only if you switch it on – up to five sample records per table.
- Optional: limits per session (rounds, tool calls, token budget) and prices per million tokens for the cost estimate.
Everyone who may build flows (the AutoFlow User role) can use the button; only administrators change the setup and the provider profiles.
Business Central must be allowed to reach the internet: the provider's endpoint, and once per AutoFlow version codeload.github.com, from where AutoFlow downloads the documentation the model works with (the public AutoFlow agent docs). In a sandbox, switch on Allow HttpClient Requests for AutoFlow on the Extension Management page. On-premises, allow both hosts in your firewall. If the download fails and no earlier documentation is stored, the session stops with the reason.
Costs and data
- The tokens go to your provider under your contract; AutoFlow shows rounds, tokens and an estimated cost in every session. mse receives nothing.
- Each session is logged under AutoFlow Intelligence Setup → Sessions (rounds, tool calls, tokens, status; the conversation itself when the setup keeps it). The log is cleaned up by a retention policy (90 days by default).
- Sensitive values never leave Business Central: credentials are listed by code only, sample records are off unless an administrator allows them.
Tips for good results
- Name the business objects: "when a sales order is released", "the customer's e-mail", "the item's vendor".
- Say what should happen on the edges: what if nothing is found, what if the field is empty.
- For changes, describe the change, not the whole flow – Intelligence edits only the steps it needs to.
- Read the assumptions and open points in the journal; that is where the model tells you what it decided for you.
Intelligence also works inside your flows: the Intelligence step answers prompts and classifies documents while a flow runs.
Do you develop your own triggers or actions? See Document your own triggers and actions for AutoFlow Intelligence.