Design automated legal logic with a node-based workflow engine.
The Flow Builder is a visual programming environment where you define conditional paths for document processing. By connecting different types of nodes, you can automate decisions like approving low-risk contracts, flagging specific clauses for senior review, or iterating through tables of financial data.
1. Canvas & Workspace
The workspace provides an infinite canvas with smart connection validation to ensure your automation logic is robust.
Node Palette: Access all automation building blocks from the left sidebar. Drag any node onto the canvas to start.
Smart Connections: Drag handles between nodes to create logic paths. The builder prevents invalid connections (e.g., connecting an "End" node back to a "Start" node).
Logic Handles: Nodes like Condition and Filter have multiple output handles (Yes/No, Match/No Match) to fork your workflow.
FLOW CANVAS
Recording: Dragging nodes, connecting them via handles, and using the toolbar
2. Node Directory
Understand the purpose and configuration of each building block in your flow.
Start Node
The entry point. Every flow begins here when a document is processed.
Condition Node
If/Else logic. Brands paths as "Yes" or "No" based on field values.
Action Node
Perform a specific task like Reject, Approve, or Notify Stakeholder.
Filter Node
Advanced matching for finding specific items within arrays or tables.
Loop Node
Repeat steps for every item in a list (e.g., every row in a table).
End Node
Marks the completion of a specific workflow path.
3. Node Deep-Dive
Each node in the Flow Builder serves a unique purpose in your automation logic. Below is a detailed breakdown of when and how to use them effectively.
Start Node
How to Use: Every flow must begin with exactly one Start node. It is pre-placed on new flows and cannot be deleted.
When to Use: Use it to define the trigger point. In most workflows, this represents the moment a document is successfully uploaded and initial fields are extracted.
Example: A "Lease Agreement" workflow triggers the Start node as soon as the PDF is uploaded.
Condition Node
How to Use: Connect an input to the top and define a field comparison (e.g., Total Amount > 50000). It has two outputs: Yes (right) and No (bottom).
When to Use: Use this for binarized branching logic. Use it when you need to fork the workflow based on document data.
Example: If Indemnity Clause is "Not Found", route to Flag for Review. If "Found", route to Approve.
Action Node
How to Use: Place this at the end of a decision path. Pick an action from the dropdown like Reject Document or Notify Stakeholder.
When to Use: Use this to perform the final outcome of your logic. It is the "result" of your automation.
Example: Automatically set the document status to "Compliant" if it passes all condition checks.
Filter Node
How to Use: Target a Table field and specify a search criterion (e.g., Find row where Service Name contains 'Maintenance').
When to Use: Use this when dealing with complex data structures or arrays. It allows you to isolate specific data points for further checking.
Example: In an invoice, find the row for "Delivery Fee" to ensure it doesn't exceed the agreed cap of $10.
Loop Node
How to Use: Select a table or list field. Connect the Do handle to a logic path that should run for every item. Use Next to continue the flow after finishing.
When to Use: Use this for repetitive verification. If you have 20 line items and each needs an individual compliance check, the Loop node is required.
Example: For every party listed in a "Multi-Party Signature" table, check if their Signature Status is "Signed".
End Node
How to Use: Connect the final node of any logic path to an End node to terminate processing for that branch.
When to Use: Use this to signify that no further automation is needed. Every path must eventually reach an End node or an Action node.
Example: Place after a Reject action to signal the document summary is finalized and no more checks apply.
4. Action Types Library
12+ Actions Available
The Action Node is the final destination for any logic branch. Below are the supported actions that the Juricloud AI can trigger based on your defined criteria.
Approve Document
Sets document status to Approved and triggers downstream workflows.
Reject Document
Flags document as Rejected and halts further automated processing.
Flag for Review
Puts the document in the Manual Review queue for senior counsel.
Escalate to Senior
Assigns the document task to a senior member of the legal team.
Request Revision
Notifies the uploader that specific fields or clauses require correction.
Mark Compliant
Adds a "Compliant" metadata tag to the document record.
Mark Non-Compliant
Adds a "Non-Compliant" tag and triggers a high-priority risk alert.
Archive Document
Moves the document to the Archive folder after processing.
Notify Stakeholder
Sends an in-app notification to specific users or teams.
Send Email
Sends a customized email with document details to external recipients.
Generate Opinion
Triggers the AI to draft a formal legal opinion based on extraction data.
Draft Document
Automatically drafts a follow-up document (e.g., a counter-offer).
5. Building Your Flow
Follow these steps to translate your legal processes into a working automation.
Place Nodes: Drag nodes from the palette onto the grid. Every flow must have one Start node and at least one End node.
Connect Logic: Link the output handle of one node to the input handle of another. For Condition nodes, link both "Yes" and "No" paths.
Configure Data: Click a node to open the Configuration Panel. Select the workflow fields (e.g., "Contract Value") and operators (e.g., "Greater Than") to define the logic.
Validate: Check the status indicator in the top toolbar. It will flag unconfigured nodes or broken paths in real-time.
Activate: Once valid, click Activate to move the flow from Draft to Live.
NODE CONFIGURATION
Recording: Configuring a Condition node and choosing an Action (Reject) for the 'No' path
6. Iteration & Scoping
The Loop Node allows you to process repeating data blocks, such as line items in a bill or parties in a multi-party agreement.
Variable Scoping
When you connect a node to the "Do" handle of a Loop, that node gains access to exclusive Loop Variables. This allows you to perform checks on individual rows within a table.
LOOP LOGIC
Recording: Setting up a Loop on a 'Financial Table' and mapping iterator variables
7. Flow Execution
Execute your automated logic against document sets in your workspace.
Selection:
Filter by Case or search for specific files to include in the run.
Contextual Modes:
Individual Processing: Each document is run through the flow separately.
Array Processing: Documents are analyzed together (Aggregate Mode).
Natural Language Overrides:
Use the Context Box during execution to add specific instructions (e.g., "For this run, treat all flagged values as warnings only").
FLOW EXECUTION MODAL
Recording: Selecting documents and launching a flow analysis
Active vs. Draft
Flows cannot be modified while Active. You must deactivate a flow to make changes to its nodes or connections.
