Menu

Mattering Automations StatusCake integration

Connect StatusCake to Mattering Automations: uptime, SSL, pagespeed and heartbeat checks, maintenance windows, contact groups and monitoring locations as workflow steps, authorized with a single API token.

The Mattering Automations StatusCake integration puts StatusCake API version 1.2.0 on your automation canvas: list, read, create, update and delete uptime checks, SSL certificate checks, pagespeed checks, heartbeat checks, maintenance windows and contact groups, read the run history, status periods and alert history behind an uptime check, read a pagespeed check's measurement history, and list the monitoring locations StatusCake runs checks from. Thirty six nodes in total, eighteen that read and eighteen that act, which is one node per operation the API defines.

The credential is a single API token. You generate it in the StatusCake account panel, paste it into one field in Connectors, and click Test Connection. There is no account id, no key and secret pair, and no region to choose. There is also nothing to scope: StatusCake documents no token scopes and no read-only tokens, so the token you paste can reach every node in this guide, including the six deletes.

Two things are worth reading before you build. First, this integration has no trigger nodes, so nothing here listens for a StatusCake alert; StatusCake's own alerting webhooks are a StatusCake feature configured in StatusCake, and workflows in this integration run on a schedule or on a trigger from another connector and read. Second, StatusCake sells domain monitoring on its plan page and its API has no domain surface at all, so domain expiry is not something this integration can reach. Both are explained below, and this guide ends with the complete node reference.

Before you start

  • A StatusCake account. The free tier is listed on StatusCake's pricing page as 10 uptime monitors, 5 minute test intervals, 1 page speed monitor, 1 domain monitor, 1 SSL monitor and alerts through integrations. Plan limits surface as rejected creates rather than as blocked endpoints, so an account at its check limit answers a healthy 200 on every read and a 4xx on create.
  • An API token generated in the StatusCake account panel at app.statuscake.com/User.php, which is where StatusCake documents tokens being viewed and managed. Treat it as a full-account credential: StatusCake's documentation describes no scopes, no read-only tokens and no per-resource tokens.
  • An awareness of which features your plan includes, because the API does not tell you. StatusCake's pricing page lists mixed content alerts, certificate scores and custom locations from its Superior tier, so the corresponding fields on an SSL check can come back empty and the regions field on an uptime check may be ignored or rejected on an account without them. Heartbeat checks and maintenance windows are not named on the pricing page in any tier, so their plan availability is not something we can state.
  • A plan for how many calls a workflow makes. StatusCake's rate limiting guide documents 60 requests per minute for accounts without a subscription or on a free plan, no per-minute limit for paid subscriptions, and a burst limit of 5 requests per second for all accounts, free or otherwise.
  • A Mattering workspace with access to the Automations app.

Generate a StatusCake API token

StatusCake authenticates with a single API token sent as an Authorization Bearer header on every request, over HTTPS. There is one field to fill in and nothing to configure alongside it. The decision that carries weight is not which permissions to grant, because there are none to choose from, but who and what gets to hold the token.

Sign in to StatusCake and open the account panel at app.statuscake.com/User.php, which is where StatusCake documents API tokens being viewed and managed.
Generate a token and copy it somewhere safe for the length of the next step. StatusCake's authentication guide is explicit that API tokens must be kept private, and that in the event one is exposed a new one should be generated rather than the old one reused.
A StatusCake token is a full-account credential. StatusCake's documentation describes no token scopes, no read-only tokens and no per-resource tokens, so anything holding this token can reach every node in this integration, including the six that delete checks, windows and contact groups permanently. Keep write and delete nodes behind a condition or an approval step in any agent-facing workflow.
Decide which StatusCake account holds the connection before you generate the token. Unattended automations keep running on it, so an account the team controls beats an individual's personal login, and rotating the token later is a single replacement in one place rather than a hunt through workflows.

Connect StatusCake to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose StatusCake from the list.
Click Create new credential, paste the token into the token field, name the credential something a colleague will recognise, and save it.
The token is stored encrypted in Google Secret Manager and is registered for redaction on every execution, so it does not appear in workflow logs. Revoking or regenerating the token in the StatusCake account panel ends the connection immediately.
Click Test Connection. Mattering calls the uptime check lister with a limit of one, the smallest read available on the account. A 401 means the token is wrong, was revoked, or was regenerated in StatusCake without being updated here.
A passing connection test proves less than it looks. It is a read with no body, so it exercises none of the form encoding every write depends on, and it touches only the uptime family. SSL, pagespeed, heartbeat, maintenance window and contact group nodes are separate paths, and it says nothing about whether your plan has room to create another check.
All 36 StatusCake nodes appear in your canvas palette.

Verify it works

Open any automation canvas and check the palette: a StatusCake section should list eighteen read nodes and eighteen action nodes. Drop StatusCake: List Uptime Checks onto the canvas and run a test step without configuring anything. It needs no parameters, it is the cheapest read on the account, and it returns each check with its current status, type, check rate, tags, contact groups and uptime percentage. Every uptime check picker in this integration is populated from this same node, so a successful run here is also a prediction that the pickers will work.

Open the check picker on a node such as StatusCake: Get Uptime Check and confirm it populates with check names grouped by check type, each showing the URL or host it watches underneath. That second line is doing real work: two checks can legitimately share a name and differ only in what they watch, so the URL is what tells them apart. If the picker is empty, run its source lister on its own before suspecting the picker.

Read one check in full with StatusCake: Get Uptime Check to see the shape the rest of the integration returns. StatusCake wraps its payloads in its own data key and the connector envelope adds one more, so a single resource is at data.data and a list is at data.data with the paging figures alongside it at data.metadata. Everything in this verify path is read-only and safe to re-run whenever you want to check the connection.

Node reference

36 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 18

StatusCake: Get Contact Group

statuscake_get_contact_group

Get one contact group with its full recipient list: email addresses, mobile numbers, connected integration ids and the ping URL. Read the group with this before updating it, because every list on a contact group is replaced wholesale on update rather than appended to.

StatusCake: Get Heartbeat Check

statuscake_get_heartbeat_test

Get one heartbeat check with its push URL, the period allowed between check-ins, when it was last pinged, its current status, contact groups and tags. This is how a workflow that has just created a heartbeat check retrieves the URL to hand to the job, since the create call returns only an id. The URL contains the check's push key, so pass it through a secret rather than logging or emailing it.

StatusCake: Get Maintenance Window

statuscake_get_maintenance_window

Get one maintenance window with its start and end times, the timezone those times are read in, how often it repeats, its current state and the exact list of uptime checks and tags it covers. Read the window with this before updating it, because the checks and tags lists are replaced wholesale on update.

StatusCake: Get Pagespeed Check

statuscake_get_pagespeed_test

Get one pagespeed check with its configuration, the monitoring location it runs from and its latest recorded load time, page size and request count. Read a check with this before updating it so an update only changes what you meant to change.

StatusCake: Get SSL Check

statuscake_get_ssl_test

Get one SSL check with the full certificate picture: issuer, valid from and valid until dates, cipher suite and scores, the flag block saying whether the certificate is broken, expired, revoked, missing or extended validation, and the list of mixed content resources found on the page. Use the flags object rather than parsing certificate_status text when branching a workflow.

StatusCake: Get Uptime Check

statuscake_get_uptime_test

Get one uptime check in full: its type and target, check rate and timeout, the monitoring locations assigned to it, the string match and status codes it treats as failure, its contact groups and tags, when it last ran, where it runs next and its current status. Read a check with this before updating it so an update only changes what you meant to change.

StatusCake: List Contact Groups

statuscake_list_contact_groups

List the contact groups on the account with the email addresses, mobile numbers, third-party integration ids and ping URL each one alerts. Every check type in this connector attaches its alerting by contact group id, so this is the node that populates those pickers and the place to look when a check is up and down as expected but nobody is being told.

StatusCake: List Heartbeat Checks

statuscake_list_heartbeat_tests

List the heartbeat checks on the account: the ones your own cron jobs and workers check IN to, rather than the ones StatusCake reaches out to. Each row carries the allowed period between check-ins, the current status, tags, contact groups and the push URL the job calls. Treat that URL as a secret: it embeds the check's push key, so anything that can call it can mark the job healthy.

StatusCake: List Maintenance Windows

statuscake_list_maintenance_windows

List the maintenance windows on the account with their start and end times, timezone, repeat interval, current state and which uptime checks or tags they cover. Filter by state to answer the two useful questions separately: active tells you what is suppressing alerts right now, pending tells you what is scheduled.

