02 · Rules
Route events without writing code.
Every routing decision is a rule stored in the platform. Compose rules in a visual builder, test them against sample payloads before activation, and govern the flow of every event between connected systems.
What you get
- No-code visual builder
- Eight condition operators
- Drag-and-drop field mapping
- Dry-run testing
- Priority ordering
- Version history
Pick source, destination, adapter.
A rule binds a source connector and event type to a destination connector and an adapter. Conditions filter which events match — equals, not_equals, contains, not_contains, greater_than, less_than, exists, not_exists — and multiple conditions combine with explicit AND or OR. Priority ordering determines which of several matching rules fires first.
Field mapping that survives schema drift.
The field mapper is a dictionary of source paths to destination paths with optional transformation templates. Source payloads are normalized into the universal envelope first; mappings operate on the normalized shape, so schema changes at the connector layer do not break downstream adapters. Unmapped fields pass through untouched unless explicitly dropped.
Dry-run before activation.
Every rule supports dry-run execution against a sample payload. The platform runs the adapter transform, surfaces the normalized and transformed shapes side by side, and reports whether the downstream delivery would succeed. Activation is a separate action — dry-runs leave no trace in the event log.
Governance, not guesswork.
Every rule edit persists to the rule version history with actor identity, diff, and UTC timestamp. Rules can be disabled without deletion to freeze a flow during incident response. The rule engine is the single source of truth for how events move through your integration fabric.
Continue reading