Skip to main content
Push alert events from Nightingale (n9e) or Flashcat to Flashduty through webhook. When an alert is triggered, send a trigger event to Flashduty; when an alert recovers, send a recovery event to Flashduty. From Nightingale/Flashcat v8.0.0-beta.7 (inclusive), you can pick a channel directly in the alert notification rules and no longer need routing rules. Earlier versions push through a webhook callback URL and need routing rules in Flashduty.

Prerequisites

  • You must have permission to modify System Settings → Global Notifications or Alert Management → Alert Rules
  • Your Nightingale server must be able to access the domain api.flashcat.cloud

Get the push URL in Flashduty

You can get the push URL in either of the following ways.Choose this option if all alerts go to one channel. It’s the simpler setup.
  1. Log in to the Flashduty console, select Channels, and open the target channel’s details page
  2. Select Configuration → Integrations → Private integration, click Add integration, select the Nightingale/Flashcat integration, and click Save
  3. Open the generated integration card and copy the Push URL
  4. (Optional) Click Edit and enter the Nightingale console domain in Console URL. Flashduty then adds a Nightingale details link to new alerts

Use a shared integration

Choose this option when you need to route alerts to different channels based on the alert payload.
  1. Log in to the Flashduty console and select Integration Center → Alert Events
  2. Select the Nightingale/Flashcat integration and fill in:
    • Integration Name: a name for this integration
    • Console URL: (optional) the Nightingale console domain
  3. Configure the default route and select a channel. You can add more rules on the Routing page later
  4. Click Save and copy the generated Push URL

Configure Nightingale/Flashcat

1

Add the Flashduty push URL in Nightingale

Where: Nightingale › Notification › Notification Channels › FlashDutyIn some v8 versions, Notification Channels is under the Alerting menu.Click Save.Adding the FlashDuty notification channel in Nightingale
2

Create a notification rule for Flashduty in Nightingale

Where: Nightingale › Notification › Notification Rules › AddOnly v8.0.0-beta.7 and later need this step. Skip it on earlier versions.Create the channels in Flashduty first and configure their escalation rules. Click Save.Configuring a notification rule in Nightingale
3

Link alert rules to Flashduty in Nightingale

Where: Nightingale › Alert Management › Alert Rules › Add or edit › Notification settingsSelect the notification rule from the previous step and click Save.Selecting the notification rule in a Nightingale alert rule
4

Send a test notification from Nightingale and confirm

Where: Nightingale › Notification › Notification Rules › your rule › Notification TestOn v8.0.0-beta.7 and later, click Notification Test and select a historical alert event to send. Earlier versions have no such entry, so wait for a new alert to fire.After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

No-event detection

The No-event detection card creates a Warning alert when no valid event arrives within the set time. Its switch is at the right of the card’s title row and is off by default; when off, the card is a single row with no other options. When it is on, the card shows these options:

Status and severity

Nightingale/Flashcat to Flashduty alert severity mapping:

FAQ

In Flashduty
  1. Check the latest event time: if the integration shows no Latest Event Time, Flashduty hasn’t received any pushes. Check the Nightingale side first.
  2. Check routing rules: if you use a Shared Integration, confirm that you’ve configured Routing Rules. Without routing rules, the system rejects new pushes.
In Nightingale/Flashcat
  1. Confirm that alerts were generated: go to Alert Management → Alert History and check for new alerts in Triggered status created after you configured the webhook.
  2. Check the callback URL: open the alert details and check that the Callback URL exactly matches the Flashduty push URL.
  3. Check network access: log in to the Nightingale server and confirm it can reach the api.flashcat.cloud domain.
  1. Check error logs: if the network is fine, look for related errors in the server logs.
If you still can’t find the cause, contact Flashduty support.
Check the following:
  1. The Nightingale alert rule sends recovery notifications
  2. The recovery event uses the same webhook callback URL as the trigger event
  3. The alert’s unique identifier (fingerprint) stays the same between trigger and recovery
You can test it this way:
  1. Trigger a test alert in Nightingale manually
  2. After a few seconds, check whether the Latest Event Time in the Flashduty integration list updates
  3. Open the channel and confirm that the matching incident was created