StatusCake: List Pagespeed Check History

statuscake_list_pagespeed_test_history

Every recorded run of one pagespeed check: when it ran, the load time in milliseconds, the page size in kilobytes, the request count, the simulated connection speed and a link to the saved HAR file for that run. StatusCake also computes the minimum, maximum and average of each measure ACROSS THE WHOLE REQUESTED WINDOW and returns them at data.metadata.aggregates, which is the number to quote for a period: recombining the per-run rows yourself gives a different and usually wrong answer, because these are per-run measurements rather than quantities that add up.

StatusCake: List Pagespeed Checks

statuscake_list_pagespeed_tests

List the pagespeed checks on the account with the latest recorded load time, page size and request count for each, plus whether the last run breached one of its alert thresholds and what the issue was. The latest_stats block is a snapshot of the most recent run only; use StatusCake: List Pagespeed Check History for a series.

StatusCake: List Pagespeed Monitoring Locations

statuscake_list_pagespeed_locations

List the servers StatusCake runs pagespeed checks from, with each one's region, region code, IP addresses and current status. Useful for allowlisting the addresses and for seeing which testing servers are healthy. Note these region codes are NOT the values the region field of a pagespeed check takes: that field uses its own eleven-code vocabulary (AU, CA, DE, FR, IN, JP, NL, SG, UK, US, USW), which is why the create and update nodes do not offer this list as a picker.

StatusCake: List SSL Checks

statuscake_list_ssl_tests

List the SSL certificate checks on the account with each certificate's issuer, validity dates, cipher, scores, mixed content findings and the alert thresholds configured for it. This is the node that answers what is about to expire: read data.data[].valid_until and compare it to now. Certificate scores and mixed-content detail are documented as paid-plan features, so those fields can be empty on a free account even though the check itself runs.

StatusCake: List Uptime Check Alerts

statuscake_list_uptime_test_alerts

The alerts StatusCake actually sent for one uptime check, with the status that triggered each one, the HTTP status code seen and when it fired. Use it to answer whether anyone was told, which is a different question from whether the site was down: confirmation servers and the trigger rate delay mean a short outage can appear in the periods list with no alert here at all.

StatusCake: List Uptime Check History

statuscake_list_uptime_test_history

Every individual run of one uptime check: when it ran, which monitoring server ran it, the status code that came back and the load time in milliseconds. Walk backwards through the series with before, or bound a period with before and after together, both as UNIX timestamps in seconds. Load time is a per-run measurement, so read the rows or chart them; adding them up means nothing and averaging them across days is only valid when each day contributed the same number of runs.

StatusCake: List Uptime Check Periods

statuscake_list_uptime_test_periods

The up and down periods of one uptime check: when each period started, when it ended and how long it lasted in milliseconds. This is the outage log rather than the raw run log, so it is the right source for a downtime report. Two things to know before doing arithmetic on it: a period that is still running has no end and no duration yet, and a period is filed under the moment it STARTED, so a window that cuts through an outage sees either all of it or none of it.

StatusCake: List Uptime Checks

statuscake_list_uptime_tests

List the uptime checks on the account with each one's current status, type, check rate, tags, contact groups and uptime percentage. This is the node the rest of the StatusCake connector leans on: uptime check pickers are populated from it and it is the cheapest way to confirm a credential works. Note that the uptime figure here is a percentage with no denominator in the payload, so it can be read and compared but never summed or averaged across checks.

StatusCake: List Uptime Monitoring Locations

statuscake_list_uptime_locations

List the servers StatusCake runs uptime checks from, with each one's region, region code, IPv4 and IPv6 addresses and whether it is currently up. Two uses: the region codes are the values the regions field of an uptime check takes, and the IP addresses are what you allowlist in a firewall so the checks are not blocked. Several servers share one region code, so the list is longer than the list of regions.

Action nodes 18

StatusCake: Create Contact Group

statuscake_create_contact_group

Create a contact group: the named bundle of email addresses, mobile numbers, integrations and a ping URL that checks alert through. Only the name is required, so a group can be created empty and filled later, but a check attached to an empty group alerts nobody. Returns only the new group's id at data.data.new_id, which is what you pass to the contact_groups field of any check.

StatusCake: Create Heartbeat Check

