Actions
Action nodes define what a Flow does after its trigger activates. They execute the work that follows the trigger, and each Flow can chain multiple actions (operations, notifications, ticketing, and more) to run in sequence and automate downstream tasks.
Adding an action opens the List of Actions panel on the right-hand side, which groups the available actions into five categories; selecting an already configured action opens its own settings instead. Each category has its own section, with concept pages, step-by-step guides, API notes, and FAQ; the table links to each one.
How Actions Run
Every action hangs from a parent, either the trigger or another action, and starts only after that parent succeeds. Several actions can share the same parent; each branch then continues independently. When an action fails, the actions downstream of it are marked Skipped instead of running, so one broken step does not cascade into the rest of the chain.
In each run, every action records its own result (Pending, Running, Success, Failure, Skipped, or Aborted), visible on the execution's read-only graph along with the exact configuration the action had at that moment. See Flow Executions.
Info
Inline summaries are shown within action nodes, displaying key details depending on the action type. For example, datastore names for operations, Slack or Teams channels for notifications, and webhook URLs for HTTP actions. This provides quick clarity during flow configuration.
Action Categories
| Category | Description |
|---|---|
| Operation | Run datastore-level operations automatically when the trigger activates. |
| Anomaly | Apply lifecycle changes to anomalies returned by the trigger, for example cleaning up inactive or resolved findings. |
| Notification | Send alerts to people or channels so the right audience hears about the event. |
| Workflow | Hand off the event to an external system through outbound integrations and trigger downstream automation outside Qualytics. |
| Ticketing | Create or update tickets in your issue tracker so anomaly context flows directly into the team's existing triage workflow. |
Warning
The Ticketing category is only selectable when the flow's trigger is Anomaly Detected or Anomaly Status Changed, and only on a node that hangs from the trigger itself. Otherwise the category still appears in the panel but is disabled.
Warning
Notification and Workflow actions cannot be followed by any other action. When the previous Action node belongs to one of these categories, every category in the panel is disabled and no further actions can be chained.
Info
A single flow can include up to 10 Operation actions. Once that limit is reached, the Operation category is disabled in the panel until one of the existing Operation actions is removed. The other categories are not subject to this cap.
See Also
-
Executions
The Definitions and Executions tabs, execution states, and the read-only execution graph.
-
Examples
Real scenarios showing how a trigger and a chain of actions combine into a working automation.
-
Best Practices
Guidelines for building Flows that stay quiet when healthy and loud when something breaks.
-
Permissions
The user roles behind viewing, building, executing, and deleting Flows.
-
How It Works
The canvas, Flow settings, chaining rules, and the publish lifecycle behind every edit.
-
Triggers
The six trigger types, schedule configuration, and the filter conditions each type supports.