Skip to main content

​
Overview

Each workflow node has configuration options that control its behavior. This guide covers the settings for each node type.

​
Policy Trigger Node

Fires when a policy produces a matching assessment.
SettingOptions
PolicySelect which policy to monitor
CompliantMatch compliant or non-compliant results
Risk LevelLow, Medium, High, Critical (or any)
Confidence ThresholdMinimum confidence to trigger (0-1)
Example Configuration: 
Policy: GDPR Privacy
Compliant: false
Risk Level: High, Critical
Confidence: >= 0.8

​
Conditional Trigger Node

Fires based on custom field comparisons.
SettingDescription
FieldThe data field to check
OperatorHow to compare
ValueWhat to compare against
Field Categories:
PrefixExampleDescription
trace.trace.functionNameTrace properties
args.args.amountTrace arguments
metadata.metadata.userIdTrace metadata
assessment.assessment.riskLevelAssessment results
Operators:
OperatorDescription
equalsExact match
not_equalsDoes not match
containsString contains value
not_containsString doesn’t contain
greater_thanNumeric comparison
less_thanNumeric comparison
inValue in list
not_inValue not in list

​
Human Intervention Node

Creates a review task and pauses for human decision.
SettingDescription
Approvals NeededNumber of approvals required (1-10)
TimeoutSeconds to wait before timeout path
ChannelsWhere to send notifications
Channel Options:
  • Slack (with channel selection)
  • Email (with recipient list)
  • Microsoft Teams (with channel selection)
  • SMS/Text Message
Output Paths:
OutputWhen
ApprovedRequired approvals received
DeclinedAny reviewer declines
Change RequestedReviewer requests changes
ErrorTimeout or system error

​
Notification Node

Sends an alert without pausing the workflow.
SettingDescription
ChannelsWhere to send (Slack, Email, Teams, SMS)
Include Request DetailsShow trace arguments
Include Policy ResultsShow assessment data
Message TemplateCustom message text
Example: 
Channel: Slack #security-alerts
Include Details: true
Include Policy: true
Message: "High-risk trace detected: {trace.functionName}"

​
Rejection Node

Marks the trace as rejected and ends the workflow.
SettingDescription
ReasonWhy the trace was rejected
The rejection reason is logged and returned to the calling system.

​
Connecting Nodes

Nodes connect through input/output ports:
  • Triggers have one output (fires when matched)
  • Human Intervention has multiple outputs (Approved, Declined, Change Requested, Error)
  • Notification has one output (continues after sending)
  • Rejection has no outputs (ends workflow)

​
Workflow Settings

Global settings for the entire workflow:
SettingDescription
NameDescriptive name for the workflow
ActiveWhether the workflow is enabled
PriorityOrder when multiple workflows could match

​
Testing Workflows

Before activating:
  1. Create a test trace with expected data
  2. Watch the workflow execution in the dashboard
  3. Verify triggers fire correctly
  4. Check notifications arrive
  5. Confirm human intervention creates review tasks

Understanding Workflows

Learn workflow fundamentals

Decision Types

Understand approval outcomes