Skip to content

Getting Started with Actions

An action is a node you chain after a Flow's trigger to define what the Flow does, such as running an operation, cleaning up anomalies, alerting a channel, calling an external system, or opening a ticket. This hub gathers everything about working with actions.

The List of Actions panel, grouping the available actions into the five categories

The Deep Dive opens with an introduction to actions and holds one hub per category (Operation, Anomaly, Notifications, Workflow, and Ticketing), each with its concept pages. The How-tos walk through configuring each action type. Editing, moving, cloning, and deleting any action on the canvas is covered in Navigate the Canvas. The API and FAQ pages cover every category in one place.

Deep Dive

  • Introduction


    What an action is, how actions run, and the five categories.

    Introduction

  • How It Works


    The action node, the five categories in detail, how actions run, and the chaining rules and limits.

    How It Works

  • Operation


    Run datastore operations (Sync, Profile, Scan, Export, Materialize) when the trigger activates.

    Operation

  • Anomaly


    Archive or delete inactive anomalies automatically.

    Anomaly

  • Notifications


    Alert a channel: In App, Email, Slack, Microsoft Teams, or PagerDuty.

    Notifications

  • Message


    The notification's body: how to write and format it, and the dynamic tokens per trigger type.

    Message

  • Workflow


    Hand the event to an external system through a Webhook, an HTTP action, or n8n.

    Workflow

  • Ticketing


    Create or update tickets in your issue tracker from anomaly events.

    Ticketing

  • Examples


    Real scenarios showing what each action category does inside a working Flow.

    Examples

  • Best Practices


    Guidelines per category for actions that do their work quietly and fail loudly.

    Best Practices

How-tos

Operation

Anomaly

Notifications

Workflow

Ticketing

  • Create a Ticket


    Open a ticket in your issue tracker when an anomaly event activates the trigger.

    Create a Ticket

  • Update Ticket Status


    Move linked tickets to a target status when an anomaly changes.

    Update Ticket Status

Reference

  • Troubleshooting


    What to check when a category is disabled, an action fails or lands as Skipped, or a notification never arrives.

    Troubleshooting

  • API


    How every action category appears in the Flow API, with the notification endpoints per channel.

    API

  • FAQ


    Common questions about each action category, with the notification channels covered per channel.

    FAQ