UptimeRobot

Overview

This document provides a detailed guide to integrating UptimeRobot with Callgoose SQIBS for real-time Incident Management, uptime-based alerting, and automated incident resolution.

The integration uses UptimeRobot Webhook Alerts to send monitor status change events directly to Callgoose SQIBS, where API Filters convert those events into incidents that are automatically created and resolved based on monitor state.

Prerequisites

Before beginning, ensure you have the following:

• A Callgoose SQIBS account with permissions to create API Filters and access the integration endpoint
• An UptimeRobot account (Team plan or higher recommended for webhook alerts)
• A valid Callgoose API token and Api endpoint URL.
• At least one UptimeRobot monitor (HTTP(s), Ping, Port, or Keyword)
• A test monitor or controlled downtime scenario for validation

1. Prepare Callgoose: Obtain Endpoint and Token

1.1 Retrieve Callgoose API Endpoint

Generate or locate your Callgoose process endpoint:

https://****.callgoose.com/v1/process?from=UptimeRobot&token=xxxx

• Store the API token securely
• Never expose or commit the token to source control

2. Configure UptimeRobot Webhook

2.1 Choose the Webhook Scope

UptimeRobot webhooks are configured at the Alert Contact level.

Navigate to:

UptimeRobot Dashboard → My Settings → Alert Contacts → Add Alert Contact

Select Webhook as the alert type.

2.2 Configure Webhook Fields

Set the following options:

• Friendly Name: Callgoose SQIBS
• Webhook URL:Callgoose endpoint from Step 1
• HTTP Method:POST
• Content Type:application/json

Recommended Webhook Payload

{
  "monitorID": "*monitorID*",
  "monitorName": "*monitorName*",
  "monitorURL": "*monitorURL*",
  "alertType": "*alertType*",
  "alertDetails": "*alertDetails*",
  "alertFriendlyName": "*alertFriendlyName*",
  "alertTime": "*alertTime*"
}

Save and enable the webhook alert contact.

2.3 Attach Webhook to Monitors

1. Go to Monitors
2. Edit the desired monitor(s)
3. Under Alert Contacts, select Callgoose SQIBS
4. Save changes

3. Example UptimeRobot Payloads

Monitor Down (Trigger)

{
  "monitorID": "789456123",
  "monitorName": "Production Website",
  "monitorURL": "https://example.com",
  "alertType": "1",
  "alertDetails": "Timeout while connecting",
  "alertTime": "2025-10-01 12:05:00"
}

Monitor Up (Resolved)

{
  "monitorID": "789456123",
  "monitorName": "Production Website",
  "alertType": "2",
  "alertTime": "2025-10-01 12:15:22"
}

Inspect your actual payloads inside Callgoose API Logs and map filters using real field names.

4. Create API Filters in Callgoose SQIBS

Callgoose API Filters convert incoming UptimeRobot webhook events into incidents.

Create two filters:

• Trigger Filter (create incident)
• Resolve Filter (auto-resolve incident)

4.1 Trigger Filter — Create Incident

Use the following settings:

• Payload JSON Key: "alertType"
• Key Value Contains: 1
• Map Incident With: "monitorID"
• Incident Title: "monitorName"
• Incident Description: "alertDetails "(optional)

This filter creates an incident whenever a UptimeRobot monitor goes DOWN.

4.2 Resolve Filter — Auto-Resolve Incident

Use the following settings:

• Payload JSON Key: "alertType"
• Key Value Contains: 2
• Incident Mapped With: "monitorID"

This ensures the incident is automatically resolved when the monitor comes UP.

Refer to the API Filter Instructions and FAQ for more details.

5. Verify and Test the Integration

5.1 Test Initial Delivery

• Create a temporary test filter in Callgoose
• Trigger a manual downtime or pause a monitor
• Confirm payload reception in Callgoose API Logs

5.2 View Exact Payload

Use Callgoose’s API Request Logs to inspect the exact JSON received.

Always copy field names directly from logs when configuring filters.

5.3 Final Verification

• Bring a monitored service DOWN → Incident should be created
• Restore service UP → Incident should be auto-resolved
• Confirm correct mapping using monitorID

6. Troubleshooting

Incoming Payload Not Received

• Verify webhook URL and token
• Confirm alert contact is attached to the monitor
• Check UptimeRobot alert delivery logs
• Ensure HTTPS connectivity

Incidents Not Auto-Resolving

• Confirm alertType = 2 is received
• Ensure resolve filter uses the same monitorID
• Verify no conflicting filters exist

Duplicate Incidents

• Ensure monitorID is used as the deduplication key
• Avoid creating multiple trigger filters for the same payload

Wrong or Missing Payload Fields

• Inspect live webhook payloads in Callgoose API Logs
• Update filters to match exact key names
• Re-test with DOWN and UP conditions

7. Conclusion

Integrating UptimeRobot with Callgoose SQIBS enables automated incident creation and resolution for uptime monitoring events.

By forwarding UptimeRobot webhook alerts into Callgoose and mapping them through API Filters, teams gain instant visibility into service outages while ensuring incidents close automatically once services recover.

This integration provides a clean, reliable incident lifecycle for website availability, API uptime, and network monitoring use cases.

• Callgoose SQIBS API Token Documentation
• Callgoose SQIBS API Endpoint Documentation
• API Filter Instructions and FAQ
• How to Send API
• uptimeRobot decumentation