Flow Introduction

A Flow is an automation you build on a visual canvas: a trigger that defines when it starts, followed by the actions that run once it does. This deep dive is the reference for the concepts behind Flows. Here you will find what a Flow is and why to use one, how the canvas, its nodes, and the publish lifecycle work, when each of the six trigger types activates, which actions a Flow can run, how executions are tracked, and who can do what.

Why Use a Flow

A Flow takes repetitive data quality work off your hands. When its trigger activates, the platform runs the actions you chained, in order, with no one starting anything by hand.

Use a Flow to:

• Chain routine operations: Run a Profile after every successful Sync, or a Scan on a schedule, without anyone remembering to start it.
• Alert the right channel: Send an in-app, email, Slack, Microsoft Teams, or PagerDuty message the moment a matching event happens.
• Open work automatically: Create or update tickets from anomaly events, so investigation starts in the tool the team already uses.
• Hand events to other systems: Call a webhook or HTTP endpoint, or start an n8n workflow, carrying the event's context.
• Keep anomalies tidy: Archive or delete anomalies that have gone inactive, on the cadence you choose.
• Audit every run: Review each run's status, timing, and per-action results on the Executions tab.

What You Will Find Here