WorkflowFramework
A fluent, extensible workflow and pipeline engine for .NET.
Getting Started
- Getting Started — Installation and first workflow
- Core Concepts — Steps, context, middleware, events
Building Workflows
- Fluent Builder — Complete builder API
- Branching — Conditional logic
- Loops — Iteration patterns
- Parallel Execution — Run steps concurrently
- Typed Pipelines — Strongly-typed workflows
- Dynamic Expressions — Runtime expression evaluation and templates
Reliability & Operations
- Error Handling — Try/Catch/Finally, compensation
- Middleware — Interceptors and cross-cutting concerns
- Resilience (Polly) — Retry, circuit breaker, timeout
- Persistence — Checkpointing and state stores
- Scheduling — Cron and interval scheduling
- Hosting — ASP.NET Core integration and health checks
Integration & Data
- Enterprise Integration Patterns — Router, Splitter, Aggregator, Scatter-Gather, and 15+ more EIP steps
- Connectors — HTTP, SQL, FTP, gRPC, messaging (RabbitMQ, Kafka, Azure SB)
- Data Mapping — Declarative field mapping, format conversion, schema validation
- Event-Driven Workflows — Publish/subscribe, event correlation
- Reactive Extensions — Streaming steps with
IAsyncEnumerable<T>
AI & Human Tasks
- AI Agents — LLM calls, AI routing decisions, autonomous planning (Ollama, Semantic Kernel)
- Human-in-the-Loop — Approval gates, task inbox, escalation, delegation
Agentic
- Agentic Workflows — Autonomous agent loops, tool registries, context sources
- Hook Lifecycle System — Intercept, audit, and control agent execution
- Context Compaction — Manage long conversations with auto-compaction and checkpointing
- MCP Server Integration — Connect to Model Context Protocol servers
- Agent Skills — Load reusable agent instructions from SKILL.md files
Advanced
- Configuration — YAML/JSON workflow definitions
- Dependency Injection — DI container integration
- Diagnostics — Tracing and observability
- Extensibility — Custom steps and middleware
- Validation — Workflow validation rules
- Versioning — Schema versioning
- Visualization — Workflow graph rendering
- Testing — Test harness and utilities
Architecture
WorkflowFramework is built around a simple pipeline model:
Steps → Middleware → Context → Runner
Steps are units of work. Middleware wraps step execution (logging, retry, auth). Context carries data through the pipeline. The Runner orchestrates execution. Everything is interface-based and extensible via DI.