How to Create a Workflow

Learn how to design and test a multi-step workflow in Chorigen Studio. This tutorial demonstrates how Chorigen acts as the "connective tissue" between AI agents and human tasks, orchestrating collaborative workflows where humans and AI work together seamlessly.

Intermediate ⏱️ 25 minutes

On this page

Overview

In this tutorial, you'll build a "Checkit Analytics" workflow that evaluates financial risk from quarterly snapshots. The workflow demonstrates how Chorigen coordinates multiple participants (both AI agents and humans) in a structured process:

  1. Context Retriever (AI Agent) — Collects financial data through a form
  2. Context Retriever Result — Reviews and inspects the collected data
  3. Confirm — Human validation step with conditional branching
  4. Auto Approval — Final confirmation message based on risk assessment

This workflow showcases how Chorigen acts as connective tissue, allowing you to define the structure and logic while different actors (AI or human) handle individual tasks.

Part 1: Configure Workflow Structure

What You'll Configure

🤖 Context Retriever (AI Agent)

An Input/Data Entry task that collects financial information using your Quarterly Financial Snapshot form.

Represents a potential AI agent that could gather data automatically.

📊 Context Retriever Result

A View/Inspection task for reviewing the collected data using the same form in read-only mode.

Allows humans to inspect AI-gathered information.

✅ Confirm

A SubProcess with a Confirm semantic operation that evaluates data and branches based on conditions.

Demonstrates conditional logic in workflows.

🎉 Auto Approval

A Confirmation Message task that notifies participants of the workflow outcome.

Final step that communicates results.

Part 2: Define Logic and Test

What You'll Learn

🔀 Conditional Branching

Add conditions to workflow nodes that evaluate data and determine the next step in the process.

Example: Route to different approval paths based on financial ratios.
📝 Expression Editor

Use the expression editor to create logic using form field references and comparison operators.

Example: $1.response.qVar8 < 0.2 checks if a debt ratio is below 20%.
🧪 Testing Workflows

Test expressions with sample values, generate test applications, and walk through workflows with real data.

Verify your workflow logic before deploying to production.
🏷️ Named Conditions

Give meaningful names to your conditions (like "Low Risk", "High Risk") for better workflow readability.

Makes complex workflows easier to understand and maintain.

Key Workflow Concepts

Task Types

Chorigen workflows support several task types that determine how participants interact with each step:

Task Type Purpose Form Usage
Input/Data Entry Collect information from participants Editable form fields
View/Inspection Review data without modification Read-only form display
SubProcess Encapsulate logic and branching Optional — can contain nested workflows
Confirmation Message Display results or notifications Message content only

Semantic Operations

SubProcess tasks can be configured with semantic operations that define their behavior. The Confirm operation used in this tutorial evaluates conditions and routes the workflow based on the result.

Expression Syntax

Reference form data in expressions using this pattern:

$<task_number>.response.<field_id>

Examples:

  • $1.response.qVar8 — Access the value of field qVar8 from task 1
  • $1.response.qVar8 < 0.2 — Check if the value is less than 0.2
  • $2.response.companyName == "Acme Corp" — Compare text values

AI-Human Collaboration

This workflow demonstrates Chorigen's core value proposition: orchestrating AI agents and human workers in structured processes. The "Context Retriever (AI Agent)" represents a future AI agent that could automatically gather financial data, while human participants review, validate, and make decisions based on that data.

What's Next?

Now that you've created your first workflow, you're ready to:

🚀 Deploy Your Workflow

Publish your workflow and make it available to your team for real-world use.

Tutorial coming soon
📊 Monitor Workflow Instances

Track workflow progress, view submissions, and analyze results from completed workflows.

Tutorial coming soon
🔧 Advanced Expressions

Learn complex expression syntax, mathematical operations, and data transformations.

Tutorial coming soon
🤝 Integrate AI Agents

Connect real AI agents to your workflow tasks and automate data collection and processing.

Tutorial coming soon

Troubleshooting

Can't find my form in the form selector?

Make sure you've created and saved the "Quarterly Financial Snapshot" form. Forms must be saved before they appear in workflow configuration. If you just created the form, try refreshing the workflow canvas.

Expression test fails with "undefined"?

Verify that the field ID in your expression matches the actual field ID in your form. Field IDs are usually like qVar1, qVar2, etc. You can check field IDs by opening the form in Design Studio and inspecting each field's properties.

Workflow won't save?

Ensure all required fields are filled in for each task node (especially the task name and task type). Check your network connection, as Design Studio requires connectivity to save workflows.

Can't generate test application?

Your workflow must be saved before you can generate a test application. Also ensure that all task nodes are properly configured and connected. Disconnected nodes or incomplete configurations will prevent test generation.

Test instance doesn't open?

Make sure you've clicked "Get Test Instance" after generating the test application. The test instance creates a specific workflow execution that you can interact with. If it still doesn't open, check your browser's popup blocker settings.

Need more help?

Contact us at support@chorigen.com or check the documentation for more detailed information about workflow design and testing.