Why should you care?

Business analysts model hospital intake paths without reading C# orchestrator code.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.WorkflowStudio/WorkflowJson.cs
public sealed record WorkflowJson(string Name, WorkflowNode[] Nodes);
public sealed record WorkflowNode(string Id, string Type, string? Agent, string[]? Next);

// sample exported JSON deserialized at runtime
var flow = JsonSerializer.Deserialize<WorkflowJson>(json);
var runner = new JsonWorkflowRunner(sp);
await runner.ExecuteAsync(flow, payload, ct);

What happened?

• WorkflowJson describes nodes and edges; JsonWorkflowRunner walks graph invoking named agents per node type.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Build Blazor Workflow Studio drag-drop MVP.
2. Validate acyclic graph and required HumanReview nodes on write paths.
3. Store published JSON in SQL with version column.
4. Add conditional branch on lead score threshold.
5. Import/export workflows between tenant sandboxes.

Remember

Workflow platform stores agent graphs as versioned JSON. JsonWorkflowRunner executes declarative flows safely. Validate graphs before publish; support dry-run.

Analyst-built intake flow

Hospital ops adjusts triage branch in Studio without dev ticket.

Outcome: Published JSON activates next day; audit records workflow version id.