FZ File Sequence Diagram Example
The reference example from the .fz file announcement: a text-first sequence diagram with two lanes, four nodes and one labeled message, stored as a portable .fz file.
MCP Server Order Fulfillment Example
Compact order fulfillment diagram generated through the FlowZap MCP server, written with the shorthand syntax: sales validation with a validity gate, then fulfillment processing and shipping.
Full FlowZap Code
Copy and paste the following FlowZap code into a project in your FlowZap account to see this template diagram.
sales { # Sales Team
n1: circle label:"Order Received"
n2: rectangle label:"Validate Order"
n3: diamond label:"Valid?"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> fulfillment.n4.handle(left) [label="Yes"]
}
fulfillment { # Fulfillment
n4: rectangle label:"Process Order"
n5: rectangle label:"Ship Items"
n6: circle label:"Complete"
n4.handle(right) -> n5.handle(left)
n5.handle(right) -> n6.handle(left)
}
Install the MCP packagenpm install -g flowzap-mcpMCP documentation
Related templates
n8n JSON Workflow as FlowZap Code
An n8n automation rendered as FlowZap Code: manual trigger, spreadsheet read, batch iteration, AI field mapping, PDF generation, email send, with success and error logging branches.
AI-Assisted E-Commerce Onboarding Workflow
Vibe-coding example: a cart lane and an AI lane, where the assistant analyses the shopper profile, asks for missing details and adds the suggested products to the cart.
Shipping Process Workflow
Order shipping workflow with carrier selection, rate shopping, label generation, tracking number assignment, and dispatch confirmation.
Saga Order Fulfillment Architecture
An order fulfillment saga architecture diagram with four sequential steps: customer verification, inventory reservation, payment authorization, and shipment creation, with a compensation chain that reverses completed steps on failure. This template models the end-to-end order lifecycle as a saga, showing how each service participates in the transaction and how compensating actions maintain data consistency. Ideal for e-commerce architects designing reliable order processing pipelines.
AI-Native Single Agent Architecture
A single-agent AI architecture where one agent handles everything: parsing requests, reasoning, calling tools via MCP, and generating responses. This is the default architecture for prototypes and simple automations—easy to debug but hits context-window limits quickly and is hard to parallelize. Ideal for MVPs and solo builders shipping fast.