Event types
Flashduty currently supports the following event types and may add more later.Manually closing an alert does not currently trigger a Webhook callback.
Push description
Request method
POST, Content-Type:“application/json”
Request payload:
The Person and Image fields are the same as in Incident Webhook.Alert:
Legacy fields:
data_source_id, data_source_name, data_source_type, and data_source_ref_id equal integration_id, integration_name, integration_type, and integration_ref_id; use the latter. responder_name and responder_email are always empty strings; get responder info at the incident level.Incident:Request response
HTTP status code 200 indicates successful push.Request example
Configuration guide
Go to Integration Center → Webhook → Add or edit an Alert Webhook integration.Basic settings
Enter the integration name and description for easy management.Webhook settings
Only Incident Webhook and Webhook custom actions support custom request body and value mapping. An Alert Webhook always pushes the Payload structure described above and cannot reorganize it. See the Custom Request Body and Value Mapping sections of Incident Webhook.
Invocation history
Alert Webhook provides a complete invocation history, helping you troubleshoot push delivery and debug callback interfaces.View invocation history
Go to the Alert Webhook integration detail page and switch to the Invocation History tab.Filtering and search
History record fields
View invocation details
Click View Details on a record to see the complete request and response information:- Request: Includes Endpoint, Request Headers, and Request Payload
- Response: On success, shows Response Headers and Response Body; on failure, shows Error Message
FAQ
-
Is there a response timeout?
- Your service must respond within 2 seconds; Flashduty treats a slower response as a failure
-
Will pushes continue after failure?
Flashduty retries only these network errors, at most once:
- Connection or read/write timeout (
i/o timeout) - Connection closed early by the peer (
EOF)
- Connection or read/write timeout (
-
How to ensure push order?
- Flashduty pushes events for the same alert in chronological order, but retries can deliver them out of order
- Services can filter based on event_time; after receiving a later event, they can drop earlier ones. Each push carries the latest complete information, so occasional event loss is tolerable
-
Trusted IP whitelist for push source?
47.94.95.118,123.56.8.183,47.94.193.81, and1.13.19.96(SaaS only; in a private deployment, pushes originate from your own environment’s egress address — check with your infrastructure team)- We may update this list, so check it regularly