Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Configure incident custom actions, allowing you to quickly call external interfaces during incident troubleshooting to achieve self-healing, information enrichment, or any custom operations.

Create action

  1. Login to Flashduty console, go to Integration Center - Webhook
  2. Click to add Custom Action integration
  3. Configure Action Name—this name will appear as a button in incident details
  4. Configure Managing Team—select the team that manages this integration; only team members can edit the integration configuration
  5. Configure Channels—you can configure multiple, but each channel can have at most 5 Custom Actions
  6. Configure Endpoint and custom Headers
  7. 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
Disabling TLS certificate verification may expose you to man-in-the-middle attacks. Only disable it in test environments or when using self-signed certificates.
  1. Save to complete
Each channel can have a maximum of 5 custom actions. You can’t select a channel that has reached this limit when adding a custom action.

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.alerts additionally returns the associated alert list, described in Alert below; the field is not returned when there is no associated alert.
  • incident.links isn’t returned; use Incident Webhook to get it.
Alert:The alert object in custom actions has these limits:
  • incident, integration_ref_id, and data_source_type aren’t returned.
  • integration_name, integration_type, channel_name, channel_status, responder_name, responder_email, data_source_name, and data_source_ref_id are always empty strings.
  • data_source_id equals integration_id; use integration_id.
event_detail (fixed structure for i_custom):

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

  1. Is there a response timeout?
    • Your service must respond within 2 seconds; Flashduty treats a slower response as a failure
  2. 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)
    Flashduty doesn’t retry when the request was sent and the wait for response headers timed out.
  3. Trusted IP whitelist for push source?
    • 47.94.95.118, 123.56.8.183, 47.94.193.81, and 1.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