One paperwork path, three doors in.
A branched office flow for a growing SME. First the document type, then the fields for that type, then a person, then write. Other document types can be added later. This is not a full accounting product.
- Trigger
- Agent
- Knowledge
- Decision
- Tool
- Approval
- Result
SM Servis — a pragmatic model, not an ERP
Told as the SM Servis (smservis.cz) growth path: incoming invoices, the cash register, one warehouse with categories, employees — later performance and bonuses. Not a named ERP. Booking chat on that site stays In progress; this paperwork story is Planned and is not running live there.
Enough structure to run the workshop as it grows: incoming invoices, a real cash register, one warehouse with categories, a staff list. Performance and bonuses come later. Records live in your SQL, REST or MCP tools — not in a branded ledger we do not sell.
Incoming invoices
Supplier, number, dates, amounts, VAT, due date, lines if present. After approval, insert into your invoices table or a CSV.
Cash register
Cash receipts and related cash documents — enough to keep a workshop till, not a full statutory ledger.
One warehouse, several categories
A single stock location with categories (parts, fluids, and so on). Delivery notes update stock via SQL or MCP — not a multi-site WMS.
Employee list
Who works in the shop. A table you already keep, or SQL behind MCP Fabric. Directory federation stays on its own Planned track.
Performance and bonuses
Phase 3: measures from work already recorded, then a bonus calculation a person still approves. Planned — not live at SM Servis.
How it starts — same process, three ways
Forward an email with files
A message in the connected mailbox starts the process. Attachments are stored as files with a checksum — they are not poured into the prompt.
See emailUpload into Files
Photos and PDFs can be uploaded in the licensed Files add-on, including a drop link. They stay files, separate from searchable knowledge. Starting this same workflow automatically when a file lands is Planned.
See FilesAttach files to a chat message
Licensed website chat is Available. Attaching a file to a chat message so this paperwork process starts is Planned.
See website chatTypes in the first cut
Then the process
Detect the type first
Invoice, delivery note or cash receipt first; other types later. A dedicated diagram step for this classification is Planned.
See workflow stepsThen take the matching path
Once the type is known, Switch and Decision steps already send the run down the matching branch.
See workflow stepsFill the fields for that type
An agent plus field checks and mapping can fill what that type needs. There is no branded invoice reader in the catalog.
See workflow stepsA person must approve
Human approval already pauses the run. Staff get e-mail or channel buttons; admin shows a payload preview. That generic pause is Available.
See governanceDocument on one half, fields on the other
A split view of the paper and the extracted fields, changing the type and reading again, or adding a short instruction such as “the inv field is the invoice number”, is Planned.
See governanceWrite after approval
Then write through SQL or REST, store a CSV in Files, call an MCP tool, or map fields. Only these sinks are claimed.
See data connectionsWhat a person sees today vs what still needs building
Human approval already pauses the run. The split view of the paper and the fields, with a type change and a short instruction to the model, is not in the product yet.
Today: generic approval
The approval inbox shows title, description and a JSON-style payload. E-mail has Approve / Reject / Open. WhatsApp and similar channels can answer yes or no. That is enough for an MVP pause.
Must be built: split review
Document preview on one half, extracted fields on the other, editable values, change of type, optional instruction to the model, then re-parse — that screen does not exist yet.
Re-parse loop
Loop-back on the canvas is Available. The review UI that changes type, adds “inv is the invoice number”, and asks the model to read again is Planned.
Proposed diagram step — not generally available
A dedicated Classify document step would emit a type (invoice, delivery note, cash receipt, later others) and then Switch would branch. Today you can approximate this with an agent or judge plus Switch. A topic classifier already exists for visitor messages — it is not a document-type reader.
Classify document
Proposed canvas step: input is a file reference; output is a type plus confidence. Branches: invoice, delivery note, cash receipt, other. Not in the published step catalog as Available.
Mapped to real platform pieces
Each step names what exists today. Status uses the same labels as the rest of the site.
A connected mailbox starts the graph. Attachments land in Files as storage references.
EmailFiles (licensed)
Browse, upload and drop links. Binary store is not RAG. Auto-start of this workflow on upload is Planned.
Files (licensed)Website chat
Licensed guest chat can start other processes today. File attachments on a chat message are Planned.
Website chatKnowledge
RAG is searchable text. Do not treat the invoice PDF as a prompt dump; keep the file, extract fields in the graph.
KnowledgeAgent / judge
A model step can propose a type and fields. It is a workaround until Classify document exists.
Agent / judgeWorkflow nodes
Switch, Decision, validate fields, collect variables, map fields, loop back, code and HTTP are Available.
Workflow nodesHuman approval
Generic HITL via approval-service: pause, notify, approve or reject, resume. Split-pane review is Planned.
Human approvalSQL / REST / GraphQL
Catalog-gated data connections. Destructive SQL execute requires approval.
SQL / REST / GraphQLNotifications
Mail, Teams, WhatsApp or OpenClaw where those channels are licensed — including approval links.
NotificationsWhere approved data can go
SQL table
SQL connections and a data-query step are Available. Destructive SQL execute exists and waits for human approval. You insert into the tables you already keep.
SQL tableREST or GraphQL
HTTP, REST and GraphQL connections are Available as governed tools — not an open shell on a laptop.
REST or GraphQLCSV in Files
Licensed Files can store a generated file. There is no dedicated “export CSV” diagram step; a workflow tool, MCP call or code step would write it.
CSV in FilesMCP insert
An MCP tool step can call the same governed tools AI clients use — including a write, if that tool exists on the tenant server.
MCP insertMap fields
The map-fields step copies and transforms object fields with explicit mappings. It is not a packaged document-transform product.
Map fieldsPhased plan
What can be drawn as a workflow now, and what needs product work (a new step or a new approval screen).
Can run as a workflow now
Email start, licensed Files storage, agent or judge, Switch, field checks, map fields, generic approval, notifications, SQL (including destructive execute behind approval), REST, GraphQL and MCP tools.
Needs product work
Classify document step with a schema per type, split-pane review, re-parse with a type change and optional instructions, chat file attachments, and starting this workflow automatically when a file is uploaded in Files.
Phase 0 — Classify, parse, pause
Workflow now: email in, agent or judge proposes type and fields, Switch, generic approval. Product work: Classify document step and split-pane review (MVP can ship with payload-only approval).
Phase 1 — Invoices into DB or CSV
After approval, SQL insert or REST, or a CSV written into Files. Incoming-invoices agenda for SM Servis. Sinks above are Available; the dedicated review UI is still Planned.
Phase 2 — Cash register and warehouse
Same graph, more types and tables: cash documents, one warehouse with categories. Still your database — not a named ERP.
Phase 3 — People, KPIs, bonuses
Employee list, then performance from recorded work, then bonus calculation with human approval. Planned for the growing workshop.
Related pieces
Do not read this as SM Servis already processing invoices in production. Files is a licensed add-on. There is no branded accounting app and no store transform pack in the catalog.
Small and mid-size firms
Concrete situations: customer mail, an offer from chat, incoming papers, invoices, the calendar, a weekly note — with the pieces named honestly.
Connect a mailbox (a classic mailbox or Microsoft 365). A new message starts the workflow, attachments are stored, and none of that belongs in the prompt. Teams and WhatsApp can start the same kind of process.
Datastore
Business text for retrieval lives in Postgres with pgvector. Binary objects (photos, PDFs to keep) use the licensed files add-on with file-service and MinIO, including admin browse and anonymous drop links.
Workflow steps
The steps you can place on the canvas — from triggers and agents to approvals and actions.
Governance
Giving an agent access to a tool is not the same as giving it permission to use it. Before an action runs, MCP Fabric can evaluate tenant, identity, role, license, service, policy and capacity — including how much you are willing to spend. When an action needs a person, the workflow can stop, request approval and continue after the decision.
References
These sites run on MCP Fabric: customer conversations, knowledge search, approvals, operational workflows and related capabilities — according to what each organization actually has enabled.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes, finishes the work — and keeps token spend under your control.