Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corsa.finance/llms.txt

Use this file to discover all available pages before exploring further.

Corsa Workflows let compliance teams automate repeatable operational steps without code. Build a workflow visually, choose what should trigger it, add blocks for decisions and actions, then activate it when ready. Use workflows to reduce manual handoffs across onboarding, transaction monitoring, alert triage, case operations, and periodic reviews.

​
How It Works

  1. Choose a trigger: an event in Corsa, such as a new alert, updated case, created transaction, or client update.
  2. Add blocks to decide what happens next: update records, create follow-up items, branch by condition, or notify the right people.
  3. Save changes as a draft until the workflow is ready.
  4. Activate the workflow so it starts running automatically.
  5. Review each execution in the workflow history, including step-by-step outcomes and linked results.

​
Workflow Builder

The builder gives your team a visual canvas for designing automation logic. Every workflow starts with a trigger and then flows through one or more blocks. Available workflow blocks include:
  • Record - Create or update Corsa records, including alerts, cases, clients, and transactions.
  • Action - Trigger a customer interaction, such as an email-based request for information.
  • Notify - Send an in-app, email, or Slack notification.
  • Branch - Split the workflow into conditional paths based on alert, case, or client data.
You can rename workflows, edit blocks, add parallel branches, and discard unsaved changes before publishing.
Keep workflows small and focused. A workflow that owns one operational outcome is easier to review, test, and audit.

​
Triggers

Workflows can start from Corsa events or from a recurring schedule.

​
Event Triggers

Event-based workflows run when matching activity happens in Corsa. Supported event families include:
  • Individual client created or updated
  • Corporate client created or updated
  • Transaction created or updated
  • Alert created or updated
  • Case created or updated
Each trigger can include filters, so the workflow only runs when the event matches your criteria. For example, you can trigger a workflow only for high-priority transaction monitoring alerts, clients with a specific risk level, or cases in a specific stage.

​
Scheduled Triggers

Scheduled workflows run on a recurring interval. Use them for periodic review, stale-case checks, recurring client controls, or other time-based operations. Schedules support minute, hour, day, and week intervals, with a minimum interval of 5 minutes. Scheduled workflows can target individual or corporate clients and can include filters to narrow the population.

​
Draft, Active, Inactive, and Archived

Every workflow has a lifecycle:
  • Draft - Editable, but not running yet.
  • Active - Live and eligible to run automatically.
  • Inactive - Paused. You can reactivate it later.
  • Archived - Retained for history, but no longer editable.
Drafts are useful while building or updating a workflow. When you activate a workflow, Corsa validates the workflow structure first, so incomplete or invalid workflows do not go live.

​
Execution History

Each workflow keeps a history of its runs. Use the execution list to see status, start and completion time, duration, creator, failed step, and generated results. Execution statuses include Pending, Running, Completed, Failed, Cancelled, and Timed out. Open an execution to inspect the timeline. The timeline shows each step, whether it succeeded, failed, skipped, or is still running, and any output or error details available for that step. When a workflow creates or updates a linked result, such as an alert, Corsa shows that result directly in the execution detail so analysts can jump from the run history to the affected record.

​
Common Use Cases

Alert triage automation

When a high-priority alert is created, assign ownership, update priority, notify the compliance team, and branch based on alert category.

Case operations

When a case changes stage, update related fields, notify reviewers, or trigger customer follow-up.

Client review controls

Run scheduled checks over individual or corporate clients and start review actions when risk or activity criteria match.

Transaction follow-up

When a transaction is created or updated, branch by amount, status, type, or risk context and create downstream compliance work.

​
Best Practices

  • Start with a narrow trigger and add filters early.
  • Use branches for meaningful business decisions, not cosmetic structure.
  • Keep record updates explicit so analysts can understand what changed.
  • Review execution history after activation to confirm the workflow behaves as expected.
  • Pause inactive workflows instead of deleting operational history.