A Process Map in FlowSharp is the level at which a business process is seen in its entirety: operational flows, departments, external systems, documents, manual steps, events and responsibilities.
The difference between a Flow and a Process Map:
A single flow answers the question: "How does this object move through a procedure?"
A Process Map answers a broader question: "How does this process really work, from start to finish, even when it crosses multiple flows, people and systems?"
What a Process Map contains:
- Linked flows — the FlowSharp flows that make up the process
- External systems — ERP, CRM, e-commerce, customer portals
- Documents — contracts, invoices, forms, reports
- Manual steps — activities that do not go through FlowSharp but are part of the real process
- Departments and responsibilities — who does what at each stage
When to use it:
- To visualise and communicate an end-to-end process to stakeholders
- To identify bottlenecks that span multiple flows
- To document the operational architecture before automating
- To verify that the real wiring (flows, webhooks, systems) matches the design
The Process Map is verified against FlowSharp's real wiring: if a flow is linked but not published, the map flags it.