statuscake_create_heartbeat_test

Create a heartbeat check: a check that goes down when your own job STOPS calling in, which is how you monitor a cron job, a backup or a queue worker that nothing outside can reach. Set period comfortably longer than the job's normal interval so a slow run does not alert. The response carries only the new id, so follow with StatusCake: Get Heartbeat Check to read the push URL the job needs to call.

StatusCake: Create Maintenance Window

statuscake_create_maintenance_window

Create a window during which alerting is suppressed for the uptime checks it covers, one-off or repeating daily, weekly, fortnightly or monthly. Two things decide whether it does what you meant. First, the times are read as LOCAL time in the timezone field and any UTC offset in the timestamps is ignored, so the timezone is not decoration. Second, at least one of tests or tags must be given or the window covers nothing at all. Only uptime checks can be covered: SSL, pagespeed and heartbeat checks keep alerting straight through a maintenance window.

StatusCake: Create Pagespeed Check

statuscake_create_pagespeed_test

Create a pagespeed check that measures one page's load time, size and request count on a schedule from a chosen region. The three alert thresholds are all opt-in: a value of 0 means that alert is off, which is the default for all three, so a check created without them measures and never alerts. Returns only the new check's id at data.data.new_id.

StatusCake: Create SSL Check

statuscake_create_ssl_test

Create an SSL certificate check for an https URL. The one field that catches people is alert_at: it must be a list of EXACTLY three numbers of days, such as [1, 7, 30], and any other length is rejected. SSL checks have no name in this API, so the URL is how they are identified everywhere. Returns only the new check's id at data.data.new_id.

StatusCake: Create Uptime Check

statuscake_create_uptime_test

Create an uptime check of any of the seven supported types. The test_type field decides which of the other fields apply: HTTP and HEAD watch a URL, PING and TCP watch a host, DNS compares returned records against dns_ips, and SMTP and SSH check a service responds. Returns only the new check's id at data.data.new_id, so follow it with StatusCake: Get Uptime Check if the workflow needs the full record. How many checks an account may hold and how low the check rate may go are both capped by the StatusCake plan, so a rejected create is often a plan limit rather than a bad request.

StatusCake: Delete Contact Group

statuscake_delete_contact_group

DESTRUCTIVE and irreversible. Deleting a contact group discards the group and its whole recipient list, and StatusCake documents no trash and no restore. The dangerous part is what happens to the checks: every uptime, SSL, pagespeed and heartbeat check that alerted through this group loses that route, and they keep running and keep going down while alerting nobody. Nothing warns you first. List the checks referencing the group id before deleting it, and reattach them to another group.

StatusCake: Delete Heartbeat Check

statuscake_delete_heartbeat_test

DESTRUCTIVE and irreversible. Deleting a heartbeat check discards the check, its recorded history and its push URL. Any job still calling that URL is now pinging a check that does not exist, and nothing tells you the job stopped: the monitoring goes quiet rather than going red. StatusCake documents no trash and no restore, and a recreated check gets a NEW push URL. If you only want the alerting to stop, use StatusCake: Update Heartbeat Check with paused set to true.

StatusCake: Delete Maintenance Window

statuscake_delete_maintenance_window

DESTRUCTIVE and irreversible. Deleting a maintenance window removes the schedule and the list of checks and tags it covered, and StatusCake documents no trash and no restore, so a recurring window has to be rebuilt from scratch. The immediate effect matters as much as the loss: the checks it covered start alerting again, which during a planned outage means paging everyone. The checks themselves are untouched.

StatusCake: Delete Pagespeed Check

statuscake_delete_pagespeed_test

DESTRUCTIVE and irreversible. Deleting a pagespeed check discards the check and its entire recorded history: every load time, page size and request count ever measured for that page, and the saved HAR files behind them. StatusCake documents no trash and no restore. If you only want the measurements to stop, use StatusCake: Update Pagespeed Check with paused set to true.

StatusCake: Delete SSL Check

statuscake_delete_ssl_test

DESTRUCTIVE and irreversible. Deleting an SSL check discards the check and every certificate observation recorded against it, including the expiry history you would use to prove when a certificate changed. StatusCake documents no trash and no restore. If you only want the checks and the expiry warnings to stop, use StatusCake: Update SSL Check with paused set to true.

