StatusCake is a website monitoring platform that provides observability for applications, offering features like uptime monitoring, page speed monitoring, SSL monitoring, and more.
StatusCake is a website monitoring platform that provides observability for applications, offering features like uptime monitoring, page speed monitoring, SSL monitoring, and more. On Nagent, Statuscake is exposed as a fully-configurable server monitoring integration that any agent can call — 30 actions, and API key authentication. No code is required to wire Statuscake into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Statuscake to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Statuscake into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Statuscake, with input parameters and output schema. Drop these into any step of an agent built in Helix.
STATUSCAKE_CREATE_CONTACT_GROUPTool to create a contact group for alert notifications in StatusCake. Use when you need to set up a new group of notification recipients for monitoring alerts. The group can include email addresses, mobile numbers, integrations, and a webhook URL. At minimum, provide a name; other notification methods are optional.
Input parameters
Name of the contact group. This is a required field.
URL or IP address of an HTTP GET endpoint to push uptime events to. Currently only supports HTTP GET endpoints.
List of integration IDs to associate with this contact group. Integration IDs can be obtained from your StatusCake integrations.
List of international format mobile phone numbers for SMS notifications (e.g., +1234567890).
List of email addresses to receive notifications. Each email will be notified when associated tests trigger alerts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_CREATE_HEARTBEAT_TESTTool to create a heartbeat check in StatusCake. Use when you need to set up monitoring for services that send periodic pings. A heartbeat check monitors whether your service is sending regular "heartbeat" pings to StatusCake. If the service fails to send a ping within the specified period, StatusCake will alert you through the configured contact groups. This is ideal for monitoring cron jobs, backup processes, or any scheduled tasks that should run at regular intervals.
Input parameters
Name of the hosting provider or location for organizational purposes.
Name of the heartbeat check. This is the identifier you'll see in the StatusCake dashboard.
List of tags to assign to the heartbeat check for organization and filtering.
Whether the check should be paused (not actively monitoring). Set to true to create the check in a paused state. Defaults to false (active monitoring).
Number of seconds since the last ping before the check is considered down. Minimum 30 seconds, maximum 172800 seconds (48 hours).
List of contact group IDs to notify when the heartbeat check fails. Each ID should be a string (e.g., '355190').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_CREATE_PAGESPEED_TESTTool to create a new pagespeed check in StatusCake. Use when you need to set up performance monitoring for a website URL with specific check frequency and region. Returns the ID of the newly created test.
Input parameters
Name of the pagespeed check.
Whether the check should be paused. Default is false (check will run).
Region on which to run checks. Valid values: AU, CA, DE, FR, IN, JP, NL, SG, UK, US, USW.
Number of seconds between checks. Valid values: 60 (1 minute), 300 (5 minutes), 600 (10 minutes), 900 (15 minutes), 1800 (30 minutes), 3600 (1 hour), 86400 (1 day).
URL, FQDN, or IP address of the website under test.
An alert will be sent if the size of the page is larger than this value (kb). A value of 0 prevents alerts being sent.
An alert will be sent if the load time of the page exceeds this value (ms). A value of 0 prevents alerts being sent.
An alert will be sent if the size of the page is smaller than this value (kb). A value of 0 prevents alerts being sent.
List of contact group IDs to notify on alerts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_CREATE_UPTIME_TESTTool to create a new uptime monitoring check in StatusCake. Use when you need to set up monitoring for a website or server. Supports various check types including HTTP, PING, TCP, DNS, and more. Returns the ID of the newly created test.
Input parameters
Name of the hosting provider.
Name of the uptime check.
Destination port for TCP checks.
List of tags to assign to the test.
Whether the check should be paused (not run). Default is false.
List of IP addresses to compare against returned DNS records (for DNS check type).
List of regions on which to run checks. The values can be retrieved from the STATUSCAKE_GET_ALL_LOCATIONS action. If not specified, the API will use default regions.
The number of seconds to wait to receive the first byte (5-75). Default is 15.
Whether to enable cookie storage. Default is false.
Raw HTTP POST string to send to the server.
JSON object as string representing the payload submitted with the request. Setting this updates the check to use the HTTP POST verb.
Uptime check type (DNS, HEAD, HTTP, PING, SMTP, SSH, or TCP).
Number of seconds between checks. Use 0 to pause, 30 for 30s, 60 for 1min, 300 for 5min, 900 for 15min, 1800 for 30min, 3600 for 1hr, 86400 for 1 day.
FQDN or IP address of the nameserver to query (for DNS check type).
Custom user agent string set when testing.
Whether to consider the check as down if the find_string content is present within the response. Default is false.
String to look for within the response. Considered down if not found.
URL or IP address of the server under test.
Number of confirmation servers to confirm downtime before an alert is triggered (0-3). Default is 2.
The number of minutes to wait before sending an alert (0-60). Default is 0.
JSON object as string representing headers to be sent when making requests (e.g., '{"User-Agent": "CustomAgent"}').
Basic authentication password for the target website.
Basic authentication username for the target website.
List of contact group IDs to notify on status changes.
Specify where the redirect chain should end.
Include header content in string match search. Default is false.
Whether to send an alert if the SSL certificate is soon to expire. Default is false.
Whether to follow redirects when testing. Default is false.
Comma separated list of status codes that trigger an alert (e.g., '400,401,403,404,500').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_DELETE_CONTACT_GROUPTool to delete a contact group. Use when you need to remove an existing contact group by its ID after confirming its existence.
Input parameters
The unique identifier of the contact group to delete. Contact group IDs can be retrieved using the Get All Contact Groups action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_DELETE_HEARTBEAT_TESTPermanently deletes a StatusCake heartbeat check. Use this to remove heartbeat monitoring tests that are no longer needed. This operation is irreversible - the heartbeat check and all its historical data will be removed.
Input parameters
The unique identifier of the heartbeat check to delete. Obtain this from the STATUSCAKE_GET_HEARTBEAT_CHECKS action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_DELETE_PAGESPEED_TESTPermanently deletes a StatusCake PageSpeed test. Use this to remove PageSpeed tests that are no longer needed. This operation is irreversible - the test and all its historical data will be removed. The operation is idempotent - deleting an already-deleted test will still return success.
Input parameters
The unique identifier of the PageSpeed test to delete. Obtain this from the STATUSCAKE_GET_ALL_PAGESPEED_TESTS action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_DELETE_SSL_TESTTool to delete an SSL check with the given ID. Use when you need to permanently remove an SSL monitoring test from StatusCake.
Input parameters
The unique identifier of the SSL check to delete. Obtain this from the STATUSCAKE_GET_SSL_CHECKS action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_DELETE_TESTPermanently deletes a StatusCake uptime monitoring test. Use this to remove tests that are no longer needed. This operation is irreversible - the test and all its historical data will be removed. The operation is idempotent - deleting an already-deleted test will still return success.
Input parameters
The unique identifier (numeric ID) of the uptime test to delete. Obtain this from the STATUSCAKE_GET_ALL_TESTS action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_ALL_CONTACT_GROUPSRetrieves a paginated list of contact groups for alert notifications. Contact groups define who receives alerts when monitoring tests fail. Returns group names, email addresses, mobile numbers, and integrations. Use this to find existing contact groups before creating new ones or to verify notification recipients.
Input parameters
Page number for pagination (1-indexed). Defaults to 1 if omitted.
Maximum number of contact groups to return per page (1-100). Defaults to 25 if omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_ALL_LOCATIONSRetrieves all available uptime monitoring server locations from StatusCake. Use this tool to: - List all monitoring locations to show users available regions - Get region_code values needed when creating or updating uptime checks - Check the current status of monitoring servers - Get IP addresses of monitoring servers for firewall whitelisting Returns ~150 monitoring locations across 30+ countries with their region codes, IP addresses, and availability status.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_ALL_PAGESPEED_TESTSTool to retrieve all PageSpeed tests. Use when you need to list existing PageSpeed performance tests in StatusCake after authenticating.
Input parameters
Page number of results to return (1-based).
Number of results per page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_ALL_TESTSTool to retrieve a list of all tests. Use when you need to list your monitoring tests in StatusCake. Results reflect only pre-configured tests; missing results or stale check data do not indicate real-time downtime.
Input parameters
Page number of results to return (1-based).
Comma-separated list of tags to filter tests by.
Number of results per page (1-100). Server default is 25.
Include uptime data if true.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_CONTACT_GROUP_DETAILSTool to retrieve details of a specific contact group. Use when you need group metadata by providing its ID. Example: "Get details for contact group 12345".
Input parameters
The unique identifier for the contact group to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_HEARTBEAT_CHECKSTool to list heartbeat checks. Use when you need to retrieve all heartbeat monitoring tests for your account.
Input parameters
Page number of results to return (1-based).
Number of results per page (1-100).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_HEARTBEAT_TESTTool to retrieve details of a specific heartbeat check. Use when you need configuration and status of a heartbeat test by providing its ID. Example: "Get heartbeat test details for 7884186".
Input parameters
The unique identifier for the heartbeat check to retrieve. Obtain this from the Get Heartbeat Checks action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_PAGESPEED_TESTTool to retrieve details of a specific pagespeed check. Use when you need configuration and status of a pagespeed test by providing its ID. Example: "Get pagespeed test details for 122582".
Input parameters
The unique identifier for the pagespeed check to retrieve. Obtain this from the Get All Pagespeed Tests action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_SSL_CHECK_DETAILSTool to retrieve details of a specific SSL check. Use when you need configuration and status of an SSL test by providing its ID. Example: "Get SSL check details for 123".
Input parameters
The unique identifier for the SSL check to retrieve. Obtain this from the Get SSL Checks action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_SSL_CHECKSRetrieve a paginated list of SSL checks configured in your StatusCake account. Use this action to: - List all SSL certificate monitors - Check certificate statuses across your monitored domains - Review SSL check configurations and alert settings - Get pagination metadata for navigating large result sets Returns SSL check details including certificate validity dates, cipher information, security scores, and alert configuration.
Input parameters
Page number for pagination (1-based). Defaults to 1 if omitted.
Number of results per page (1-100). Default is 25 if omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_GET_UPTIME_TESTTool to retrieve details of a specific uptime test. Use when you need configuration and status of an uptime check by providing its ID. Example: "Get uptime test details for 7884184".
Input parameters
The unique identifier for the uptime test to retrieve. Obtain this from the Get All Tests action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_LIST_PAGESPEED_MONITORING_LOCATIONSRetrieves all available PageSpeed monitoring server locations from StatusCake. Use when you need to list regions for PageSpeed test configuration or check server availability.
Input parameters
Alpha-2 ISO 3166-1 country code to filter locations by country (e.g., 'GB', 'US', 'DE')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_LIST_PAGESPEED_TEST_HISTORYTool to retrieve pagespeed check history for a given test ID. Use when you need to analyze historical performance data for a specific pagespeed test.
Input parameters
Only results created after this UNIX timestamp will be returned.
The number of results to return from the series. Default is 25.
Only results created before this UNIX timestamp will be returned.
Pagespeed check ID to retrieve history for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_LIST_UPTIME_TEST_ALERTSTool to retrieve a list of alerts for a specific uptime check. Use when you need to view historical alerts and status changes for an uptime test.
Input parameters
Only alerts triggered after this UNIX timestamp will be returned.
The number of uptime alerts to return per page. Default is 25.
Only alerts triggered before this UNIX timestamp will be returned.
Uptime check ID to retrieve alerts for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_LIST_UPTIME_TEST_HISTORYTool to retrieve uptime check history for a given test ID. Use when you need to view historical results of uptime monitoring checks. Supports pagination and time-based filtering.
Input parameters
Only results created after this UNIX timestamp will be returned.
The number of results to return per page. Server default is 25.
Only results created before this UNIX timestamp will be returned.
The unique identifier for the uptime test to retrieve history for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_LIST_UPTIME_TEST_PERIODSTool to retrieve a list of uptime check periods for a specific test. Use when you need to view the historical up/down periods for an uptime check.
Input parameters
Only check periods created after this UNIX timestamp will be returned.
The number of uptime check periods to return per page. Default is 25.
Only check periods created before this UNIX timestamp will be returned.
Uptime check ID to retrieve periods for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_UPDATE_CONTACT_GROUPUpdates an existing contact group's configuration in StatusCake. Use this tool when you need to modify the name, email addresses, mobile numbers, or integrations of an existing contact group. At least one field besides contact_group_id should be provided to make meaningful changes. The API uses form-urlencoded data format and returns 204 No Content on success, so the action fetches the updated group details after a successful update.
Input parameters
New name for the contact group. If not provided, the existing name is preserved.
List of integration IDs to associate with the group. Replaces existing integrations when provided.
List of mobile phone numbers for SMS notifications. Replaces existing list when provided.
List of email addresses for notifications. Replaces existing list when provided.
Unique identifier of the contact group to update (numeric string, e.g. '355190')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_UPDATE_HEARTBEAT_TESTTool to update an existing heartbeat check with new parameters. Use when you need to modify the name, monitoring period, tags, contact groups, host, or pause status of a heartbeat check.
Input parameters
Name of the hosting provider
Name of the heartbeat check
List of tags to assign to the heartbeat check
Whether the heartbeat check should be paused (not actively monitoring)
Number of seconds since the last ping before the check is considered down. Must be between 30 and 172800 (48 hours).
Unique identifier of the heartbeat check to update
List of contact group IDs to notify when the heartbeat is missed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_UPDATE_PAGESPEED_TESTUpdates a pagespeed check with the given parameters. Use when you need to modify the configuration of an existing pagespeed monitoring test in StatusCake. At least one field besides test_id should be provided to make meaningful changes.
Input parameters
Name of the check. If not provided, the existing name is preserved.
Whether the check should be run. Set to true to pause the check, false to resume it.
Region options for pagespeed checks.
Unique identifier of the pagespeed test to update. Obtain this from the STATUSCAKE_GET_ALL_PAGESPEED_TESTS action.
Check rate options in seconds.
URL, FQDN, or IP address of the website under test. If not provided, the existing URL is preserved.
An alert will be sent if the size of the page is larger than this value (kb). A value of 0 prevents alerts being sent.
An alert will be sent if the load time of the page exceeds this value (ms). A value of 0 prevents alerts being sent.
An alert will be sent if the size of the page is smaller than this value (kb). A value of 0 prevents alerts being sent.
List of contact group IDs to notify on alerts. Replaces existing contact groups when provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_UPDATE_SSL_TESTTool to update an SSL check with new configuration parameters. Use when modifying SSL monitoring settings like check frequency, alert preferences, or contact groups. Example: "Update SSL check 123 to check every hour".
Input parameters
Whether to pause the SSL check. Set to true to stop monitoring, false to resume.
Unique identifier of the SSL check to update. Obtain this from Get SSL Checks action.
List of days before certificate expiry to send alerts. Must be exactly 3 numerical values (e.g., \[1, 7, 30\]).
Hostname of the server under test (e.g., 'example.com').
Check rate interval in seconds.
Custom user agent string to use when testing the SSL certificate.
Whether to enable alerts when mixed content (HTTP resources on HTTPS page) is found.
URL of the server to test. Must begin with https:// (e.g., 'https://example.com').
Whether to enable alerts when SSL certificate issues (e.g., expired, broken chain) are detected.
Whether to enable alerts when the SSL certificate is about to expire.
Whether to enable alert reminders for this SSL check.
List of contact group IDs to notify when alerts are triggered. Replaces existing contact groups when provided.
Whether to follow HTTP redirects when testing the SSL certificate. Disabled by default.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
STATUSCAKE_UPDATE_UPTIME_TESTUpdates an uptime check with the given parameters. Use when you need to modify configuration of an existing uptime monitoring test such as check frequency, URL, tags, contact groups, or other settings. At least one field besides test_id should be provided to make meaningful changes.
Input parameters
Name of the hosting provider
Name of the check
Destination port for TCP checks
List of tags to categorize and organize the check
Whether the check should be run. Set to true to pause the check, false to resume it
List of IP addresses to compare against returned DNS records
List of regions on which to run checks. The values can be retrieved from the GET /v1/uptime-locations endpoint
Uptime check ID to update
The number of seconds to wait to receive the first byte (5-75)
Whether to enable cookie storage
Raw HTTP POST string to send to the server
JSON object as string representing the payload submitted with the request. Setting this updates the check to use the HTTP POST verb
Check rate interval in seconds
FQDN or IP address of the nameserver to query
Custom user agent string set when testing
Whether to consider the check as down if the content is present within the response
String to look for within the response. Check is considered down if not found
URL or IP address of the server under test
Number of confirmation servers (0-3) to confirm downtime before an alert is triggered
The number of minutes to wait before sending an alert
JSON object as string representing headers to be sent when making requests
Basic authentication password
Basic authentication username
List of contact group IDs to receive alerts
Specify where the redirect chain should end
Include header content in string match search
Whether to send an alert if the SSL certificate is soon to expire
Whether to follow redirects when testing. Disabled by default
Comma separated list of status codes that trigger an alert
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 84 agents privately built on Nagent that already use Statuscake.
Build on Nagent
Connect Statuscake to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Statuscake, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Statuscake is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Statuscake is connected, you configure its 30 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Statuscake steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Statuscake event fires, the agent kicks off automatically.
Every Statuscake action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Statuscake ships with 30 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Statuscake together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Statuscake-based workflows tailored to your business.