Create action
- Login to Flashduty console, go to Integration Center - Webhook
- Click to add Custom Action integration
- Configure Action Name—this name will appear as a button in incident details
- Configure Managing Team—select the team that manages this integration; only team members can edit the integration configuration
- Configure Channels—you can configure multiple, but each channel can have at most 5 Custom Actions
- Configure Endpoint and custom Headers
- TLS Verification is enabled by default. If the target service uses a self-signed or internal-CA certificate, turn off TLS Verification, and Flashduty skips validating the server certificate
- Save to complete
Edit a saved action
Once saved, the Endpoint and the custom Payload are shown as usual and can be edited in place. The custom Headers values are treated as secrets and are never shown back: on the detail page and in the edit form, each Header value reads as******.
Saving follows these rules:
To change a Header value, type it again. If you change the Endpoint, every Header still holding
****** must be entered again, because the saved value would otherwise be sent to the new address; the edit form points out those Headers.
Push description
Request method
POST, Content-Type:“application/json”
Request payload:
The fields of
person and incident (including Responder, AssignedTo, and Image) are the same as in Incident Webhook, with these differences:incident.alertsadditionally returns the associated alert list, described in Alert below; the field is not returned when there is no associated alert.incident.linksisn’t returned; use Incident Webhook to get it.
The alert object in custom actions has these limits:
incident,integration_ref_id, anddata_source_typearen’t returned.integration_name,integration_type,channel_name,channel_status,responder_name,responder_email,data_source_name, anddata_source_ref_idare always empty strings.data_source_idequalsintegration_id; useintegration_id.
Request response
HTTP status code 200 indicates successful push.Request example
Custom request body and value mapping
Custom actions support custom request body and value mapping the same way as Incident Webhook. Variable paths refer to fields in the request payload above. For syntax and examples, see Incident Webhook.Use cases
Restart host
When host memory or CPU is maxed out, trigger a host restart script to quickly complete the restart.Information enrichment
When an incident occurs, call back your service to fetch tracing, logging, topology, and other details for the alert. Your service then calls the Flashduty Open API to update the incident, for example by adding labels or setting custom fields.Rollback changes
When an incident occurs, if a change caused it, directly trigger a callback to your deployment platform to start the rollback process and accelerate incident recovery.Update status page
When you confirm an incident affects production services, trigger external status page updates to promptly notify your customers or upstream/downstream parties.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 (
-
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