Open an incident on a confirmed outage
The record is created once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with ServiceNow.
One integration user, and a confirmed outage opens an incident record before the first ticket about it arrives at the service desk.
What lands in ServiceNow
Everything the alert pipeline creates in ServiceNow is on this list, and nothing beyond it. Read it once and you know what your team will see.
File the recovery as its own record
The all clear arrives as a second incident carrying the time it resolved and how many minutes the site was gone.
Set urgency and impact from the severity
An outage or a slow site opens at 1, a warning or a flapping site at 2 and a recovery at 3, on both fields.
Speak the Table API
Records are created on the incident table with Basic authentication, so no scripted REST endpoint is needed on your side.
Fill in the description
URL, customer, organisation, the error with its status code, the checking locations and the times sit in the description field.
Report a failing certificate
A TLS certificate that has crossed into its critical window opens an incident of its own.
An instance per client
Each channel carries its own instance URL and credentials, so a client's outage lands in the desk that client's team actually works.
File a test incident
The dashboard creates one record marked TEST while you set the channel up, so wrong credentials are caught before the first outage.
Keep the password encrypted
The integration user's password is stored encrypted, only an https instance is accepted, and the address is checked before it is called.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Pick an integration user
Create or reuse a user that may write on the incident table, the itil role covers it.
Instance URL
yourcompany.service-now.comCredentials stored encrypted
2. Enter instance and credentials
Add the instance URL together with the user name and password the integration should authenticate with.
3. Save and test
Assign the monitors the channel covers and file the test incident, so the first real outage is not the first attempt.
Before you connect ServiceNow.
Enough to create a record on the incident table, which the itil role covers. Nothing else is called, so the account does not need admin rights.
No. The recovery is filed as its own record rather than closing the first one, so the outage keeps its work notes and whatever state your desk moved it to.
From the severity, on both fields at once. An outage or a slow site opens at 1, a warning or a flapping site at 2, and a recovery at 3.
No. Your quota covers monitors and the monthly SMS and voice allowance. Records created in ServiceNow, Jira or GitHub do not draw on it.
The password is stored encrypted in the channel configuration. Only an https instance URL is accepted, and the address is resolved and checked against internal and loopback targets before any request is sent.
Every alert, where your team already works.
Connect ServiceNow once, and every confirmed outage opens an incident before the first ticket about it arrives.