Overview

Send Netweak website and server alerts to Callgoose SQIBS. A channel with a custom webhook destination posts each alert to your SQIBS API endpoint. SQIBS opens an incident when a website or server goes offline and resolves it when it is back online.

You need
A Netweak account, and a SQIBS API token
Setup time
About 10 minutes
Result
Netweak alerts open and resolve SQIBS incidents

How it works

Netweak
Alert fires
A website or server goes offline.
Netweak
Sends a webhook
Through a custom webhook destination, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
offline opens it, online 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 Netweak. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "server"."status" offline Opens an incident.
Resolve "server"."status" online Resolves the open incident.
Match "server"."id" Ties the resolve message to the incident it opened.
Title from "alert"."event" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

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: Create a channel with a webhook destination

  1. In Netweak, go to Channels and click Create a Channel. Name it CallgooseSQIBS and click Continue.
  2. Open the channel, click Add Destination and choose Custom Webhook.
  3. Enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=netweak&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. Click Save, then select the channel on each website or server you want in SQIBS.

Step 3: 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. Add a test website that does not answer.
  2. In SQIBS, a new incident opens. Netweak's payload looks like this:
{
  "alert": {
    "id": 9511,
    "event": "website.down",
    "threshold": null,
    "trigger_delay": 0
  },
  "server": {
    "id": "XkeeV",
    "name": null,
    "url": "https://shop.example.com",
    "status": "offline",
    "status_updated_at": "2026-11-22T10:21:01.000000Z"
  }
}
  1. When the site is back, Netweak sends "status": "online" for the same server.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 Netweak channel.

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 Netweak reports a server offline, SQIBS can run a workflow that checks the host from another network and power-cycles it through your hypervisor if it is hung.

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: