Better Stack provides monitoring, logging, and incident management solutions to help teams ensure the reliability and performance of their applications.
Better Stack provides monitoring, logging, and incident management solutions to help teams ensure the reliability and performance of their applications. On Nagent, Better Stack is exposed as a fully-configurable server monitoring integration that any agent can call — 117 actions, and API key authentication. No code is required to wire Better Stack into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Better Stack 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 Better Stack 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 Better Stack, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BETTER_STACK_ACKNOWLEDGE_INCIDENTTool to acknowledge an ongoing incident. Use when you need to mark an incident as being worked on, which prevents further escalations. Acknowledging an incident signals that someone is actively addressing the issue.
Input parameters
The ID of the incident to acknowledge
Email or custom identifier of the person or system acknowledging the incident
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
BETTER_STACK_CREATE_ESCALATION_POLICYCreates a new escalation policy for incident management. Escalation policies define who gets notified and in what order when incidents occur. Supports multiple step types: 'escalation' (notify members), 'instructions' (guidance text), 'time_branching' (route by schedule), and 'metadata_branching' (route by incident metadata). For escalation steps, a valid urgency_id from the Severities API is required.
Input parameters
Name of the escalation policy
Ordered list of escalation policy steps
Team owning the policy (required with global API token)
How many times to repeat the policy if unacknowledged
Seconds to wait between policy repetitions
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
BETTER_STACK_CREATE_HEARTBEATTool to create a new heartbeat monitor for cron jobs and scheduled tasks. Use when you need to set up monitoring for a service that should send regular heartbeat signals.
Input parameters
Should we send an SMS to the on-call person?
Should we call the on-call person?
The name of the service for this heartbeat
Should we send a push notification to the on-call person?
Should we send an email to the on-call person?
Grace period for heartbeat fluctuation in seconds. Minimum value: 0. Recommended: 20% of period
Set to true to pause monitoring
How often should we expect this heartbeat in seconds. Minimum value: 30 seconds
Required if using global API token to specify the team which should own the resource
Set this attribute to add this heartbeat to a heartbeat group
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
BETTER_STACK_CREATE_HEARTBEAT_GROUPTool to create a new heartbeat group. Use when you need to organize related heartbeat checks under a single, logical group. Example prompt: "Create a new heartbeat group named 'Backend services'."
Input parameters
Name of the group visible in the dashboard.
Set to true to pause monitoring for all existing heartbeats in the group; false (default) to resume monitoring.
Team which should own the resource. Required when using a global API token.
Zero-based index to control sort order of heartbeat groups.
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
BETTER_STACK_CREATE_INCIDENTTool to create a new incident and alert the on-call person. Use when you need to manually report an incident or trigger escalation workflows. The incident will be routed according to the specified escalation policy or default team settings.
Input parameters
Send SMS notification to on-call person
Trigger phone call to on-call person
Short incident title
Send email notification to on-call person
Brief incident overview
Custom metadata with key-value pairs for incident classification and routing
Escalation policy identifier for routing the incident
Team owning the incident (required when using global API token)
Escalation delay in seconds before alerting entire team. Leave blank to disable team escalation.
Detailed incident information
Send critical push notification that ignores mute switch and Do Not Disturb settings
Email of user requesting the incident
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
BETTER_STACK_CREATE_INCIDENT_COMMENTTool to create a new comment on an incident. Use when you need to add documentation, updates, or notes to an existing incident in Better Stack.
Input parameters
The content of the comment. Markdown is supported for formatting.
The ID of the incident to add the comment to
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
BETTER_STACK_CREATE_METADATATool to create or update a metadata record for a resource. Metadata provides key-value associations for resources like monitors, heartbeats, or incidents. Use when you need to tag or annotate resources with custom data. Existing values for the specified key will be completely replaced.
Input parameters
The metadata key identifier. This serves as the name for the metadata entry
Array of metadata values to associate with the key. Existing values for the given key will be completely replaced
The ID of the resource to update metadata for
Type of resource that owns this metadata. Must be one of: Monitor, Heartbeat, Incident, WebhookIntegration, EmailIntegration, IncomingWebhook, or CallRouting
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
BETTER_STACK_CREATE_MONITORTool to create a new uptime monitor for a URL or service. Use when you need to set up monitoring for websites, APIs, servers, or network services. Supports multiple monitor types including HTTP/HTTPS status checks, keyword monitoring, ping, TCP/UDP, email protocols, DNS queries, and browser automation with Playwright.
Input parameters
Enable SMS notifications when monitor goes down or recovers. Default is false.
The URL or host to monitor. For HTTP/HTTPS monitors use full URL with protocol. For TCP/UDP/SMTP/POP/IMAP use hostname or IP. For DNS monitors use the domain to query.
Enable phone call alerts when monitor goes down or recovers. Default is false.
Port number for TCP, UDP, SMTP, POP, or IMAP monitors. Required for these monitor types.
Enable push notifications when monitor goes down or recovers. Default is false.
Enable email notifications when monitor goes down or recovers. Default is false.
If true, the monitor is created in paused state and will not perform checks. Default is false.
List of regions from which to perform checks. Available: us (United States), eu (Europe), as (Asia), au (Australia). Default is all regions.
ID of the escalation policy to use for this monitor. Controls who gets notified and in what order.
Team which should own this monitor. Required when using a global API token.
Seconds to wait before escalating to the team after first notification. Default is 0 (notify team immediately).
Verify SSL certificates for HTTPS monitors. If false, monitors will accept invalid/self-signed certificates. Default is true.
HTTP method for status/keyword monitors.
Type of monitor: status (HTTP/HTTPS), expected_status_code, keyword, keyword_absence, ping (ICMP), tcp, udp, smtp, pop, imap, dns, or playwright (browser automation).
Body content to send with POST/PUT/PATCH requests. Required for DNS monitors (specify the DNS record type to query).
Password for HTTP Basic Authentication. Used with auth_username.
Username for HTTP Basic Authentication. Used with auth_password.
Name identifier for playwright monitor scenarios. Used to distinguish between different automation scripts.
If enabled, alerts will override Do Not Disturb settings and mute schedules. Use for critical monitors only.
End time of daily maintenance window in HH:MM:SS format. Checks resume after this time.
How often to check the monitor in seconds. Minimum is 30 seconds. Default is 30.
Number of seconds the monitor must be up before automatically resolving any open incidents. Default is 0 (resolve immediately).
Request timeout in seconds. For server monitors this is in milliseconds. Default varies by monitor type.
Automatically follow HTTP redirects when checking status/keyword monitors. Default is false.
Days of the week to skip monitoring checks during maintenance windows. Combine with maintenance_from and maintenance_to.
Start time of daily maintenance window in HH:MM:SS format. Checks are skipped during this window on specified maintenance_days.
ID of the monitor group to assign this monitor to. Used for organizing monitors.
For keyword monitors: the text that must be present in the response. For keyword_absence monitors: the text that must NOT be present.
JavaScript code for playwright monitor type. Defines browser automation scenario to execute during checks.
Human-readable name for the monitor displayed in the dashboard.
How long in seconds to observe failures before creating an incident. Helps avoid false alerts from transient issues. Default is 0.
ID of the escalation policy for SSL certificate and domain expiration alerts.
Timezone for maintenance window times. Use IANA timezone database names.
Key-value pairs of environment variables accessible within playwright scripts. Useful for parameterizing automation scenarios.
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
BETTER_STACK_CREATE_MONITOR_GROUPTool to create a new monitor group. Use when you need to organize related monitors under a single, logical group for better dashboard organization.
Input parameters
The display name for the monitor group visible in the dashboard
When true, monitoring pauses for existing group monitors; false resumes monitoring
Required only when using a global API token to specify resource ownership
Numeric value controlling monitor group sort order
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
BETTER_STACK_CREATE_ON_CALL_SCHEDULETool to create a new on-call schedule. Use when you need to set up a new on-call calendar for managing team rotations.
Input parameters
The identifier for the on-call schedule
Team which should own the resource. Required when using a global API token.
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
BETTER_STACK_CREATE_OUTGOING_WEBHOOKTool to create a new outgoing webhook integration. Use when you need to register an endpoint to receive event notifications from Better Stack.
Input parameters
The endpoint URL of the outgoing webhook integration.
The name of the outgoing webhook integration.
Required if using a global API token to specify the team which should own the resource.
The type of event that triggers the webhook.
Trigger when an incident starts (only if trigger_type is 'incident_change').
Trigger when an incident is resolved (only if trigger_type is 'incident_change').
Trigger when an incident is acknowledged (only if trigger_type is 'incident_change').
Custom webhook template attributes such as HTTP method, headers, and body.
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
BETTER_STACK_CREATE_POLICY_GROUPTool to create a new escalation policy group. Use when you need to organize related escalation policies under a single logical group.
Input parameters
The name of the group that you can see in the dashboard
Required only when using a global API token to designate the owning team
Specifies the ordering sequence for escalation policy groups
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
BETTER_STACK_CREATE_SOURCE_GROUPTool to create a new source group. Use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
Input parameters
The name of the group that you can see in the dashboard.
Required if using a global API token to specify the team which should own the resource.
Set sort_index to specify how to sort your source groups. Must be non-negative.
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
BETTER_STACK_CREATE_STATUS_PAGE_GROUPTool to create a new status page group. Use when you need to organize related status pages under a single logical group with a descriptive name.
Input parameters
A descriptive label for the group visible in the dashboard.
Required only when using a global API token to designate which team owns the resource.
Numeric value controlling the sort order of status page groups.
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
BETTER_STACK_CREATE_STATUS_PAGE_REPORTTool to create a new status page report (incident or maintenance). Use when you need to publish a status update about an ongoing incident or scheduled maintenance on a status page.
Input parameters
The title/name for the status page report
ISO-8601 timestamp when the report/incident ends. Leave empty for ongoing incidents.
The initial status update text/message for this report
ISO-8601 timestamp when the report/incident starts. If not provided, defaults to current time.
Type of report: 'manual' for incident reports or 'maintenance' for scheduled maintenance. Defaults to 'manual'.
ISO-8601 timestamp when the report should be published. If not provided, the report is published immediately.
The numeric ID of the status page (e.g., '221582'). Obtain this from the list_status_pages action.
List of status page resources affected by this report, with their status. Each object must contain status_page_resource_id and status fields. For maintenance reports, use status='maintenance'. For manual incident reports, use status='resolved', 'degraded', or 'downtime'.
Whether to send email notifications to status page subscribers. Defaults to false.
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
BETTER_STACK_CREATE_STATUS_PAGE_RESOURCETool to create a new status page resource. Use when you need to add a monitor, heartbeat, or other resource to a status page for public visibility tracking.
Input parameters
Zero-indexed placement position on the status page (omit to append to end)
Detailed help text displayed as an icon tooltip
Display name shown publicly on the status page
The identifier of the resource being added (Monitor, Heartbeat, etc.)
Display format for the resource on the status page
Type of resource to add to the status page
Prevents position reordering when true
The ID of the status page to add the resource to
Condition that triggers marking the resource as down
Condition that triggers marking the resource as degraded
Section ID where the resource should be placed (defaults to first section if omitted)
Metadata rule for status matching.
Metadata rule for status matching.
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
BETTER_STACK_CREATE_STATUS_PAGE_SECTIONTool to create a new section on a status page. Use when organizing resources into logical groups (e.g., by datacenter or service type). Leave name blank to hide the section header.
Input parameters
The name of the section. Leave blank to hide the section header.
The position of this section on your status page, indexed from zero. Defaults to the end if not specified.
The identifier for your status page where the section will be created.
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
BETTER_STACK_CREATE_STATUS_UPDATETool to create a new status update for an existing status report. Use when you need to post an update about the current state of an incident or maintenance. The update can include a message, affected resources with their status, and optionally notify subscribers.
Input parameters
Message associated with the status update, providing details about the current state or actions taken.
ISO-8601 timestamp for publication time. If not provided, defaults to current time.
Your status page identifier. Obtain from list_status_pages action.
Your status page report identifier. Obtain from list_status_page_reports action.
Array of affected resources with their current status. Must contain at least one resource.
Send notification email to subscribers. Default is false.
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
BETTER_STACK_CREATE_URGENCIESTool to create a new severity level (urgency) for incident management. Use when you need to define notification preferences for different incident severity levels.
Input parameters
Enables SMS notifications for new incidents at this severity level
Enables phone calls for new incidents at this severity level
The identifier for this severity level
Enables push notifications for new incidents at this severity level
Enables email notifications for new incidents at this severity level
Required only when using global API tokens to designate resource ownership
Sends critical alerts bypassing device mute settings
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
BETTER_STACK_CREATE_URGENCY_GROUPTool to create a new urgency group (severity group) for incident categorization. Use when you need to define severity levels for monitoring alerts and incidents.
Input parameters
The name of the urgency group that you can see in the dashboard.
Required only when using a global API token to specify resource ownership. The team which should own the urgency group.
Determines the ordering of severity groups. Must be non-negative.
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
BETTER_STACK_DELETE_ESCALATION_POLICYTool to delete an escalation policy by ID. Use when you need to permanently remove an existing escalation policy after confirming its ID.
Input parameters
The ID of the escalation policy you want to delete
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
BETTER_STACK_DELETE_HEARTBEATTool to permanently delete a heartbeat by ID. Use when you need to remove a heartbeat that is no longer needed.
Input parameters
The unique ID of the heartbeat to delete. You can get this from the list heartbeats or get heartbeat actions.
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
BETTER_STACK_DELETE_HEARTBEAT_GROUPTool to permanently delete a heartbeat group by ID. Use when you need to remove a heartbeat group that is no longer needed.
Input parameters
The ID of the heartbeat group to delete. Use list heartbeat groups to find available IDs.
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
BETTER_STACK_DELETE_INCIDENTTool to permanently delete an existing incident by ID. Use when you need to remove an incident from Better Stack Uptime.
Input parameters
The ID of the incident you want to delete
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
BETTER_STACK_DELETE_INCIDENT_COMMENTTool to delete an existing comment from an incident. Use when you need to remove a comment that was previously added via the API. Note: Only comments created via the API can be deleted; comments created in the UI cannot be deleted via the API.
Input parameters
The unique ID of the comment to delete. Note: Only API-created comments can be deleted.
The unique ID of the incident containing the comment
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
BETTER_STACK_DELETE_MONITORTool to permanently delete a monitor by ID from Better Stack Uptime. Use when you need to remove a monitor that is no longer needed.
Input parameters
The unique ID of the monitor to delete. You can get this from the list monitors or get monitor actions.
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
BETTER_STACK_DELETE_MONITOR_GROUPTool to permanently delete a monitor group by ID from Better Stack Uptime. Use when you need to remove a monitor group that is no longer needed.
Input parameters
The unique ID of the monitor group to permanently delete. You can get this from list monitor groups or create monitor group actions.
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
BETTER_STACK_DELETE_ON_CALL_SCHEDULETool to permanently delete an on-call schedule by ID. Use when you need to remove an on-call calendar that is no longer needed.
Input parameters
The unique ID of the on-call schedule to delete. You can get this from the list on-call schedules 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
BETTER_STACK_DELETE_OUTGOING_WEBHOOKTool to delete an outgoing webhook integration by ID. Use when you need to permanently remove an existing webhook integration.
Input parameters
The unique ID of the outgoing webhook integration to delete. You can get this from the list or create outgoing webhook actions.
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
BETTER_STACK_DELETE_POLICY_GROUPTool to delete an escalation policy group by ID. Use when you need to permanently remove an existing escalation policy group after confirming its ID.
Input parameters
The ID of the escalation policy group you want to delete
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
BETTER_STACK_DELETE_SOURCE_GROUPTool to permanently delete a source group by ID from Better Stack Telemetry (Logs). Source groups are used to organize related log sources. Use this action when you need to remove a source group that is no longer needed. Note: This action requires a Telemetry API token (not an Uptime API token). Deleting a source group does not delete the sources within it - they will become ungrouped.
Input parameters
The unique ID of the source group to delete. You can get this from the list source groups or create source group actions.
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
BETTER_STACK_DELETE_STATUS_PAGE_GROUPTool to delete a status page group by ID. Use when you need to permanently remove an existing status page group.
Input parameters
The ID of the status page group you want to delete
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
BETTER_STACK_DELETE_STATUS_PAGE_REPORTTool to permanently delete a status page report by ID from Better Stack Uptime. Use this action when you need to remove an existing status page report that is no longer needed. The report will be permanently deleted and cannot be recovered.
Input parameters
The numeric ID of the status report to delete (e.g., '824278'). Obtain this from the list_status_page_reports action.
The numeric ID of the status page (e.g., '221582'). Obtain this from the list_status_pages 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
BETTER_STACK_DELETE_STATUS_PAGE_RESOURCETool to delete an existing resource from a status page. Use when you need to permanently remove a resource (monitor or heartbeat) that is displayed on a status page.
Input parameters
The ID of the resource to delete from the status page
The ID of the status page that contains the resource
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
BETTER_STACK_DELETE_STATUS_PAGE_SECTIONTool to permanently delete a status page section by ID. Use when you need to remove a section from a status page that is no longer needed. Sections organize resources on status pages for better visibility.
Input parameters
The ID of the section to delete from the status page. You can get this from listing sections within a status page.
The ID of the status page that contains the section to delete. You can get this from the list status pages or get status page actions.
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
BETTER_STACK_DELETE_STATUS_PAGE_STATUS_REPORT_STATUS_UPDATETool to delete an existing status update from a status report. Use when you need to permanently remove a status update after confirming its ID.
Input parameters
The ID of the status page. You can get this from the list_status_pages action.
The ID of the status report containing the update. You can get this from the list_status_page_reports action.
The ID of the status update to delete.
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
BETTER_STACK_DELETE_URGENCYTool to delete a severity (urgency) by ID. Use when you need to permanently remove an existing severity level after confirming its ID.
Input parameters
The ID of the severity you want to delete
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
BETTER_STACK_DELETE_URGENCY_GROUPTool to permanently delete an urgency group (severity group) by ID. Use when you need to remove an existing severity group that is no longer needed.
Input parameters
The ID of the urgency group (severity group) to delete. You can get this from the list urgency 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
BETTER_STACK_ESCALATE_INCIDENTTool to escalate an ongoing incident to a user, team, schedule, policy, or organization. Use when you need to route an active incident to the appropriate responders with specified notification channels (call, SMS, email, push).
Input parameters
Enable SMS notification
Enable phone notification
Enable push notification
Enable email notification
Team ID to escalate to (required when escalation_type is Team, alternative to team_name)
User ID to escalate to (required when escalation_type is User, alternative to user_email)
Additional metadata key-value pairs to attach to the escalation
Policy ID to escalate to (required when escalation_type is Policy)
Team name to escalate to (required when escalation_type is Team, alternative to team_id)
User email to escalate to (required when escalation_type is User, alternative to user_id)
The identifier of the incident to escalate
Schedule ID to escalate to (required when escalation_type is Schedule)
Critical push notification (bypasses Do Not Disturb)
Target type: User, Team, Schedule, Policy, or Organization. Determines which additional identifier field is required.
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
BETTER_STACK_GET_ESCALATION_POLICYTool to get a single escalation policy by its ID. Use when you need full details of a specific escalation policy including its steps, repeat settings, and team information.
Input parameters
The ID of the escalation policy 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
BETTER_STACK_GET_HEARTBEATTool to get a single heartbeat by ID. Use when you need to fetch details of a specific heartbeat.
Input parameters
The ID of the requested heartbeat
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
BETTER_STACK_GET_HEARTBEAT_AVAILABILITYTool to retrieve availability summary for a specific heartbeat. Use when you need availability metrics for a heartbeat within an optional date range.
Input parameters
End date (inclusive) for the summary in YYYY-MM-DD format
Start date (inclusive) for the summary in YYYY-MM-DD format
ID of the heartbeat to retrieve availability 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
BETTER_STACK_GET_HEARTBEAT_GROUPTool to get a single heartbeat group by ID. Use when you need to fetch details of a specific heartbeat group.
Input parameters
The ID of the heartbeat 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
BETTER_STACK_GET_INCIDENT_COMMENTTool to get a single comment from an incident. Use when you need to retrieve details of a specific comment on a Better Stack incident.
Input parameters
The ID of the comment to retrieve
The ID of the incident containing the comment
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
BETTER_STACK_GET_MONITORTool to get a single monitor. Use when you need full details of a specific monitor by its ID.
Input parameters
The ID of the monitor 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
BETTER_STACK_GET_MONITOR_AVAILABILITYTool to return an availability summary for a specific monitor. Use when you need uptime percentage and incident details within an optional date range.
Input parameters
End date (inclusive) for the summary in YYYY-MM-DD format
Start date (inclusive) for the summary in YYYY-MM-DD format
The ID of the monitor to retrieve availability 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
BETTER_STACK_GET_MONITOR_GROUPSTool to get a single monitor group by ID. Use when you need to fetch details of a specific monitor group.
Input parameters
The ID of the monitor 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
BETTER_STACK_GET_MONITOR_GROUPS_MONITORSTool to get all monitors belonging to a monitor group. Use when you need to retrieve all monitors within a specific monitor group, with optional pagination support.
Input parameters
Page number to return. Starts at 1.
Number of monitors per page. Default is 50, maximum is 250.
The ID of the monitor group to retrieve monitors 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
BETTER_STACK_GET_MONITOR_RESPONSE_TIMESRetrieves response time performance metrics for a specific uptime monitor. Returns detailed timing data (DNS lookup, connection, TLS handshake, data transfer) grouped by geographic region. By default returns data for the last 24 hours. Use this to analyze monitor performance, identify latency issues, or compare response times across regions. Requires a valid monitor_id which can be obtained from the list_monitors action.
Input parameters
Optional end date (inclusive) for filtering response times in ISO 8601 format. If not specified, defaults to now.
Optional start date (inclusive) for filtering response times in ISO 8601 format. If not specified, defaults to 24 hours ago.
Maximum number of response time records to return per region. Defaults to 1 if not specified to prevent oversized responses.
The unique numeric ID of the monitor to retrieve response times for. Obtain this from the list_monitors 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
BETTER_STACK_GET_ON_CALL_SCHEDULETool to get a single on-call schedule by ID. Use when you need to retrieve who is currently on-call for a specific schedule. Optionally specify a date to check on-call status at a specific time.
Input parameters
ISO-8601-formatted date or date-time for looking up on-call at a specific time
The ID of the on-call schedule you want to get. Use 'default' if you want to get the default on-call
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
BETTER_STACK_GET_OUTGOING_WEBHOOKTool to get a single outgoing webhook integration by ID. Use when you need to retrieve details of a specific webhook integration.
Input parameters
The ID of the Outgoing Webhook integration you want to get. You can get this from the list or create outgoing webhook actions.
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
BETTER_STACK_GET_POLICY_GROUPTool to get a single escalation policy group. Use when you need full details of a specific escalation policy group by its ID.
Input parameters
The ID of the escalation policy 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
BETTER_STACK_GET_STATUS_PAGETool to get a single status page by ID. Use when you need detailed information about a specific status page.
Input parameters
The ID of the status page 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
BETTER_STACK_GET_STATUS_PAGE_GROUPTool to get a single status page group by ID. Use when you need to retrieve details of a specific status page group.
Input parameters
The unique identifier for the specific status page 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
BETTER_STACK_GET_STATUS_PAGE_REPORTTool to get a single status page report by ID. Use when you need detailed information about a specific status report or incident.
Input parameters
The numeric ID of the status report to retrieve (e.g., '824274').
The numeric ID of the status page (e.g., '221582'). Obtain this from the list_status_pages 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
BETTER_STACK_GET_STATUS_PAGE_RESOURCETool to get a single status page resource by ID. Use when you need detailed information about a specific resource on a status page.
Input parameters
The ID of the status page resource
The ID of the status 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
BETTER_STACK_GET_STATUS_PAGE_SECTIONTool to get a single status page section. Use when you need details of a specific section within a status page by its ID.
Input parameters
The ID of the section you want to get
The ID of your status 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
BETTER_STACK_GET_STATUS_UPDATETool to get a single status update by its ID. Use when you need details of a specific status update for a status report on your status page.
Input parameters
The ID of your status page. Obtain from list_status_pages action.
The ID of your status page report. Obtain from list_status_page_reports action.
The ID of your status update. Obtain from list_status_page_status_report_status_updates action or after creating a status update.
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
BETTER_STACK_GET_UPTIME_API_TOKENTool to retrieve the configured Uptime API token. Use when you need the Uptime API token for subsequent authenticated API calls.
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
BETTER_STACK_GET_URGENCYTool to get a single severity level (urgency) by ID. Use when you need to fetch details of a specific urgency configuration.
Input parameters
The ID of the severity level you're interested in
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
BETTER_STACK_GET_URGENCY_GROUPTool to get a single urgency group (severity group) by ID. Use when you need to fetch details of a specific urgency group.
Input parameters
The ID of the urgency group (severity group) to retrieve. You can get this from the list urgency 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
BETTER_STACK_LIST_AWS_CLOUDWATCH_INTEGRATIONSTool to list all AWS CloudWatch integrations. Use when you need to retrieve and inspect all configured AWS CloudWatch on-call integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_AZURE_INTEGRATIONSTool to list all Azure integrations. Use when you need to retrieve and inspect all configured Azure on-call integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_CATALOG_RELATIONSTool to list all catalog relations. Use when you need to retrieve all catalog relations, supports pagination.
Input parameters
Page number to return. Starts at 1.
Number of resources per page. Default is 50, maximum is 250.
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
BETTER_STACK_LIST_DATADOG_INTEGRATIONSTool to list all Datadog integrations. Use when you need to retrieve and inspect all configured Datadog on-call integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_ELASTIC_INTEGRATIONSTool to list Elastic integrations. Use when you need to retrieve and inspect all configured Elastic integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations by team name. Useful when using a global API token to narrow results to a specific team.
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
BETTER_STACK_LIST_EMAIL_INTEGRATIONSTool to list email integrations. Use when you need to retrieve and inspect all configured email integrations with optional team filtering and pagination support.
Input parameters
Page number to return. Starts at 1.
Filter email integrations by team name. Useful when using a global API token to narrow results to a specific team.
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
BETTER_STACK_LIST_GOOGLE_MONITORING_INTEGRATIONSTool to list all Google Monitoring integrations. Use when you need to view your configured Google Monitoring on-call integrations with pagination support.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations by team name. Only returns integrations belonging to the specified team. Useful when using a global API token to filter results.
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
BETTER_STACK_LIST_GRAFANA_INTEGRATIONSTool to list all Grafana integrations. Use when you need to retrieve and inspect all configured Grafana integrations.
Input parameters
Page number for pagination. Defaults to 1.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_HEARTBEAT_GROUPSTool to list all heartbeat groups. Use when you need to retrieve configured heartbeat groups with optional filtering by team name.
Input parameters
Page number to return. Starts at 1.
Number of heartbeat groups per page. Default is 50, maximum is 250.
Filter heartbeat groups belonging to a specified team when using global API token
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
BETTER_STACK_LIST_HEARTBEATSTool to list all heartbeats. Use when you need to retrieve your configured uptime heartbeats with optional pagination.
Input parameters
Page number to return. Starts at 1.
Filter heartbeats belonging to a specific team. Only applicable when using a global API token.
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
BETTER_STACK_LIST_INCIDENTS_COMMENTSTool to list all comments on an incident. Use when you need to retrieve all comments associated with a Better Stack incident.
Input parameters
The ID of the incident to list comments 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
BETTER_STACK_LIST_INCIDENTS_TIMELINETool to retrieve all timeline events for an incident. Use when you need to get a chronological history of events, comments, responses, and changes for a specific incident in Better Stack. Returns all timeline items without pagination.
Input parameters
The ID of the incident to get timeline events 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
BETTER_STACK_LIST_INCIDENTS_UPTIMETool to list all incidents with optional filtering by monitor, heartbeat, date range, or resolution status. Supports pagination with default of 10 per page and maximum of 50.
Input parameters
Return incidents until a certain date (format YYYY-MM-DD)
Return only incidents from a certain date (format YYYY-MM-DD)
Page number to return. Starts at 1.
Number of incidents per page. Default is 10, maximum is 50.
List only resolved or unresolved incidents. Use false to list active incidents
Filter incidents belonging to a specified team when using global API token
Filter incidents belonging to a specified monitor
Filter incidents belonging to a specified heartbeat
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
BETTER_STACK_LIST_JIRA_INTEGRATIONSTool to list all Jira integrations. Use when you need to retrieve and inspect all configured Jira integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_METADATATool to list all existing metadata. Use when you need to retrieve metadata records with optional filtering by team, owner resource ID, or owner resource type.
Input parameters
Page number to return. Starts at 1.
Targets metadata for a particular resource
Number of metadata records per page. Default is 50, maximum is 250.
Filters results to a specific team (global tokens only)
Owner types for metadata resources.
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
BETTER_STACK_LIST_MONITOR_GROUPSTool to list all monitor groups. Use when you need to retrieve existing monitor groups with optional team filtering and pagination support.
Input parameters
Page number to return. Starts at 1.
Number of monitor groups per page. Default is 50, maximum is 250.
Filters results to monitor groups belonging to a specified team when using a global API token
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
BETTER_STACK_LIST_MONITORSTool to list all monitors. Use when you need to retrieve existing uptime monitors with optional filtering by URL or name and pagination.
Input parameters
Filter monitors by their URL property
Page number to return. Starts at 1.
Number of monitors per page. Default is 50, maximum is 250.
Filter monitors by their pronounceable name property
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
BETTER_STACK_LIST_NEW_RELIC_INTEGRATIONSTool to list New Relic integrations. Use when you need to retrieve and inspect all configured New Relic integrations with pagination support.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations by team name. Useful when using a global API token to narrow results to a specific team.
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
BETTER_STACK_LIST_ON_CALL_EVENTSTool to list all events for a specific on-call schedule. Use when you need to retrieve the calendar of scheduled on-call periods for a team.
Input parameters
Identifier for the on-call schedule. Use 'default' to reference the team's default schedule.
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
BETTER_STACK_LIST_ON_CALL_SCHEDULESTool to list all on-call schedules. Use when you need to retrieve all configured on-call calendars.
Input parameters
Page number to return. Starts at 1.
Number of resources per page. Default is 50, maximum is 250.
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
BETTER_STACK_LIST_OUTGOING_WEBHOOKSTool to list all outgoing webhook integrations. Use when you need to retrieve configured webhook endpoints for event notifications.
Input parameters
Page number to return. Starts at 1.
Filter outgoing webhooks belonging to a specified team. Only applicable when using a global API token.
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
BETTER_STACK_LIST_PAGER_DUTY_WEBHOOKSTool to list PagerDuty integrations. Use when you need to retrieve and inspect all configured PagerDuty integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations by team name. Useful when using a global API token to narrow results to a specific team.
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
BETTER_STACK_LIST_POLICIESTool to list all escalation policies. Use when you need to retrieve existing escalation policies with optional filtering by team name.
Input parameters
Page number to return. Starts at 1.
Number of policies per page. Default is 50, maximum is 250.
Filter escalation policies by team name when using global API token
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
BETTER_STACK_LIST_POLICY_GROUPSTool to list all escalation policy groups. Use when you need to retrieve existing policy groups with optional team filtering and pagination support.
Input parameters
Page number to return. Starts at 1.
Number of policy groups per page. Default is 50, maximum is 250.
Filter policy groups belonging to a specified team when using global API token
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
BETTER_STACK_LIST_PROMETHEUS_INTEGRATIONSTool to list all Prometheus integrations. Use when you need to retrieve and inspect all configured Prometheus on-call integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_SINGLE_INCIDENTTool to retrieve detailed information about a single incident by its ID. Use when you need to get the full details of a specific incident including its status, timeline, affected regions, and notification settings.
Input parameters
The ID of the incident 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
BETTER_STACK_LIST_SLACK_INTEGRATIONSTool to list all Slack integrations. Use when you need to retrieve and inspect all configured Slack channel integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter Slack integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_SPLUNK_ON_CALL_INTEGRATIONSTool to list all Splunk On-Call integrations. Use when you need to retrieve and inspect all configured Splunk On-Call on-call integrations.
Input parameters
Page number to return. Starts at 1.
Number of integrations per page. Default is 50, maximum is 250.
Filter integrations belonging to a specified team. Only valid when using a global API token.
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
BETTER_STACK_LIST_STATUS_PAGE_GROUPSTool to list all status page groups. Use when you need to retrieve existing status page groups with optional pagination.
Input parameters
Page number to return. Starts at 1.
Number of status page groups per page. Default is 50; maximum is 250.
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
BETTER_STACK_LIST_STATUS_PAGE_GROUPS_STATUS_PAGESTool to list status pages within a specific status page group. Use when you need to retrieve all status pages belonging to a particular group with optional pagination.
Input parameters
Page number to return. Starts at 1.
The ID of the status page group to list status pages from
Number of status pages per page. Default is 50; maximum is 250.
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
BETTER_STACK_LIST_STATUS_PAGE_REPORTSTool to list all reports on a status page. Use when you need to retrieve existing status page reports with optional pagination via `page` and `per_page`.
Input parameters
Page number to return. Starts at 1.
Number of reports per page. Default is 50, maximum is 250.
The numeric ID of the status page (e.g., '221582'). Obtain this from the list_status_pages 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
BETTER_STACK_LIST_STATUS_PAGE_REPORT_STATUS_UPDATESTool to list all status updates for a status page report. Use when you need to retrieve updates posted on a specific status page report with optional pagination.
Input parameters
Page number for pagination. Starts at 1.
Number of items per page. Default is 50, maximum is 250.
Identifier for your status page report. Obtain this from the list_status_page_reports action.
Identifier for your status page. Obtain this from the list_status_pages 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
BETTER_STACK_LIST_STATUS_PAGESTool to list all your status pages. Use when you need to retrieve existing status pages with optional pagination.
Input parameters
Page number to return. Starts at 1.
Number of status pages per page. Default is 50; maximum is 250.
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
BETTER_STACK_LIST_STATUS_PAGE_SECTIONSTool to list all sections of a specific status page. Use when you need to retrieve the existing sections within a status page.
Input parameters
Page number to return. Starts at 1.
Number of sections per page. Default is 50, maximum is 250.
The identifier for your status 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
BETTER_STACK_LIST_STATUS_PAGES_RESOURCESTool to list all resources on a status page. Use when you need to retrieve existing resources with optional pagination.
Input parameters
Page number to return. Starts at 1.
Number of resources per page. Default is 50; maximum is 250.
The ID of the status 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
BETTER_STACK_LIST_URGENCIESTool to list all severity levels (urgencies). Use when you need to retrieve existing incident severity configurations with their notification settings.
Input parameters
Filters severities belonging to a specified team when using a global API token
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
BETTER_STACK_LIST_URGENCY_GROUPSTool to list all urgency groups (severity groups). Use when you need to retrieve existing urgency groups with optional team filtering and pagination support.
Input parameters
Page number to return. Starts at 1.
Number of urgency groups per page. Default is 50, maximum is 250.
Filter urgency groups belonging to a specified team when using global API token
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
BETTER_STACK_RESOLVE_INCIDENTTool to resolve an ongoing incident. Use when you need to mark an incident as resolved and close it. Resolving an incident signals that the issue has been fixed and stops any further escalations.
Input parameters
The ID of the incident to resolve
Email or custom identifier of the person or system resolving the incident
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
BETTER_STACK_UPDATE_ESCALATION_POLICYTool to update an existing escalation policy. Use when you need to modify policy attributes like name, repeat settings, or escalation steps. Only the fields you provide will be updated (partial updates supported).
Input parameters
The name of this escalation policy
An array of escalation policy steps to replace existing steps
The ID of the escalation policy to update
How many times to repeat the escalation policy if unacknowledged
How long in seconds to wait before each repetition
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
BETTER_STACK_UPDATE_HEARTBEATTool to update an existing heartbeat configuration. Use after retrieving a heartbeat and choosing which fields to change.
Input parameters
Whether to send an SMS to the on-call person
Whether to call the on-call person on failure
The name of the service for this heartbeat
Whether to send a push notification on failure
Whether to send an email to the on-call person
Acceptable delay beyond period in seconds (min 0)
Set true to pause monitoring; false to resume
How often to expect the heartbeat in seconds (min 30)
ID of the escalation policy to assign
Seconds to wait before escalating alert to team. Leave blank to disable team escalation.
Index position within a heartbeat group
The ID of the heartbeat to update
Send a critical push ignoring mute and Do Not Disturb
End of maintenance window each day (HH:MM:SS)
Days for daily maintenance window. Use both days for overnight windows.
Start of maintenance window each day (HH:MM:SS)
ID of the heartbeat group to assign
Timezone for maintenance window. See Rails TimeZone list.
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
BETTER_STACK_UPDATE_HEARTBEAT_GROUPUpdates an existing heartbeat group's properties. Use to rename a group, change its display order, or pause/resume monitoring for all heartbeats in the group.
Input parameters
New name for the heartbeat group visible in the dashboard.
Set to true to pause monitoring for all heartbeats in this group; false to resume monitoring.
Zero-based index to control the display order of heartbeat groups in the dashboard.
The ID of the heartbeat group to update. Use list heartbeat groups to find available IDs.
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
BETTER_STACK_UPDATE_INCIDENT_COMMENTTool to update an existing comment on an incident. Use when you need to modify the content of a comment that was previously added to a Better Stack incident.
Input parameters
The updated content of the comment. Markdown is supported for formatting.
The ID of the comment to update
The ID of the incident containing the comment
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
BETTER_STACK_UPDATE_MONITORTool to update an existing uptime monitor configuration. Use when you need to modify settings of an existing monitor such as check frequency, notification preferences, URLs, or monitoring behavior.
Input parameters
Enable SMS notifications when monitor goes down or recovers.
The URL or host to monitor. For HTTP/HTTPS monitors use full URL with protocol. For TCP/UDP/SMTP/POP/IMAP use hostname or IP. For DNS monitors use the domain to query.
Enable phone call alerts when monitor goes down or recovers.
Port number for TCP, UDP, SMTP, POP, or IMAP monitors. Required for these monitor types.
Enable push notifications to on-call personnel when monitor goes down or recovers.
Enable email notifications when monitor goes down or recovers.
If true, the monitor is paused and will not perform checks. If false, monitoring resumes.
List of regions from which to perform checks. Available: us (United States), eu (Europe), as (Asia), au (Australia).
ID of the escalation policy to use for this monitor. Controls who gets notified and in what order.
Seconds to wait before escalating to the team after first notification. Leave blank to disable team escalation.
IP version to use for checks.
The ID of the monitor to update
Verify SSL certificates for HTTPS monitors. If false, monitors will accept invalid/self-signed certificates.
HTTP method for status/keyword monitors.
Type of monitor to create or update.
Body content to send with POST/PUT/PATCH requests. Required for DNS monitors (specify the DNS record type to query).
Password for HTTP Basic Authentication. Used with auth_username.
Username for HTTP Basic Authentication. Used with auth_password.
Name identifier for playwright monitor scenarios. Used to distinguish between different automation scripts.
If enabled, alerts will override Do Not Disturb settings and mute schedules. Use for critical monitors only.
End time of daily maintenance window in HH:MM:SS format. Checks resume after this time.
Advance warning in days before SSL certificate expiration. Allowed values: 1, 2, 3, 7, 14, 30, or 60.
How often to check the monitor in seconds. Minimum is 30 seconds. Default is 30.
Number of seconds the monitor must be up before automatically resolving any open incidents.
List of HTTP headers to send with the check request.
Request timeout in milliseconds for server/port monitors or seconds for other types.
Automatically follow HTTP redirects when checking status/keyword monitors.
Days of the week to skip monitoring checks during maintenance windows. Combine with maintenance_from and maintenance_to.
Start time of daily maintenance window in HH:MM:SS format. Checks are skipped during this window on specified maintenance_days.
ID of the monitor group to assign this monitor to. Used for organizing monitors.
Whether to remember cookies across checks and redirects.
For keyword monitors: the text that must be present in the response. For keyword_absence monitors: the text that must NOT be present. Required for keyword and UDP monitor types.
Advance warning in days before domain expiration. Allowed values: 1, 2, 3, 7, 14, 30, or 60.
JavaScript code for playwright monitor type. Defines browser automation scenario to execute during checks.
Human-readable name for the monitor displayed in the dashboard.
How long in seconds to observe failures before creating an incident. Helps avoid false alerts from transient issues.
ID of the escalation policy for SSL certificate and domain expiration alerts. Null sends email to team.
Timezone for maintenance window times. Use Rails TimeZone values. Defaults to UTC.
Key-value pairs of environment variables accessible within playwright scripts. Useful for parameterizing automation scenarios.
Array of acceptable HTTP status codes for successful checks. Used with expected_status_code monitor type.
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
BETTER_STACK_UPDATE_MONITOR_GROUPUpdates an existing monitor group's properties. Use to rename a group, change its display order, or pause/resume monitoring for all monitors in the group.
Input parameters
Display name for the monitor group visible in the dashboard.
Set to true to pause monitoring for any existing monitors in the group; false to resume monitoring.
Numeric value controlling monitor group sort order in the dashboard.
The ID of the monitor group to update. Use list monitor groups to find available IDs.
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
BETTER_STACK_UPDATE_ON_CALL_SCHEDULETool to update an on-call schedule's name. Use when you need to rename an existing on-call calendar.
Input parameters
The name of the schedule
The ID of the on-call schedule you want to update
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
BETTER_STACK_UPDATE_OUTGOING_WEBHOOKTool to update an existing outgoing webhook integration. Use when you need to modify the configuration of a webhook endpoint.
Input parameters
Webhook destination URL
Integration display name
Trigger on incident creation
The ID of the Outgoing Webhook integration you want to update
Trigger when incident reopened
Trigger when incident resolved
Trigger when incident acknowledged
Custom webhook template attributes such as HTTP method, headers, and body.
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
BETTER_STACK_UPDATE_POLICY_GROUPUpdates an existing escalation policy group's properties. Use to rename a group or change its display order.
Input parameters
New name for the escalation policy group visible in the dashboard.
Zero-based index to control the display order of escalation policy groups in the dashboard.
The ID of the escalation policy group to update. Use list policy groups to find available IDs.
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
BETTER_STACK_UPDATE_SOURCE_GROUPUpdate an existing source group in Better Stack Logs/Telemetry. Use this to rename a source group or change its sort order. Requires a Telemetry API token (different from Uptime API token).
Input parameters
The new display name of the source group
Order index to control group sorting. Must be non-negative.
The ID of the source group you want to update
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
BETTER_STACK_UPDATE_STATUS_PAGE_GROUPTool to update an existing status page group. Use when you need to modify the name or display order of a status page group.
Input parameters
A descriptive label for the group visible in the dashboard.
Numeric value determining the group's display order.
The ID of the status page group to update. Use list status page groups to find available IDs.
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
BETTER_STACK_UPDATE_STATUS_PAGE_REPORTTool to update an existing status page report. Use when you need to modify the title, timing, or affected resources of an existing incident or maintenance report.
Input parameters
The updated title/name for the status page report
ISO-8601 timestamp when the report concludes. Required for maintenance-type reports.
The numeric ID of the status report to update (e.g., '824282').
ISO-8601 timestamp when the report becomes active. Defaults to current time if not provided.
The numeric ID of the status page (e.g., '221582'). Obtain this from the list_status_pages action.
List of status page resources affected by this report, with their status. Each object must contain status_page_resource_id and status fields.
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
BETTER_STACK_UPDATE_STATUS_PAGE_RESOURCETool to update an existing status page resource. Use when you need to modify the display name, position, widget type, or other properties of a resource on a status page.
Input parameters
Zero-indexed placement; unspecified defaults to end position
Helper text displayed as an icon
How the resource appears on your public status page
The specific resource requiring modification
Display format options: plain, history, response_times, or chart_only
Type of resource on the status page
Boolean preventing position reordering when enabled
The identifier of your status page
Incident impact settings: any_incident, no_incident, or incident_matching_metadata
Degraded status trigger: any_incident, no_incident, or incident_matching_metadata
Section assignment (defaults to first section 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
BETTER_STACK_UPDATE_STATUS_PAGESTool to update an existing status page configuration. Use when modifying settings like company info, appearance, access control, or display preferences.
Input parameters
Theme options for status pages (v2 only).
Design version options for status pages.
Layout options for status pages (v2 only).
Number of days to display on the status page. Between 7 and 365 days
URL of the logo image. Image should be under 20MB
Password for accessing the status page (when password_enabled is true)
Timezone in Rails TimeZone format
Subdomain for the status page. Must be globally unique
Custom CSS to apply to the status page
URL of the company homepage
URL for contact or support page
Announcement text to display on the status page
Company name shown on the status page
List of IP addresses allowed to access the page
Whether visitors can subscribe for updates
Custom domain for the status page
Identifier for the status page being modified
Custom navigation links for the status page
Whether a password is required to view the page
Whether automatic reports are enabled
Custom JavaScript to apply to the status page
Google Analytics tracking ID
Minimum incident duration in seconds to be displayed
ID of the status page group to assign this page to
Whether the page should be hidden from search engines
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
BETTER_STACK_UPDATE_STATUS_PAGE_SECTIONTool to update an existing status page section. Use when reorganizing sections or changing their display. Leave name blank to hide the section header.
Input parameters
Section title. Omit to hide the header.
Zero-indexed placement on the status page. Unspecified adds to end.
The section identifier you want to modify.
The identifier for your status 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
BETTER_STACK_UPDATE_STATUS_PAGE_STATUS_REPORT_STATUS_UPDATETool to update an existing status update for a status report. Use when you need to modify the message, affected resources, or other details of a previously created status update.
Input parameters
Message associated with the status update, providing details about the current state or actions taken.
ISO-8601 timestamp for publication time. If not provided, uses the original published time.
Your status page identifier. Obtain from list_status_pages action.
Your status page report identifier. Obtain from list_status_page_reports action.
Your status update identifier. Obtain from list_status_page_report_status_updates action.
Array of affected resources with their current status. If provided, must contain at least one resource.
Send notification email to subscribers. Default is false.
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
BETTER_STACK_UPDATE_URGENCIESTool to update an existing severity level (urgency) configuration. Use when you need to modify notification settings or name for a specific severity level.
Input parameters
Enables SMS notifications for new incidents at this severity level
Enables phone calls for new incidents at this severity level
The identifier for this severity level
Enables push notifications for new incidents at this severity level
Enables email notifications for new incidents at this severity level
The ID of the severity level to update
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
BETTER_STACK_UPDATE_URGENCY_GROUPTool to update an existing urgency group (severity group). Use when you need to modify the name or sort order of a severity group.
Input parameters
The display name for the group visible in the dashboard.
Determines the sorting order of the severity group. Must be non-negative.
The ID of the urgency group (severity group) to update. You can get this from the list urgency 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
No publicly available marketplace agent is found using this tool yet. There are 47 agents privately built on Nagent that already use Better Stack.
Build on Nagent
Connect Better Stack 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 Better Stack, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Better Stack is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Better Stack is connected, you configure its 117 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Better Stack 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 Better Stack event fires, the agent kicks off automatically.
Every Better Stack 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 Better Stack ships with 117 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Better Stack together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Better Stack-based workflows tailored to your business.