Process Plugin
The ProcessPlugin is the bridge between Octopus agents and Flow Studio workflows. It enables two-way integration: agents can trigger workflows from a conversation, and Flow Studio workflows can invoke Octopus agent reasoning as a node step.
Two-Way Integration
Agent → Workflow
The agent calls the start_workflow MCP tool. Octopus invokes the Flow Studio ProcessServer. The agent can wait for the result (synchronous) or fire-and-forget (asynchronous).
Workflow → Agent
A Flow Studio AI Agent Node invokes an Octopus agent turn as a workflow step. The agent's response becomes the node's output — available to subsequent workflow nodes.
Agent as HIL Actor
An Octopus agent can act as an automated HIL (Human-In-the-Loop) approver in a workflow. The agent receives the HIL task, reasons about it, and submits an approval or rejection programmatically.
Integration Architecture
// Conversation turn — agent triggers a workflow
User: "Please submit my annual leave request for next week."
Agent:
← Calls start_workflow tool:
{ "workflow_id": "leave-approval-workflow",
"inputs": { "employee_id": "EMP-1234", "days": 5, "start_date": "2024-06-24" },
"mode": "sync" }
→ ProcessServer starts workflow execution
→ Workflow runs: approval gate → manager notification → ERP update
→ Workflow returns result to Octopus
Agent: "Your leave request for June 24–28 has been submitted and is pending manager approval (Ref: LR-8821)."Plugin Registration
builder.Services.AddOctopus(config =>
{
config.AddPlugin<SqlServerPlugin>();
config.AddPlugin<ChatbotUIPlugin>();
config.AddPlugin<ProcessPlugin>(); // Requires ChatbotUIPlugin for SSE streaming
});Services Registered
| Service | Purpose |
|---|---|
IWorkflowTriggerService | Calls IProcessServerClient to start workflows from agent tool calls |
IProcessServerClient | HTTP client to the Flow Studio ProcessServer API |
IOctopusHILActor | Implements the HIL actor interface for automated workflow approvals |