Connect Better Stack integrations
VerifiedUptime monitoring, incident management and status pages, connected to WEXTL workflows and AI agents. Send Better Stack deploys, issues and webhook events into your engineering workflows. When Watch Events fires, update the docs, notify a team or continue with Get a Catalog Attribute.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Better Stack integration
Triggers can detect changes in Better Stack and run actions that can create, search or modify data inside Better Stack automatically[3], exactly how you set them.
- Watch Events Starts the workflow the moment Better Stack delivers an event through a webhook. Each run receives the Event, its Data and any Comment.
- Watch New Incidents Runs a recurring check on your account and starts the workflow for every incident created since the previous one. Use Monitor or Heartbeat to follow one source, and Limit to cap how many the first check returns, up to 40.
- Get a Catalog Attribute Reads an attribute of a catalog relation, including whether it is primary and where it is positioned.
- Get a Catalog Record Fetches a catalog record with the values stored for each attribute of its relation.
- Get a Catalog Relation Looks up a catalog relation, with its description and the match rule that applies records to incidents.
- Get a Heartbeat Shows a heartbeat with its expected ping interval, grace period and alert settings, plus its relationships.
- Get a Heartbeat Group Pulls a heartbeat group and shows whether the heartbeats inside it are paused, plus its sort position.
- Get a Monitor Gets a monitor with its type, URL or host, check frequency and regions, along with its relationships.
- Get a Monitor Group Reads a monitor group, including whether its monitors are paused and where the group sits in the list.
- Get a Severity Reads a severity level and the alert channels it uses when a new incident opens.
- Get a Severity Group Returns a group of severity levels and its position in the dashboard list.
- Get a Status Page Looks up a status page and its settings, such as subdomain, design and whether it is published.
- Get a Status Page Group Fetches a group of status pages in the dashboard, with its position in the list.
- Get a Status Page Report Returns a report shown on a status page, which is either a manual incident or planned maintenance, with its relationships.
- Get a Status Page Resource Reads an item shown on a status page, including the name displayed there and how an incident affects it.
- Get a Status Page Section Retrieves a section of a status page, along with its heading and where it sits from the top.
- Get a Status Page Subscriber Checks a subscriber of a status page and the e-mail address it uses.
- Get a Status Update Reads one update posted under a status page report, including its message.
- Get a Team Member Gets a member of your Better Stack team, returning the Attributes of that person.
- Get an Escalation Policy Returns an escalation policy, which decides who is alerted and when an incident reaches the whole team.
- Get an Escalation Policy Group Retrieves a group that organises escalation policies, with its position in the dashboard list.
- Get an Incident Opens one incident and returns its attributes along with its relationships.
- Get an Incident Comment Reads one comment from the thread of an incident. The text may contain Markdown.
- Get an Incoming Webhook Inspects an incoming webhook, including its escalation policy, recovery period and the rules that start, acknowledge and resolve incidents.
- Get an On-Call Event Displays one on-call event, reporting who is on call between its start and end and whether it overrides the regular schedule.
- Get an On-Call Rotation Shows the rotation of a schedule, with its Rotation Length, Rotation Interval, Users, Timezone and Working Hours.
- Get an On-Call Schedule Looks up one on-call schedule and returns its attributes and relationships.
- Get the Availability of a Heartbeat Reports how available a heartbeat was over a period. Narrow the period with From and To, or leave From blank for the Better Stack default.
- Get the Availability of a Monitor Calculates availability for a monitor over a period. Narrow the period with From and To, or leave From blank to use the Better Stack default.
- Get the Response Times of a Monitor Fetches the response time measurements recorded for a monitor, which show how quickly its target answered checks.
- Get the Usage by Product Reports usage of one Better Stack product between From and To. Use Resolution to set the bucket size, Dimension for cost or another dimension, and Limit for how many results. A Global API token is needed.
- Get the Usage Overview Summarises usage across your account for a period. Without From the range starts 29 days before To, and without To it ends today. The range can span at most 400 days. Use Limit to set how many results are returned.
- List Catalog Attributes Returns the attributes defined on one catalog relation. Use Limit to restrict the number returned.
- List Catalog Records Fetches the records of a catalog relation, together with their attribute values. Set Limit to the number you want.
- List Catalog Relations Shows every catalog relation on your account. Set Limit to the number you want.
- List Escalation Policies Retrieves your escalation policies with their Attributes. Use Limit to cap the list.
- List Escalation Policy Groups Browses the escalation policy groups on your account, giving the Type and Attributes of each.
- List Heartbeat Groups Collects the heartbeat groups on your account together with their Attributes and Type.
- List Heartbeats Pulls the heartbeats in your account, along with their relationships. Set Limit to control how many are returned.
- List Incident Comments Gathers the comments added to one incident. Use Limit to cap the list.
- List Incidents Finds incidents on your account. Narrow them by a From and To date, by Monitor or Heartbeat, and by Resolved or Acknowledged status, with a blank value meaning both.
- List Incoming Webhooks Lists the incoming webhooks on your account, giving the ID, Type and Attributes of each.
- List Metadata Reads the key and value pairs saved on monitors, heartbeats, incidents and incoming webhooks. Use Owner Type, plus Owner ID, to see only one resource.
- List Monitor Groups Fetches the monitor groups on your account, along with their Attributes.
- List Monitors Retrieves your monitors. Use URL or Name to keep only the ones that match.
- List Monitors in a Group Returns the monitors found in one monitor group, together with their relationships.
- List On-Call Events Shows the events on an on-call schedule. Set From to keep events that start at or after a time, and To for events that end at or before one.
- List On-Call Schedules Collects your on-call schedules together with their relationships and Attributes.
- List Roles Returns the roles available in Better Stack, listing their Type and Attributes.
- List Severities Pulls your severity levels, showing the Type and Attributes of each.
- List Severity Groups Gathers the severity groups on your account, listing their Attributes and Type.
- List Status Page Groups Browses the status page groups on your account, with their Attributes and Type.
- List Status Page Reports Lists the status reports on a chosen status page, together with their relationships and Attributes, one result per report.
- List Status Page Resources Retrieves the resources attached to one status page. Use Limit to cap the list.
- List Status Page Sections Shows the sections of one status page, giving the ID and Attributes of each.
- List Status Page Subscribers Fetches the subscribers of one status page, giving their Attributes and ID.
- List Status Pages Shows the status pages on your account, with their ID and Attributes.
- List Status Pages in a Group Finds the status pages inside one status page group, giving the ID and Attributes of each page.
- List Status Updates Gathers the updates attached to one status report, listing the Attributes and Type of each.
- List Team Members Returns the people on your Better Stack team with their attributes.
- List the Incident Timeline Returns the timeline entries of one incident. An older incident can be reached by mapping its ID from an earlier step.
- Change the Incident Status Moves an incident to a new state: Action offers Acknowledge, Resolve and Reopen. Use By to record who made the change. The updated incident is returned.
- Change the Role of a Team Member Gives an existing team member a different Role, taken from your list of roles. Use Member to say whose role changes.
- Create a Catalog Attribute Gives a catalog relation another attribute under a Name. Turn on Primary to match it against the incident metadata key of the same name, and give a Position to order it, lowest first.
- Create a Catalog Record Stores one record in a catalog relation. Fill Attributes with one row per attribute, each row holding its values.
- Create a Catalog Relation Defines a catalog relation under a Name, with an optional Description. Set Match Rule to apply a record when any primary value or every primary value matches the incident metadata.
- Create a Heartbeat Sets up a heartbeat that expects a ping every Expected Every seconds and counts one as missed after the Grace Period. Choose an Escalation Policy to decide who is alerted, or alert the on-call person with the e-mail, SMS or Call switches.
- Create a Heartbeat Group Starts a group for heartbeats under a Name. Sort it among the other groups with Position, or begin with every heartbeat inside it paused by using Paused.
- Create a Monitor Starts a monitor that checks a chosen Monitor Type against a URL or Host. Use Check Frequency and Regions to set how often and where it runs, and Escalation Policy to decide who is alerted.
- Create a Monitor Group Sets up a home for monitors under a Name. Turn on Paused to pause every monitor in that group.
- Create a Severity Defines a severity level that decides how people are notified when an incident of that level opens. Pick channels with Send SMS, Call, Send E-mail, Send Push Notification and Send Critical Alert, and file it under a Severity Group.
- Create a Severity Group Adds a named group for severities, shown in the dashboard. Use Position to order it in the list, lowest first.
- Create a Status Page Creates a status page for your company from a Company Name, Time Zone and Subdomain, which must be unique across Better Stack. Add a Custom Domain, a Design, History Days or a Password to shape who sees what.
- Create a Status Page Group Creates a named group for status pages, shown in the dashboard. Use Position to place it in the list.
- Create a Status Page Report Publishes a report with a Title and the first status update Message. Choose a Report Type, either a manual incident or planned maintenance, and turn on Notify Subscribers to e-mail them.
- Create a Status Page Resource Adds an item to a status page based on its Resource Type, shown there under the Public Name. Use Mark as Down When and Mark as Degraded When to define how an incident affects it.
- Create a Status Page Section Sets up a section for grouping the items of a status page. Leave Name blank to hide its header, and use Position with Fixed Position to place it exactly.
- Create a Status Page Subscriber Subscribes an E-mail address to the updates of a status page.
- Create a Status Update Posts a follow-up on a status page report with the text from Message. Use Affected Resources for a manual report and leave it out for maintenance. Turn on Notify Subscribers to send an e-mail.
- Create an Escalation Policy Group Makes a group for escalation policies, shown in the dashboard under its Name. Use Position to place it in the list, lowest first.
- Create an Incident Opens an incident on behalf of a Requester E-mail, described by its Summary. Add a Name, a longer Description and an Escalation Policy, or alert the on-call person with Send E-mail, Send SMS or Call.
- Create an Incident Comment Posts a Comment on an incident, with Markdown supported. Set Tag Member to notify a colleague about it. The new comment is returned.
- Create an Incoming Webhook Creates a webhook endpoint that raises incidents from outside requests. Give it a Name and an Escalation Policy, and set Recovery Period for how long to wait after a resolving request. Start, Acknowledge and Resolve rules decide when each happens.
- Create an On-Call Event Puts people on call for a stretch of time on a schedule, between Starts At and Ends At. Everyone chosen as On-Call Users must belong to the schedule team. Turn on Override so the event beats regular scheduled ones.
- Create an On-Call Rotation Rotates On-Call Users through a schedule, each person on call for the Rotation Length counted in the chosen Interval. Rotations run from Start At to End At. Use Working Hours to restrict when anyone is paged.
- Create an On-Call Schedule Creates a new on-call schedule under a Name, which can then hold events and rotations.
- Delete a Catalog Attribute Deletes an attribute that belongs to a catalog relation.
- Delete a Catalog Record Removes a record that belongs to one catalog relation.
- Delete a Catalog Relation Deletes a catalog relation, the set of attributes and records matched against incident metadata.
- Delete a Heartbeat Removes a heartbeat that expects regular pings.
- Delete a Heartbeat Group Deletes a group that can pause and organise heartbeats together.
- Delete a Monitor Deletes a monitor that checks a website, server or port.
- Delete a Monitor Group Removes a group that holds monitors and can pause them together.
- Delete a Severity Removes a severity level used to decide how people are notified of new incidents.
- Delete a Severity Group Deletes a dashboard group that holds severity levels.
- Delete a Status Page Removes the status page on which visitors check the health of your services. Check first, it is final.
- Delete a Status Page Group Deletes a dashboard group that collects status pages.
- Delete a Status Page Report Removes a report, either an incident or planned maintenance, from a status page.
- Delete a Status Page Resource Deletes an item from a status page, found by Status Page and Resource.
- Delete a Status Page Section Removes a section that groups the items of a status page.
- Delete a Status Page Subscriber Unsubscribes an e-mail address from the updates of a status page.
- Delete a Status Update Deletes one update that was posted under a status page report.
- Delete an Escalation Policy Removes an escalation policy, the setting that decides who gets alerted.
- Delete an Escalation Policy Group Deletes a dashboard group used to organise escalation policies.
- Delete an Incident Removes an incident from your Better Stack account. Plan on it being final.
- Delete an Incident Comment Deletes a note that was posted in the thread of an incident.
- Delete an Incoming Webhook Removes an incoming webhook that raises incidents from outside requests.
- Delete an On-Call Event Deletes a single on-call shift that was added to a schedule.
- Delete an On-Call Rotation Removes the rotation configured on an on-call schedule.
- Delete an On-Call Schedule Deletes an on-call schedule that people can be placed on through events and rotations.
- Invite a Team Member Sends an invitation to a new person by E-mail. Leave Role blank to invite them as Responder.
- Make an API Call Calls the Better Stack REST API directly with a free-form request under your saved credential.
- Remove a Team Member Removes one person from the Better Stack team.
- Remove a Team Member by E-mail Removes the member with a given E-mail from the team, or cancels the invitation sent to that address.
- Send an Incident Escalation Escalates an incident to a person, an on-call schedule, an escalation policy or a whole team. Turn on Call, Send SMS, Send E-mail, Send Push Notification or Send Critical Alert to pick the channels.
- Set Metadata Saves a Key and its Values on a monitor, heartbeat, incident or incoming webhook. Mode either replaces existing values or adds to them, and Remove Key deletes the key with all its values.
- Set the Future On-Call Events Replaces all future events of a schedule with a new set. Each Events entry needs Starts At, Ends At and Users, and may set Override.
- Update a Catalog Attribute Edits an attribute of a catalog relation, which always needs its Name sent again even when it is unchanged. Use Primary to match the attribute against the incident metadata key of the same name, and Position to reorder it.
- Update a Catalog Record Rewrites a catalog record through Attributes, which replaces all of its values, so an attribute left out ends up empty.
- Update a Catalog Relation Changes a catalog relation, sending its Name again even when unchanged. Add a Description, and use Match Rule to choose whether one or all primary values must match incident metadata.
- Update a Heartbeat Adjusts a heartbeat, including Expected Every, its Grace Period, the alert switches and the maintenance window. Choose entries under Clear Fields to empty them, which wins over a value in the same field.
- Update a Heartbeat Group Changes a heartbeat group: its Name, a sort value through Position, or whether it is Paused.
- Update a Monitor Changes how a monitor checks its target, such as Check Frequency, Regions, Request Timeout and Confirmation Period. Use Replace Request Headers to swap all existing headers, and Clear Fields to empty chosen values.
- Update a Monitor Group Modifies a monitor group by renaming it with Name, moving it with Position, or switching Paused on and off.
- Update a Severity Edits a severity level. Rename it with Name, change which channels fire for new incidents through Send SMS, Call, Send E-mail, Send Push Notification and Send Critical Alert, or move it with Severity Group.
- Update a Severity Group Updates a dashboard group of severities, with a new Name or a different Position in the list.
- Update a Status Page Changes the settings of a status page, such as Company Name, Subdomain, Design, History Days, Published and Password Protect. Use Clear Fields to empty chosen values.
- Update a Status Page Group Edits a dashboard group of status pages. Use Name to relabel it and Position to move it in the list.
- Update a Status Page Report Updates a report on a status page. Set a new Title, or move the window with Starts At and Ends At, where changing Ends At reschedules the end of a maintenance.
- Update a Status Page Resource Edits an item displayed on a status page: the Public Name, the Widget, an Explanation and its Position. Use Mark as Down When and Mark as Degraded When to define how an incident affects it.
- Update a Status Page Section Changes a section of a status page. Leave Name blank to hide its header, use Position to move it from the top, and turn on Fixed Position to pin it there exactly.
- Update a Status Page Subscriber Edits the resources that a subscriber of a status page is notified about.
- Update a Status Update Rewrites an update posted under a report. Change its Message or Published At value, replace the resources it affects with Affected Resources, or send an e-mail by switching on Notify Subscribers.
- Update an Escalation Policy Group Modifies a dashboard group of escalation policies. Give it a new Name or a different Position in the list, lowest first.
- Update an Incident Comment Rewrites a comment on an incident with the text of New Text, and Markdown is supported.
- Update an Incoming Webhook Reconfigures an incoming webhook, including its Escalation Policy and Recovery Period. Set Start Rule Mode, Acknowledge Rule Mode and Resolve Rule Mode to decide when requests change an incident.
- Update an On-Call Event Moves or reassigns an existing shift on a schedule. Pick a new window through Starts At and Ends At, change who covers it with On-Call Users, or turn on Override to beat regular events.
- Update an On-Call Schedule Gives an on-call schedule a new Name, the only field this module changes.
How to integrate Better Stack in automation workflow?
Better Stack in three steps: start with "Watch Events", connect one credential, then add your next step.
STEP 1
Select Better Stack in workflow
Add the "Watch Events" trigger from Better Stack to the canvas[4].
STEP 2
Connect Better Stack
Fill in the Better Stack credential once. All 137 Better Stack modules use it[3].
STEP 3
Build a workflow
Add "Get a Catalog Attribute" or "Get a Catalog Record" after it, then connect any app[5] or the HTTP node.
How Better Stack connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Better Stack app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Better Stack supports.
Full Better Stack API documentationThe following table illustrates what fields Better Stack integration require during authorization flow inside our workflow builder[4].
Connect Better Stack
API Token*Text
••••••••
Team Name*Text
••••••••
| Field | Type | Help |
|---|---|---|
API TokenRequired | password | In Better Stack, open API tokens. Copy a Team-based token from the Uptime / Incidents section (it works for one team), or a Global API token (it works for all your teams). |
| Team Name | text | Only needed with a Global API token. Type the exact team name that should own what you create. Leave empty with a Team-based token. |
Connect Better Stack to popular apps on WEXTL
Enter a name of the other app you want to sync with Better Stack below. Click on selected app to explore integration options with Better Stack. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Better Stack integration
Select Watch New Incidents trigger from Better Stack - this will be a starting point in your automation. Whenever event happens in Better Stack, workflow will start[7] from Watch New Incidents node.
Search for Create an Incident Comment, connect it as the next step of integration sequence. You can use filters between Watch New Incidents and Create an Incident Comment, so only important data pass from Watch New Incidents to the next step. WEXTL gives you full control over the process of Better Stack automation. All parts of workflow are visible on the canvas[4].
Better Stack on WEXTL has 138 modules for creating developer tools automations. Explore Better Stack documentation for more.
- Better StackWatch New Incidents
- Azure StoragePerforms action
OR
- Azure StorageTriggers
- Better StackCreate an Incident Comment
Frequently asked questions
Common questions about automating Better Stack in your workflows.
What triggers does Better Stack support?
Better Stack has 2 triggers, including "Watch Events" and "Watch New Incidents". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Better Stack?
Integration has 136 actions, including "Get a Catalog Attribute", "Get a Catalog Record", and "Get a Catalog Relation", and more. Refer to our Better Stack Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 137 Better Stack modules, like "Get a Catalog Attribute", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Better Stack credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Better Stack?
Through the official Better Stack API: 137 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Better Stack?
Yes. "Watch Events" is instant: Better Stack pushes each event, so there is no polling delay.
Why use WEXTL platform for Better Stack automation?
WEXTL is an AI-first visual canvas: describe the Better Stack flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Better Stack integration.
- Better Stack integration source code, module specs and credentials implementation.
- Internal Better Stack integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Better Stack vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Better Stack App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Better Stack app documentation
Explore how WEXTL® crafted Better Stack integration page documentation. Used sources, the role of AI, and how the team validates the result.




















