Skip to main content
Last9’s webhook notification channel sends PagerDuty Events API v2 JSON to the URL you enter, with fields such as event_action, dedup_key and payload. The Flashduty PagerDuty Compatible integration accepts this format, so no separate Last9 integration is needed: create a PagerDuty Compatible integration in Flashduty and paste its push URL into Last9.

In Flashduty On-call

Get an integration push URL in either of the two ways below. Choose the PagerDuty Compatible integration type in both, not Last9.

Use a dedicated integration

  1. In the Flashduty console, go to Channels and open a channel
  2. Go to Settings → Integrations → Dedicated integrations and click Add integration
  3. Select PagerDuty Compatible and click Save
  4. Open the generated integration card and copy the Push URL, in the form https://api.flashcat.cloud/event/push/alert/pagerduty?integration_key=<integration key>

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select PagerDuty Compatible and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

Configure in Last9

1

Add a webhook notification channel in Last9 and assign it to an Alert Group

Where: Last9 › Notification Channels › Add Channel › WebhookAfter saving the channel, assign it to the Alert Groups that should notify it.Last9 detects Microsoft Teams, Flock, Google Chat, Telegram, Jira and Zenduty URLs and switches to their own formats; a Flashduty push URL is not among them, so the generic format above is sent.
2

Verify trigger and recovery with a real alert

Last9’s documentation does not describe the behavior of a test button, so verify with a real alert: let it trigger and confirm the alert appears in Flashduty, then let it recover and confirm Flashduty closes it by the same dedup_key (see “Recovery and deduplication” below).After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Field mapping

Recovery and deduplication

  • When Last9 sends a notification with event_action set to resolve, Flashduty closes the alert with the same dedup_key.
  • severity must be one of critical, error, warning, info; Flashduty rejects other values.
  • trigger and acknowledge events must include payload; a resolve event with only dedup_key is accepted.
  • Last9’s documentation does not describe test-button behavior. After the first setup, verify with a real alert that both the trigger and the recovery show up in Flashduty.

Troubleshooting

  • Flashduty returns Invalid parameters: the push URL is incomplete and lacks integration_key, or the integration type is not PagerDuty Compatible
  • Alerts do not recover: confirm Last9 sent a resolve notification and that its dedup_key matches the trigger