Overview
The corsa-workflow-authoring skill adds Corsa workflow engine knowledge to your coding tool (Cursor, Claude Code, VS Code, etc.) so it can build, validate, and deploy compliance workflows. It covers the complete node type catalog, trigger configuration, variable interpolation, branch conditions, and the MCP-based workflow-builder interface.What It Helps With
- Building a workflow from a natural-language description
- Configuring event-driven and scheduled triggers with the correct filter syntax
- Assembling the node tree (ACTION, RECORD, NOTIFY, BRANCH, AI/Copilot)
- Wiring branch conditions using entity fields or prior node outputs
- Interpolating
{{variables}}in prompts, messages, and payloads - Validating and deploying workflows via the workflow-builder MCP tools or REST API
Quick Start
After installing the skill, ask your coding tool questions like:- “Build a workflow that triggers when a client’s risk rises to HIGH, runs an AI review, and opens an alert if suspicious”
- “What triggers are available for individual client events?”
- “How do I pass an AI node’s output to a downstream branch condition?”
- “Create a scheduled workflow that scans dormant clients weekly”
- “Fix this validation error: BRANCH_CHILD_TYPE”
What the Skill Knows
Mental Model
A workflow is one trigger + a parent→child tree of nodes. There is noedges array — every non-trigger node has a parentNodeId. Siblings of the same parent run in parallel; chain sequentially when a later node needs an earlier node’s result.
Triggers
Event-driven (triggerConfig) — fires when an entity is created or updated. Supported entities: individual_client, corporate_client, alert, case, transaction. Filters narrow which events fire the workflow (e.g. "field": "currentRisk.level", "operator": "changed_from_to").
Scheduled (scheduleConfig) — queries individual_client or corporate_client on an interval (min 5 minutes, max 1 year) and processes matching entities in a batch.
Node Types
Building Workflows
The skill knows two paths:- MCP workflow-builder tools (recommended for agents) — incremental mutations with validation feedback (
suggestedFix,allowedValues) after each step - REST API (
POST /v1/workflow-definitions) — one-shot submission of a complete definition
Variable Interpolation
{{variable}} placeholders resolve at runtime in NOTIFY messages, ACTION bodies, AI prompts, and RECORD payloads. Key variables: {{client.name}}, {{client.id}}, {{entity.<path>}}, {{node.<nodeId>.<field>}}, {{workflow.instanceId}}.
Common Mistakes It Prevents
Source
GitHub Repository
View the full skill source with the complete node catalog, trigger filter fields, variable catalog, and worked examples.