Workflow Authoring Skill

​

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, scheduled, and manual triggers with the correct filter syntax
• Assembling the node tree (ACTION, RECORD, NOTIFY, BRANCH, AI/Agent, API_REQUEST/Webhook)
• 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 member’s sanctions status changes, sends a form RFI with reminders, and opens an alert if they don’t submit within a week”
• “Create a workflow that creates an alert 30 days after a corporate client update”
• “What triggers are available for individual member events?”
• “How do I pass an AI node’s output to a downstream branch condition?”
• “Escalate an alert to a case and update the case priority in the same workflow”
• “Add a webhook that POSTs case data to our ticketing system”
• “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 no edges 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, individual_member, corporate_member, alert, case, transaction. Filters narrow which events fire the workflow (e.g. "field": "currentRisk.level", "operator": "changed_from_to"). Common filter fields by entity: Scheduled (scheduleConfig) — calendar recurrence (daily, weekly, monthly) with time, timezone, and optional weekdays. Queries individual_client or corporate_client matching filters and processes each match in a batch. Manual (triggerMode: manual, manualConfig) — analyst runs from alert, case, client, or transaction record pages. Workflow must be active and allow manual trigger for the entity type.

​

Node Types

​

ACTION subtypes

Webhooks are not ACTION nodes — use API_REQUEST (Webhook block).

​

RECORD operations

UI-selectable operations (RECORD_EVENT_TYPES):

• ALERT_CREATED — optional createDelay (e.g. "7d", "2w", "3M")
• ALERT_UPDATED — includes escalation (status: ESCALATED)
• CASE_UPDATED — update case after escalation in same run
• CLIENT_UPDATED, TRANSACTION_UPDATED

CASE_CREATED exists in types/validation but is not in the builder dropdown — use alert escalation or API if case creation is required.

​

Building Workflows

The skill knows two paths:

1. MCP workflow-builder tools (recommended for agents) — incremental mutations with validation feedback (suggestedFix, allowedValues) after each step
2. 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, RECORD payloads, and Webhook bodies. Key variables: {{client.name}}, {{client.id}}, {{entity.<path>}}, {{node.<nodeId>.<field>}}, {{workflow.instanceId}}.

---

​

Common Mistakes It Prevents

---

​

Source