Overview

Send Cisco Meraki alerts to Callgoose SQIBS. You add SQIBS as a webhook HTTP server in the Meraki dashboard and choose it as an alert recipient. SQIBS opens an incident for each alert, for example an access point or appliance going offline.

You need
A Meraki network with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Meraki alerts open SQIBS incidents

How it works

Meraki
Alert fires
A device goes offline or another alert fires.
Meraki
Sends a webhook
Meraki posts the alert to the webhook HTTP server, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the alert type.

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. Add a filter with these values (there is no built-in Meraki template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "alertLevel" critical Opens an incident for critical alerts.
Title from "alertType" Becomes the incident title.
Description from "deviceName" The device name becomes the description.
  1. Choose the Priority for these incidents and click Save.

Meraki sends the coming-back-up alert as a separate alert type. To resolve automatically, add a Resolve filter on that alert type, matched on "deviceSerial", after checking the real message in the API log.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

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 in Meraki

  1. In the Meraki dashboard, open Network-wide > Configure > Alerts.
  2. Under Webhooks, add an HTTP server named Callgoose SQIBS with your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=meraki&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 the payload template on the default (Meraki JSON). Click Send test webhook.
  2. In the alert settings, choose the alerts you want and add the Callgoose SQIBS webhook as a recipient (to all alerts under Default recipients, or per alert). Save.

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. Click Send test webhook, or unplug a lab access point.
  2. In SQIBS, a new incident opens, titled with the alert type. Meraki's payload looks like this (shortened):
{
  "version": "0.1",
  "sentAt": "2026-11-22T10:15:00.000000Z",
  "organizationName": "Example",
  "networkName": "Head office",
  "deviceSerial": "Q2XX-XXXX-XXXX",
  "deviceName": "AP-Floor2",
  "alertId": "643451796765984937",
  "alertType": "APs went down",
  "alertTypeId": "stopped_reporting",
  "alertLevel": "critical",
  "occurredAt": "2026-11-22T10:13:00.000000Z",
  "alertData": {}
}

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 Meraki webhook.

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 Meraki reports an access point down, SQIBS can run a workflow that power-cycles its PoE switch port through the Meraki API.

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: