Actions Introduction
An action is a node chained after a Flow's trigger, and it defines what the Flow actually does. Every action hangs from a parent, either the trigger or another action, and starts only after that parent succeeds. The List of Actions panel groups the available actions into five categories, and each category has its own hub in this section. How actions behave on the canvas, what each category is for, and the limits between them are covered in How Actions Work.
What You Will Find Here
-
How It Works
The action node, the five categories in detail, how actions run, and the chaining rules and limits.
-
Operation
Run datastore-level operations (Sync, Profile, Scan, Export, Materialize) automatically when the trigger activates.
-
Anomaly
Manage inactive anomalies, archiving or permanently deleting them.
-
Notifications
Send alerts to people or channels: In App, Email, Slack, Microsoft Teams, or PagerDuty.
-
Message
The notification's body: how to write and format it, and the dynamic tokens per trigger type.
-
Workflow
Hand the event to an external system through a Webhook, an HTTP action, or n8n.
-
Ticketing
Create or update tickets in your issue tracker so anomaly context reaches the team's triage workflow.
-
Examples
Real scenarios showing what each action category does inside a working Flow.
-
Best Practices
Guidelines per category for actions that do their work quietly and fail loudly.