Add a PagerDuty Notification
Add a PagerDuty notification action to a Flow to create incidents in your PagerDuty service whenever the trigger activates. For routing behavior and the concept behind the channel, see the Notifications deep dive.
Integration Required
Before using PagerDuty in Flows, you need to connect the PagerDuty integration in Settings > Integrations. See the PagerDuty Integration setup guide for instructions.
Permission Required
You need the Manager role to edit and publish Flows. See Flow Permissions for details.
Field reference
The Pager Duty Settings panel shows the following fields.
| Field | Required | Type | Description |
|---|---|---|---|
| Severity | Option | Info, Warning, Error, or Critical, with Info as the default. Each level maps to PagerDuty's severity classification, which controls urgency and notification behavior based on your service's configuration. | |
| Summary | Text | The incident summary, which PagerDuty also uses as the alert title, so it is the first thing responders read. It arrives already filled in with a one-line default written for the Flow's trigger, and dynamic tokens resolve when the Flow runs (see Message). Plain text only, Markdown formatting is not supported. PagerDuty caps the summary at 1024 characters and refuses a longer one, so avoid tokens that carry no length limit, such as {{anomaly_message}}, {{operation_message}}, and {{check_description}}. |
|
| Additional Details | Object | Key-value pairs merged into the incident's Custom Details section, on top of the details Qualytics populates automatically (datastore name, container name, check type, and so on). | |
| Routing Key Override | Text | Routes this action's events to a different PagerDuty service than the integration's default key. When left empty, the default integration key is used. |
Tip
Use the autocomplete feature (triggered by Ctrl+Space) to insert variables such as {{ flow_name }}, {{ container_name }}, and {{ datastore_name }}. The autocomplete only suggests variables that are valid for the selected Flow trigger type.
Reset to defaults
The Reset to defaults button at the top of the settings panel restores the Summary to the trigger's default and the Severity to Info. Additional Details and Routing Key Override are left exactly as you set them, because neither has a default to return to.
Steps
Step 1: Navigate to the Flows page by clicking Flows on the left side panel.
Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.
Step 3: In the List of Actions panel, pick the Notification category, then click Pager Duty. The Pager Duty Settings panel opens on the right-hand side.
Step 4: Fill in the fields.
Step 5: Click Test Notification to send a test event and confirm the configuration. A confirmation message appears when it is delivered.
Step 6: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.
Step 7: Click Publish to make the action live.
Warning
Unlike connection validation (which uses Change Events), test notifications will create an incident in your PagerDuty service.