# Ticketing Action

Source: https://userguide.qualytics.io/flows/actions/deep-dive/ticketing/

Ticketing actions execute when a supported trigger condition is met. That happens when an anomaly is detected, or when an anomaly changes to a status the trigger is filtered to. The action then creates a ticket, or updates the status of an existing one, in the connected ticketing integration.

> **Warning: Integration Required**
>
> Ticketing actions need a connected ticketing integration. See [Ticketing Integrations](https://userguide.qualytics.io/settings/integrations/ticketing/ticketing/) for the supported trackers and how to connect one.

## Why Use a Ticketing Action

Use a Ticketing action when data quality findings should become work items in the tool the team already triages in. Common cases:

- **Start the investigation where it will happen:** A severe anomaly opens a ticket carrying its context, so triage begins in the tracker instead of in a channel message someone has to copy from.
- **Keep the tracker in sync with the anomalies:** Pair a **Create Ticket** Flow with an **Update Ticket Status** Flow on **Anomaly Status Changed**, so tickets move when the anomalies resolve.
- **Make quality work visible:** Tickets put data quality issues on the same board, with the same priorities and owners, as the rest of the team's work.

> **Info: Announcing the ticket**
>
> A notification chained after a **Create Ticket** or **Update Ticket Status** action can carry the ticket's details in its message. See [Message](https://userguide.qualytics.io/flows/actions/deep-dive/message/#message-variables) for the tokens.

> **Warning: Integration Availability**
>
> If required ticketing or notification integrations (such as Slack or Microsoft Teams) are unavailable during Flow execution, ticketing actions may not complete successfully. Execution details are logged to assist with troubleshooting and error analysis.

## See Also

- **Examples**

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

  [Examples](https://userguide.qualytics.io/flows/actions/deep-dive/examples/)
- **Best Practices**

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

  [Best Practices](https://userguide.qualytics.io/flows/actions/deep-dive/best-practices/)
- **How It Works**

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

  [How It Works](https://userguide.qualytics.io/flows/actions/deep-dive/how-it-works/)
- **Operation**

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

  [Operation](https://userguide.qualytics.io/flows/actions/deep-dive/operation/)
- **Anomaly**

  Archive or delete inactive anomalies automatically.

  [Anomaly](https://userguide.qualytics.io/flows/actions/deep-dive/anomaly/)
- **Notifications**

  The dispatch pipeline and the five channels: In App, Email, Slack, Microsoft Teams, and PagerDuty.

  [Notifications](https://userguide.qualytics.io/flows/actions/deep-dive/notifications/)
- **Message**

  The message you write, its formatting, and the dynamic tokens available per trigger type.

  [Message](https://userguide.qualytics.io/flows/actions/deep-dive/message/)
- **Workflow**

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

  [Workflow](https://userguide.qualytics.io/flows/actions/deep-dive/workflow/)

*Last updated: September 10, 2026.*
