Skip to main content

Overview

Rule webhook events allow you to receive real-time notifications when compliance or business rules are triggered for entities in the Gu1 platform. These events enable you to automate compliance actions, alert your team, and maintain audit trails when risk conditions are detected.

Why Use Rule Events?

Real-Time Compliance

Get instant alerts when risk rules are triggered

Automated Actions

Automatically block, flag, or escalate entities

Audit Trail

Track all rule triggers for compliance reporting

Risk Management

Respond to high-risk conditions immediately

Available Events

rule.triggered

The rule.triggered event is fired when a compliance or business rule evaluates to true for an entity. When it fires:
  • A rule condition is met during entity creation or update
  • Periodic rule evaluation detects a match
  • Transaction monitoring rules identify suspicious activity
  • Compliance checks (PEP, sanctions, adverse media) return positive matches
Filters available:
  • ruleIds: Only receive events for specific rules
  • ruleSeverity: Filter by severity level (low, medium, high, critical)
  • entityTypes: Filter by entity type

Event Payload

rule.triggered Payload

Key Payload Fields

string
Unique identifier of the triggered rule
object
Complete rule information including name, description, severity, and category
string
Severity level: low, medium, high, or critical
string
The entity that triggered the rule
object
Complete entity information including your externalId
string
Unique identifier for this rule evaluation
object
Data that caused the rule to trigger, including matched criteria and risk scores
object
Action taken as a result of the rule trigger (optional)
string
Action type: block, flag, review, alert, or none
boolean
Whether the action was taken automatically by Gu1

Rule Categories and Examples

Geographic Risk Rules

Triggered when entities are from high-risk countries or jurisdictions:

PEP (Politically Exposed Person) Rules

Triggered when entity matches PEP databases:

Sanctions Screening Rules

Triggered when entity appears on sanctions lists:

Transaction Monitoring Rules

Triggered by suspicious transaction patterns:

Adverse Media Rules

Triggered when negative news is found:

Filter Configuration

Filter by Rule ID

Only receive events for specific rules:

Filter by Severity

Only receive high and critical severity alerts:

Filter by Entity Type

Only receive rules triggered for persons:

Combined Filters

Combine multiple filters for precise control:

Code Examples

Node.js - Handling Rule Events

Python - Handling Rule Events

Use Cases

Use Case 1: Automated Compliance Actions

Automatically block high-risk entities:

Use Case 2: Risk Scoring and Monitoring

Update entity risk scores based on rule triggers:

Use Case 3: Regulatory Reporting

Generate reports for regulatory compliance:

Best Practices

Always log rule triggers for compliance audit trails:
Implement different workflows based on severity:
  • Critical: Immediate blocking + urgent alerts
  • High: Flag for review + notify compliance team
  • Medium: Queue for periodic review
  • Low: Log only + aggregate reports
Use evaluation ID to prevent duplicate processing:
Route alerts based on rule category:
Allow marking false positives for rule tuning:

Troubleshooting

Check:
  • Webhook is subscribed to rule.triggered event
  • Rules are active in Gu1 dashboard
  • Filters match the rule properties
  • Entity type matches your filters
Test: Create a test entity that should trigger a rule and verify the webhook fires.
The triggerData structure varies by rule type and category. Not all fields will be present for all rules.Example: A geographic risk rule won’t have pepStatus, while a PEP rule won’t have sanctionList.
The action field is optional. Some rules may only trigger alerts without automatic actions:

Next Steps

Entity Events

Handle entity lifecycle events

KYC Events

Process KYC verification events

Webhook Security

Secure your webhook endpoints

Configuration

Configure webhook settings