StatusCake: Delete Uptime Check

statuscake_delete_uptime_test

DESTRUCTIVE and irreversible. Deleting an uptime check takes its entire history with it: every recorded run and load time, every up and down period, and every alert ever sent for it. All of that is reachable only through this check id and no other endpoint can return it once the id is gone. StatusCake documents no trash and no restore. If you only want the checks to stop, use StatusCake: Update Uptime Check with paused set to true, which keeps the history.

StatusCake: Update Contact Group

statuscake_update_contact_group

Change an existing contact group: rename it or change who it alerts. Only the fields you fill are sent, but every list field REPLACES what is there rather than adding to it, so adding one email address means reading the group first with StatusCake: Get Contact Group and sending the whole list back with the new address included. Sending an empty array clears a list, which silently stops that channel for every check using the group. Succeeds with HTTP 204 and an empty body.

StatusCake: Update Heartbeat Check

statuscake_update_heartbeat_test

Change an existing heartbeat check in place, including pausing it while a job is knowingly off and resuming it afterwards. Only the fields you fill are sent, and contact_groups and tags REPLACE the current lists rather than adding to them. Succeeds with HTTP 204 and an empty body.

StatusCake: Update Maintenance Window

statuscake_update_maintenance_window

Change an existing maintenance window: move it, change how often it repeats, or change which checks and tags it covers. Only the fields you fill are sent, but tests and tags REPLACE the current lists rather than adding to them, so read the window first with StatusCake: Get Maintenance Window and send the full intended list. Succeeds with HTTP 204 and an empty body.

StatusCake: Update Pagespeed Check

statuscake_update_pagespeed_test

Change an existing pagespeed check in place, including pausing and resuming it and moving it to a different region. Only the fields you fill are sent, and contact_groups REPLACES the current list rather than adding to it. Changing the region changes what the numbers mean, so a history that spans the change is not a like-for-like series. Succeeds with HTTP 204 and an empty body.

StatusCake: Update SSL Check

statuscake_update_ssl_test

Change an existing SSL check in place, including pausing and resuming it. Only the fields you fill are sent. alert_at and contact_groups REPLACE the current lists rather than adding to them, and alert_at must still be exactly three values when sent. Succeeds with HTTP 204 and an empty body, so read the check back with StatusCake: Get SSL Check if you need the result.

StatusCake: Update Uptime Check

statuscake_update_uptime_test

Change an existing uptime check in place, including pausing and resuming it with the paused field. Only the fields you fill are sent, so everything else is left alone. Two things behave differently from the rest: the list fields (contact_groups, tags, dns_ips, regions) REPLACE what is there rather than adding to it, so send the full intended list and send an empty array to clear one; and the check's TYPE cannot be changed after creation, which is why test_type is not offered here. Succeeds with HTTP 204 and an empty body, so read the check back with StatusCake: Get Uptime Check if you need the result.

Using the integration

Every write is form encoded, and why that matters even though it is handled

StatusCake's API description declares application/x-www-form-urlencoded at the top level, which applies to every operation without exception. There is no JSON request body anywhere in this API. This is the failure that costs the most time when it is not handled, because it fails in the most misleading way available: a JSON body is never parsed into fields, so StatusCake answers with a missing-required-parameter error that reads exactly like a bad node configuration, and an hour can go into checking field names before anyone checks the content type. The integration sends every write the way StatusCake documents it, including the bracket spelling its parameter guide specifies for lists, so you do not have to think about this. Two consequences do reach you. Fields that hold a list, such as contact groups, tags and regions, are entered as a JSON array in the node and sent as repeated bracketed keys. And two fields on an uptime check, the custom header and the post body, are documented as JSON objects carried in a text field, so an object dragged in from an upstream node is serialised for you rather than needing a conversion step.

List fields replace rather than append, on every update

This is the sharpest edge in the integration and it is StatusCake's design rather than ours. Every list-shaped field replaces the stored value on an update: contact groups, tags, DNS IPs, regions, an SSL check's alert days, and a contact group's email addresses, mobile numbers and integrations, and the checks a maintenance window covers. Adding one address to a contact group therefore means reading the group first with StatusCake: Get Contact Group and sending the whole intended list back through StatusCake: Update Contact Group. Sending only the new address removes everybody else, silently, from a group whose entire job is telling people the site is down. The corollary is useful rather than dangerous: an empty array is StatusCake's documented way to clear a list, so sending an empty tags array clears the tags while omitting the field entirely leaves them alone. The integration keeps those two intentions distinct rather than treating an empty list as an empty field.

