The diagram is the process — not just a picture.
An automated process defines what happens, in what order, under which conditions and when a person should step in. What you draw is what runs.
- Starting point
- Agent
- Knowledge
- Decision
- Tool
- Approval
- Result
What the diagram contains
Part of the core. A person’s approval is a real step — not a footnote.
Explicit steps
A starting point, an agent, search, a decision, a tool, a loop, approval and a reply are steps. Behaviour comes from the diagram.
Step catalogue
Step types and their contracts come from the platform. The screen does not invent magic at run time.
A run that can wait
The platform starts the diagram, keeps state, pauses for approval and continues after a decision.
Authoring in admin
On the canvas you pick a step, open its detail, version the diagram and publish a run.
Explore more
Automated process steps
From starting points and agents to approvals, actions and notifications. The company calendar is one of those steps — an appointment in the calendar, not an engineering shortcut.
Automated processes
An automated process is more than a diagram on a canvas. It defines what happens, in what order, under which conditions and when a person needs to step in. You can combine information retrieval, decisions, business-system actions, approval and delivery of the result into one repeatable process. Once designed, the AI can run that process consistently.
From request to action
MCP Fabric can turn a request into an actual process: Ask → Understand → Retrieve → Decide → Execute → Approve → Done. AI can retrieve the right business knowledge, make a decision, call the appropriate tools, wait for human approval when needed and continue the automated process.
Ready to move beyond the chatbot?
Build AI that understands your business, works with your knowledge, follows your processes and can actually finish the job. You decide which actions are allowed, when a person must step in and how much AI usage your organization can consume.