Skip to main content
Push alert events from your own system to Flashduty through standard protocols. :::tips Flashduty has already adapted webhook protocols for most common alert systems. For these systems, you should first use the corresponding integration for simplicity. This integration provides a standard HTTP interface that requires your development for adaptation. The advantage is that you can push any alert events you want to handle through On-call. :::

Setup steps

In Flashduty

You can obtain an integration push URL through either of the following two methods:

Use a dedicated integration

When you don’t need to route alert events to different collaboration spaces, this method is preferred as it’s simpler.
  1. Enter the Flashduty console, select Collaboration Space, and enter the details page of a space
  2. Select Configuration → Integrations → Private integration, then click Add integration, and enter the add integration page
  3. Select Standard Alert Event integration, click Save to generate a card
  4. Open the generated integration card and copy the Push URL

Use a shared integration

When you need to route alert events to different collaboration spaces based on the alert event’s Payload information, this method is preferred.
  1. Enter the Flashduty console, select Integration Center → Alert Events to enter the integration selection page
  2. Select Standard Alert Event integration:
    • Integration Name: Define a name for the current integration
  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 your system

This integration has no third-party product UI. Configuration happens in your own system and in the integration settings in Flashduty.
1

Push alert events to Flashduty from your system

Where: Your alerting system › the code or script that sends HTTP requestsPush on every state change: send Critical / Warning / Info when the alert fires and an Ok event with the same alert_key when it recovers, otherwise the alert stays open.
2

Configure field mapping in Flashduty (if your JSON does not match)

Where: Flashduty console › Integration Center › Alert Events (dedicated integration: Flashduty console › Channels › Configuration › Integrations › Private integration)In the integration list on the right, open your Standard Alert Event integration, then go to Receive › Mappings card. Its switch is at the right of the title row and is off by default; the mapping editor appears only when it is on. Configure Field mapping there.Skip this step if your system can push the payload above as is. Otherwise, use Field mapping with {{variable path}} to map fields of the original JSON to the standard fields, and configure Field value mapping (shown only after field mapping is set) when values need translating. See “Field mapping and value mapping” below for the syntax and examples.
3

Push a test event and confirm

Where: A terminal on the host of your system
A response with request_id and alert_key means the push succeeded. Return to Flashduty: the integration shows Latest event time. Then send an event with the same alert_key and event_status set to Ok to verify auto-resolve.

Request description

Request method

POST, Content-Type:“application/json”
The request body must not exceed 10 MiB; larger bodies are rejected with HTTP 413.

Request parameters:

Headers:

Query strings:

Payload:

image structure

Response

Data: Error: Code:

Request example

Request:
Successful Response:
Failed Response:

Field mapping and value mapping

If your JSON doesn’t match the standard payload above, configure field mapping and value mapping in the integration settings. Flashduty then converts your JSON into standard alert events.
Once field mapping is configured, the request body no longer requires a fixed format. It accepts any JSON object, and also supports batch push through JSON arrays (up to 100 items per request).

Field mapping (field_mapping)

Use {{variable.path}} syntax to reference fields from the original JSON and map them to target fields of the standard alert event. Supported target fields: The above is the whitelist of target fields supported by the field mapping editor in integration settings. The images field is not offered as a target in the console’s field mapping editor, so report it directly in the request payload. Variable syntax:
  • Use . to separate path levels, for example, {{data.severity}} references a nested field
  • When the entire value is a single variable (for example, "{{tags}}"), the original data type is preserved (object, array)
  • When a variable is mixed with other text (for example, "{{host}} - {{check}}"), variables are converted to strings for concatenation
Two ways to map labels:
  • Wildcard expansion: "labels": "{{tags}}" — expands all children of the tags object as labels
  • Per-label mapping: "labels": {"env": "{{tags.env}}", "host": "{{hostname}}"} — maps each label individually
Example: Your system pushes the following format:
Configure the following field mapping:

Value mapping (value_mapping)

When your source system’s field values differ from Flashduty’s standard (for example, using high instead of Critical for severity), configure value mapping for automatic conversion. Value mapping is configured per field path, with each path containing a source value → target value mapping table. Example:
With the field mapping above, field mapping extracts "severity": "high" from the original JSON. Value mapping then converts it to Critical and writes it to the event_status field.
Every {{...}} variable must resolve to a value in the original JSON, or the request fails. Test your mapping with a small dataset first.

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:

Best practices

  1. Send events to Flashduty when alert status changes
  2. When an alert recovers, send an event with status Ok to close the alert. Otherwise, the alert will remain open. If your alert system doesn’t have recovery events, we recommend manually sending recovery events
  3. Labels are event descriptions, and label content should be as rich as possible (specified when sending, or generated through enrichment rules), such as:
    • Alert source, like host, cluster, check, or metric
    • Alert ownership information, like team, owner
    • Alert category information, like class (api, db, net)

FAQ