What creates, updates and deletes actually return

Three shapes, and two of them look like failures until you know them. A create returns HTTP 201 with only the new record's id at data.data.new_id, and nothing else, so a workflow that needs the created object has to follow with the matching get node. Every update and every delete returns HTTP 204 with an empty body, which surfaces as an empty data object with success set, so a node that appears to have returned nothing after an update has worked. Reads are the ordinary case: a single resource at data.data, a page-numbered list at data.data with page, per page, page count and total count at data.metadata, and the four series endpoints at data.data with StatusCake's own next page link at data.links. When a write fails, StatusCake names the field: the error body carries a message and an errors map of field name to a list of messages, so a rejected create usually tells you exactly which value it did not like.

The four windowed series, and how to walk them

StatusCake: List Uptime Check History, StatusCake: List Uptime Check Periods, StatusCake: List Uptime Check Alerts and StatusCake: List Pagespeed Check History are not paged by number. They take before and after as UNIX timestamps in seconds, not milliseconds and not ISO dates, plus a limit of up to 100 rows. Getting the unit wrong does not error, it just returns the wrong window, which is why the node descriptions state it. Walk backwards by taking the oldest created_at you received, converting it to a UNIX timestamp and passing it as before. Truncation has one signal only: if the row count equals the limit you set, there is almost certainly more to fetch. Two aggregation cautions belong with these nodes. Response times and load times are per-run measurements with no sample count returned, so a mean of means is wrong and there is nothing to weight it by; re-request the window you want. And a status period is timestamped by when it started, with an ongoing period carrying no duration at all until it ends, so summing durations by day silently undercounts exactly during an outage. Pagespeed history is the lucky case: StatusCake computes minimum, maximum and average over the requested window itself and returns them alongside the rows, so read that figure rather than rebuilding one.

Maintenance windows, and the timezone that decides everything

StatusCake: Create Maintenance Window suppresses alerting over a planned outage, and three details decide whether it does what you meant. The start and end times are RFC3339 strings, but only the date and time parts are used and the UTC offset in the string is ignored: the moment is read as local time in the timezone field, so a window written as a UTC timestamp against an American timezone runs hours from where it appears to. When a repeat interval is set, the date fixes the first occurrence only and later windows repeat at the same local time. A window covers checks either by naming them or by tag, evaluated when the window runs so a check tagged later is picked up automatically, and a window with neither is accepted by the API while suppressing nothing at all. And the coverage is narrower than people expect: only uptime checks can be covered, so SSL, pagespeed and heartbeat checks alert straight through a planned outage. StatusCake: Delete Maintenance Window is flagged destructive less for the record it removes than for the immediate effect, which is that every check it covered starts alerting again.

Uptime check fields that behave unexpectedly

Four are worth knowing before you automate a create. The failure status codes field is a plain comma separated string rather than one of this API's array fields, and its polarity is the reverse of what people assume: these are the codes that trigger an alert, not the codes that count as healthy, so putting 200 in the list alerts on success. Redirects are not followed by default, so a site that redirects from its apex to www is judged on the redirect itself rather than on where it lands. The check type cannot be changed after a check is created, which is why StatusCake: Update Uptime Check does not offer it; changing a check from HTTP to TCP means delete and recreate, and that discards the history. And the string match field pairs with an invert setting, so the same field can mean the check is down when the text is missing or down when it is present, which is how you watch for an error banner rather than for a success message.

Heartbeat checks, and the URL that is a credential

A heartbeat check inverts the usual direction: your job calls StatusCake, and the check goes down when the call does not arrive within the configured period. StatusCake: Create Heartbeat Check provisions one from a workflow, which is a good fit for a batch job, sync worker or backup routine that has no URL to poll, and the period should be set comfortably longer than the job's normal run interval or a slow run alerts. The returned URL embeds the check's push key, so it is a credential: anything that can call it can mark the job healthy. Route it through a secret rather than a log, a message or a spreadsheet. This is also why the heartbeat check picker deliberately shows the check's status as its second line rather than its URL, since a picker's description renders to everyone who can open the node. StatusCake: Delete Heartbeat Check is the quiet failure of this family: the job carries on pinging a URL for a check that no longer exists and nothing reports that it stopped, and a recreated check gets a new push URL.

