Overview

Send Cloudflare notifications to Callgoose SQIBS. You add SQIBS as a webhook destination, then choose it in any notification, such as origin errors, load balancing health or DDoS attacks. SQIBS opens an incident when an alert starts and resolves it when Cloudflare reports it has ended.

You need
A Cloudflare account with permission to manage notifications, and a SQIBS API token
Setup time
About 10 minutes
Result
Cloudflare alerts open and resolve SQIBS incidents

How it works

Cloudflare
Alert fires
A notification fires, such as an origin error rate alert.
Cloudflare
Sends a webhook
To a webhook destination, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
ALERT_STATE_EVENT_START opens it, ..._END closes it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose CloudFlare. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger (none) (anything) No key, so every message opens an incident.
  1. Choose the Priority for these incidents and click Save.

The template has no key, so every notification opens an incident. Cloudflare's payload carries the alert state and a correlation id for many alert types, so use these values instead:

Part Payload JSON key Key value contains What it does
Trigger "alert_event" ALERT_STATE_EVENT_START Opens an incident.
Resolve "alert_event" ALERT_STATE_EVENT_END Resolves the open incident.
Match "alert_correlation_id" Ties the end message to the incident it opened.
Title from "name" The notification name becomes the title.
Description from "text" Becomes the incident description.

Some alert types do not send alert_event. For those, keep a second filter with key "alert_type" (contains anything) so they still open incidents.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Add SQIBS as a webhook destination

  1. In the Cloudflare dashboard, go to Alerts > Destinations. In the Webhooks card, select Create.
  2. Name it Callgoose SQIBS and in URL enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=cloudflare&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Leave Secret empty and select Save and Test.

Step 3: Send notifications to SQIBS

  1. In Alerts, click Add (create notification) and choose the product and alert, for example Load Balancing health alert or Origin Error Rate.
  2. Under webhooks, choose Callgoose SQIBS, then save the notification.

Step 4: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Save and Test sends a test message; with the custom filter it is logged but does not open an incident, because it has no alert_event.
  2. Trigger a real alert, for example take a load balancer origin out of service. In SQIBS, a new incident opens. The payload looks like this (shortened):
{
  "name": "Origin health",
  "text": "Pool web-pool is unhealthy: origin web-01 is down",
  "data": {
    "pool_name": "web-pool",
    "origin_name": "web-01"
  },
  "ts": 1764000000,
  "account_id": "abc123",
  "policy_id": "3f2c9a",
  "policy_name": "Origin health",
  "alert_type": "load_balancing_health_alert",
  "alert_correlation_id": "6b3f0d5e-8c1a-4f2e-9d7b-1a2b3c4d5e6f",
  "alert_event": "ALERT_STATE_EVENT_START"
}
  1. When the origin is healthy again, Cloudflare sends ALERT_STATE_EVENT_END with the same correlation id, and SQIBS resolves the incident.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Cloudflare destination.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when Cloudflare reports an origin down, SQIBS can run a workflow that restarts the web server on that origin and checks it answers again.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: