Skip to content

Flows Overview

Flows automate your data quality work on a visual canvas. Each Flow begins with a trigger that defines when it starts, followed by the actions that run once it does, such as operations, notifications, tickets, and calls to external systems. This section covers:

  • What Flows are, how the canvas works, and when each trigger activates
  • How to build, run, and manage Flows and their executions step by step
  • Each action type in depth, from concepts to step-by-step configuration

The Flows page with the Definitions tab in list view, showing each Flow with its trigger and actions, conditions, related datastores, recent runs, last triggered time, and creator

Permissions

Anyone can view Flows and their executions. Creating, editing, executing, and deleting a Flow requires the Editor team permission on every datastore it relates to, so any Member or Manager can manage a Flow on datastores they edit, or one that relates to no datastore. Admins can manage every Flow. See Flow Permissions for the full matrix.

Flow

Start here for the Flow itself. This section covers the canvas, triggers, executions, and permissions, along with the how-tos for building and running a Flow and the Flow API.

  • Flow

    The canvas, triggers, executions, and permissions, plus how-tos, API, and FAQ for building and running a Flow.

    Getting Started

Actions

The five action categories (Operation, Anomaly, Notifications, Workflow, and Ticketing) share one section, with a hub per category covering concepts, step-by-step configuration guides, API notes, and FAQ.

  • Actions

    The five action categories, each with concept pages, configuration how-tos, API, and FAQ.

    Getting Started