On the automation canvas

StatusCake nodes chain with every other node in Mattering. A deploy pipeline can call a Mattering webhook that runs StatusCake: Create Maintenance Window before a release and StatusCake: List Uptime Check History after it, so the workflow verifies the site answered rather than assuming it did. A scheduled morning workflow can read StatusCake: List Uptime Checks and StatusCake: List Uptime Check Periods and open a Mattering Productivity task summarising the night. A rota change in another system can reach StatusCake: Update Contact Group the same day instead of at the next incident. The pickers do the wiring: check, window and contact group fields are populated from the matching lister in this same integration, uptime checks are grouped by type with the watched URL underneath, and the monitoring regions field on an uptime check is populated from StatusCake: List Uptime Monitoring Locations. One picker is deliberately absent. The pagespeed region field takes an eleven-value code list of its own, which is a different vocabulary from the per-server codes StatusCake: List Pagespeed Monitoring Locations returns, so wiring the lister into it would populate happily with values of the wrong kind. The valid codes are spelled out in the field description instead.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. StatusCake publishes no MCP server of its own, so there is no vendor alternative to weigh here: its developer portal covers the API, official SDKs for Go, JavaScript, Python and Ruby, a Terraform provider and a cakectl command line tool listed as coming soon, and does not mention MCP anywhere. Because a StatusCake token has no scopes, the split worth making is at the workflow rather than at the credential: give an assistant the eighteen read nodes and keep creates, updates and especially the six deletes behind a condition or an approval step. An agent reading StatusCake: List Uptime Checks and StatusCake: List Uptime Check Alerts to explain last night is low risk. An agent holding StatusCake: Delete Uptime Check is not, because that call takes the check's entire history with it.

What this integration does not cover

Four things, and the first is the one to check a plan against before designing anything. Domain monitoring is sold on StatusCake's plan page, including one domain monitor on the free tier, and the API has no domain surface whatsoever in version 1.2.0: no path, no resource definition, and nothing for it in StatusCake's own generated client. Domain expiry cannot be read, created or alerted on here. Server monitoring, public status pages and reporting, SMS credit management, team members, audit logs and account or billing are likewise absent from the API description and therefore absent here. Alert integrations are a partial case worth naming: a contact group references integration ids and no endpoint lists, creates or deletes an integration, so those ids come from the integrations page of the StatusCake dashboard and the field is free text rather than a picker. And there are no trigger nodes, so nothing in this integration listens for a StatusCake event.

Troubleshooting

