Section 7: Build Conditional Workflows Using Views

Why Conditional Workflows Matter

Not all documents — or data points — should be treated the same way.

Using Single Select and Multi-Select properties, you can route documents to different stages in your workflow based on classification logic. This creates modular agents that are easier to test, scale, and manage.

This logic routing is done using the Views + Automate feature in V7 Go.

Real Example: Real Estate Appraisal Report Routing

How It Works: Conditional Workflows

Step 1: Add a Select Property

Example: “Property Type” → Options: Residential, Commercial, Industrial
Example: Views for each “Residential”, “Commercial”, and “Industrial” Leases.

Step 2: Set up Routing using Views

Create routing logic based on Select values
Route to different stages (views) depending on value
Each stage becomes a new view or sub-agent

Step 3: Build Conditional-Workflows

Each routed stage can have its own:
- Properties
- Prompts
- Tool logic
- Review rules

Handle Edge Cases with “Other” and Needs Review

Add an “Other” option to your Select list to catch outliers
Route “Other” to a “Needs Review” stage for human validation
Use this for edge cases, poorly scanned docs, or unstructured formats

Use Multi-Select for Overlapping Classifications

Example:

“What types of inspections were completed?”

Output: Structural, Fire Safety, HVAC

Multi-select enables multiple values per doc and can still be routed or grouped downstream.

Key Takeaway

Select properties + Automate = dynamic workflows.

Use this to:

Route documents to specific flows
Add complexity only where needed
Improve accuracy, speed, and maintainability