Skip to main content
By configuring an HTTP endpoint, Flashduty issues a request on the schedule you define and parses the response into events conforming to the Standard Alert Event protocol, which are then written into the alert channel. Your system does not need to support push delivery — it only needs to expose a readable alert query endpoint.
Pull integrations run only on the Pro plan; on other plans no pull runs, including manual triggers.
:::tips HTTP Pull is the right choice when your source cannot send webhooks, is query-only by nature, or when you do not want to modify the upstream system. If your system already supports webhook delivery, prefer the corresponding push-based integration (Prometheus, Zabbix) — it has lower latency and a smaller resource footprint. :::

Setup steps

In Flashduty

Configure in Flashduty

HTTP Pull is configured entirely in Flashduty. Nothing needs to be set up in the upstream system, which only has to be reachable by Flashduty.
1

Configure the HTTP request in Flashduty

Where: Integration Center › Alert Events › HTTP Pull › HTTP request (dedicated integration: Channel › Configuration › Integrations › Private integration › Add integration › HTTP Pull)
2

Configure pagination in Flashduty (if the endpoint paginates)

Where: Integration Center › Alert Events › HTTP Pull › Pagination (dedicated integration: Channel › Configuration › Integrations › Private integration › Add integration › HTTP Pull)Many query-style endpoints cap the number of records returned per call and require cursor-based pagination to walk through the full result set. Flashduty supports cursor pagination: on each response it extracts the next-page cursor, injects it into the next request, and repeats until the cursor is missing or the page cap is reached. If the endpoint returns everything in one call, keep No pagination and skip this step.
3

Configure severity mapping in Flashduty

Where: Integration Center › Alert Events › HTTP Pull › Advanced settings › Severity mapping (dedicated integration: Channel › Configuration › Integrations › Private integration › Add integration › HTTP Pull)External systems use different field names and values for alert severity. Severity mapping translates the external value into Flashduty’s standard Critical / Warning / Info.
  • Flashduty reads the event_status field from each event in the response (the severity field defined by the Standard Alert Event protocol) and looks it up in the mapping table to find the corresponding Flashduty severity.
  • Default mapping: P1 → Critical, P2 → Warning, P3 → Info. You may remove the defaults or add any number of custom entries.
  • Fallback when no match: if the event_status value does not match any key in the mapping, it falls back to Warning.
4

Save and confirm the first event

Where: Integration Center › Alert Events › HTTP Pull › Save (dedicated integration: Channel › Configuration › Integrations › Private integration › Add integration › HTTP Pull)Click Save. A shared integration also needs a Default route (see “Default route” below), otherwise pulled events are dropped. After saving, Flashduty requests the endpoint every Pull interval (minimum 30 seconds). After one interval, return to the integration list: when the integration shows Latest event time, the pull works.

Response format

The response must conform to Flashduty’s Standard Alert Event protocol (response_mode = standard). Key fields include event_status, title_rule, alert_key, description, labels, and so on Refer to the Standard Alert Event documentation for the semantics and length limits of each field. When pagination is enabled, the response must additionally expose a field for the next-page cursor, located at the path you set in Cursor path. A typical shape:

Default route

When creating a “Shared Integration” (under Integration Center → Alert Events), you must configure a default route — otherwise newly pulled events will be dropped. After creation, you can add finer-grained rules under Route. A “Dedicated Integration” (created under Configuration → Integrations → Private integration in a specific channel) is automatically bound to that channel and does not need a separate default route.

Template variables

The URL and request body support Go template syntax. There is currently one built-in variable: Usage rules:
  • When cursor pagination is enabled, {{.PageValue}} must appear at least once in the URL (when Injection target is URL Query) or the body (when Injection target is Body) — otherwise the next-page cursor cannot take effect.
  • GET requests force Injection target to URL Query, but you still decide which query parameter the variable lives in, or you can use Parameter name to let Flashduty append it for you.
  • When pagination is None, the variable always renders as an empty string.