Test Connection fails with a 401
StatusCake's authentication guide states that API requests without authentication fail with 401 Unauthorised, and on this integration that status has a short list of causes because there is only one credential field. The token was mistyped or truncated when pasted, it was revoked in the StatusCake account panel, or it was regenerated there and the new value was never brought back here. Open the account panel at app.statuscake.com/User.php, confirm the token still exists, and either paste it again or generate a new one and update the credential in Connectors. There is no region, scope or permission setting that can cause a 401 on this API, so if the token is definitely current the next thing to check is that it was saved into the credential rather than typed into a node.
Requests start failing partway through a run with a 429
The account is over its rate limit rather than anything being broken. StatusCake documents 60 requests per minute for accounts without a subscription or on a free plan, no per-minute limit for paid subscriptions, and a burst limit of 5 requests per second for all accounts, free or otherwise. That burst limit is why a paid account can still see this: a workflow that fans out and reads history for dozens of checks at once trips 5 per second regardless of plan. Every response carries x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset, the last being seconds until the window resets. This integration does not retry or back off, so a 429 surfaces as an unsuccessful node carrying StatusCake's own response body. The durable fix is shape: iterate in sequence rather than in parallel, and read the list nodes once rather than reading every check individually.
A create is rejected and the error names a field
That is the API working as designed, and the error body is more helpful than most: it carries a message and an errors map of field name to a list of messages, so start with the field it names. The three that fail most often each have a rule that is easy to miss. An SSL check's alert days must be exactly three numerical values, so two or four is refused. A maintenance window needs a name, a start, an end and a timezone, and at least one of the checks or tags fields, or it covers nothing. And an uptime check's check rate is a fixed set of values, so a rate outside that set is refused. If the named field looks correct, check the plan next: how many checks an account may hold and how low a check rate may go are both plan limits, and StatusCake rejects the create rather than the node doing it.
An update returned nothing at all
It worked. Every update and every delete in this API answers HTTP 204 with an empty body, which surfaces here as an empty data object with success set, and it reads like a failure the first time you see it. If a following step needs the updated record, add the matching get node after the update rather than trying to read fields off the update's own output. Creates are the same shape in reverse: they return HTTP 201 carrying only the new record's id at data.data.new_id, so a workflow that needs the full created object follows with a get.
An update wiped values that were not being changed
List fields replace rather than append, on every update, and this is the most damaging version of it. Contact groups, tags, DNS IPs, regions, SSL alert days, email addresses, mobile numbers, integrations and the checks a maintenance window covers all behave this way, so sending only the addition removes everything else. The pattern that avoids it is to read before you write: run the matching get node, take the current list, add or remove locally, and send the full intended set back. If the value was cleared rather than replaced, check whether an empty array reached the field, because an empty array is StatusCake's documented way to clear a list and the integration honours it deliberately. Omitting the field entirely is what leaves an existing value alone.
A maintenance window ran at the wrong time, or suppressed nothing
Three causes, in the order worth checking. The timezone field is what decides when the window runs: only the date and time parts of the start and end are used and the UTC offset in the string is ignored, so a start written with a Z suffix against an American timezone runs at that local time, not at that UTC time. Next, coverage: a window with neither checks nor tags is accepted by the API and suppresses nothing, and tag matching is evaluated when the window runs rather than when it is created. Third, scope: only uptime checks can be covered by a maintenance window, so SSL, pagespeed and heartbeat checks alert straight through one. Read the window back with StatusCake: Get Maintenance Window and check its state and timezone before adjusting anything.
An uptime check alerts on healthy responses, or misses real failures
Start with the failure status codes field, because its polarity catches nearly everyone: those are the codes that trigger an alert, not the codes that count as healthy, so a 200 in that list alerts every time the site works. It is also a plain comma separated string rather than one of this API's array fields. Next check redirects, which are not followed by default, so a site that redirects from its apex to www is judged on the redirect rather than on the page it lands on, and a final endpoint can be set when the chain must end somewhere specific. Then check the string match settings, since the same field means down when the text is missing or down when it is present depending on the invert setting. And confirm the check type matches what you are watching: an HTTP check and a TCP check use different fields entirely, and the type cannot be changed after creation.
SSL fields such as mixed content or certificate scores come back empty
That is usually a plan boundary rather than a fault, and it is the kind that does not announce itself: the check runs, the request succeeds, and the fields are simply empty. StatusCake's pricing page lists mixed content alerts and certificate scores from its Superior tier. The same shape applies to an uptime check's monitoring regions, since custom locations are listed from the Superior tier, so a regions value may be ignored or rejected on a free account. Before concluding a node is broken, check whether the feature the field belongs to is on the plan, and note that there is no plan field anywhere in an API response to tell you, which is why this has to be checked on the pricing page rather than in the payload.
A filter on the check listers seems to do the opposite of what was set
Two query parameters on the check listers are documented as taking no value, where absence means false and presence means true. Sending one of them as false therefore turns it on, because the parameter is present. This integration exposes them as ordinary booleans and emits them only when true, omitting the key entirely when false, so setting them here behaves the way the labels read. If a tag filter is returning fewer checks than expected, the cause is usually the other setting on the same node: a check must carry all the listed tags by default, and matching any one of them is the option beside it.
A workflow needs to monitor a domain, a server or a status page and cannot find the node
Those are StatusCake features without an API surface, so there is no node to find. The domain one is the trap, because StatusCake sells domain monitoring on its plan page and includes one domain monitor on the free tier, while its API version 1.2.0 has no domain path and no domain resource at all. Server monitoring, public status pages and reporting, SMS credit management, team members and audit logs are absent from the API description in the same way. Alert integrations are the near miss: a contact group references integration ids and the API has no endpoint that lists them, so read the ids off the integrations page of the StatusCake dashboard and enter them as free text, then confirm with StatusCake: Get Contact Group that they stored.

StatusCake is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products