Better Stack and Postman Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect Better Stack and Postman to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Better Stack and Postman
Detailed info you need to know about Better Stack and Postman integrations in WEXTL. Explore which modules apps support and how you connect them.
Better Stack

Uptime monitoring, incident management and status pages.[5]
Postman

Manage Postman collections, environments, mock servers, monitors, specs and workspaces.[6]
How to connect Better Stack to Postman
Set up your Better Stack and Postman integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Better Stack and Postman
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Better Stack and Postman nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Better Stack and Postman. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Better Stack and Postman work in WEXTL?
WEXTL exposes actions and triggers for Better Stack and Postman that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Better Stack triggersPostman actions
Better Stack modules
- 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.
- Get a Catalog Attribute Reads an attribute of a catalog relation, including whether it is primary and where it is positioned.
Postman modules
- Add a Collection to an API Attaches collection content to an API from an Operation Type and Data (JSON). It returns the stored Data and Operation Type.
- Create a Collection Starts a collection in a workspace. Prefill it with Items (JSON), Variables, Auth (JSON) and Events (JSON), or add a Description. It returns the Id, Name and Uid.
- Create a Collection Comment Leaves a Comment on a whole collection. Use Thread ID to reply in an existing thread, and Tagged Users to mention people by User ID or Username.
- Create a Collection Folder Makes a folder in a collection from a Name. Use Parent Folder ID to nest it inside another folder.
- Create a Collection Pull Request Opens a pull request that proposes merging a forked collection into a Destination. Assign Reviewers, give it a Title and add a Description to explain the change.
- Create a Collection Request Saves an API request in a collection with its Method, URL, Headers, Query Parameters and body. Use Folder ID to file it in a folder, or add Auth (JSON) and Events (JSON).
- Create a Collection Response Stores an example reply under the request with the Request ID. Add Status Text, Headers and a Body, and use Body Language for the syntax of the Body.
- Create a Collection Webhook Sets up a webhook for a collection under a Name. Add an Environment to run the collection with.
- Create a Folder Comment Posts a Comment on one folder of a collection, using the Folder ID. Use Thread ID to answer an existing thread and Tagged Users to mention people.
- Create a Mock Response Defines a server response on a mock server from a Name. Use Headers, Language and Body to shape what the mock sends back.
- Create a Mock Server Spins up a mock server from a collection in a workspace. Pick an Environment, give it a Name, and set Private to restrict callers. It returns the Mock Url.
- Create a Monitor Schedules a collection run on a Cron expression in a Time Zone. Turn on Active to run it, and tune Retry Attempts, Notification Limit, Email on Error and Email on Failure.
- Create a Request Comment Writes a Comment on one request of a collection, using its Request ID. Reply in a thread with Thread ID or mention people through Tagged Users.
- Create a Response Comment Adds a Comment to a saved example, using its Response ID. Set Thread ID to continue a thread, or Tagged Users to mention teammates.
- Create a Spec Writes an API spec into a workspace from a Name, a Type and its Files. Each file carries a Path and its Content.
- Create a Spec File Puts another file into a spec at the Path of your choice, along with its Content. The new file returns with its Id, Created At and Created By.
- Create a Spec Version Tag Marks the current state of a spec with a Name, giving you a version to return to later.
- Create a Workspace Opens a workspace from a Name and a Type. Add context with Description and About, and assign it to a team through Team.
- Create a Workspace Update Publishes a post to a workspace with a Topic, a Description and a Category. Add Related Resources, each with a Resource and Resource ID, to link what it covers.
- Create an API Registers an API in a workspace from a Name, with an optional Summary and Description. The API is returned with those three values.
- Create an API Version Releases a version of an API from a Name. Link Schema IDs and Collection IDs to it, and add Release Notes to explain what changed.
- Create an Environment Builds an environment in a workspace from a Name. Add Variables, each with a Key, Value, Type, Enabled flag and Description, to start with values.
- Delete a Collection Deletes a collection, the saved set of folders and requests.
- Delete a Collection Comment Deletes the collection comment that carries a Comment ID.
- Delete a Collection Folder Removes the folder with a given Folder ID from its collection.
- Delete a Collection Request Deletes a single request from its collection, using Request ID.
- Delete a Collection Response Removes a saved example response from its request, using Response ID.
- Delete a Folder Comment Removes a folder comment by its Comment ID, from the Folder ID folder.
- Delete a Mock Response Removes a mock server response by Server Response ID.
- Delete a Mock Server Removes a mock server, the fake API backed by a collection.
- Delete a Monitor Removes a scheduled monitor from your Postman account.
- Delete a Request Comment Removes a request comment by Comment ID, under the request with the Request ID.
- Delete a Response Comment Removes a comment by Comment ID from the saved response with the Response ID.
- Delete a Spec Deletes an API spec from your workspace.
- Delete a Spec File Deletes one file from an API spec by File Path.
- Delete a Workspace Deletes a workspace once Confirm is turned on.
- Delete a Workspace Update Removes an update post by its Update ID from a workspace.
- Delete an API Deletes an API definition from Postman.
- Delete an API Version Deletes the release that matches a Version ID from the version list of an API.
- Delete an Environment Deletes a named environment, the variable set of a workspace.
- Duplicate a Collection Copies a collection into a target Workspace. Use Suffix to tell the copy apart from the original.
- Fork a Collection Forks a collection into a target Workspace. Use Label to name the fork.
- Fork an Environment Makes a fork of an environment in a Workspace. Use Fork Name to title the fork.
- Generate a Collection from a Spec Builds a collection out of an API spec under a Name. Use Folder Strategy, Indent Character and Include Deprecated to shape it. It returns a Task Id and Url for following the run.
- Generate a Spec from a Collection Writes an API spec out of a collection from a Name, using Type and Format to set the spec style. Follow the run with its Task Id and Url.
- Get a Collection Downloads a whole collection: Info, Item, Auth, Event and Variable. Use Model to switch the response format and Access Key to read a shared collection.
- Get a Collection Folder Pulls one folder by Folder ID, returning its Name, Description and Owner. Turn on Populate to include what is inside.
- Get a Collection Merge Status Polls a merge task by Task ID and reports its Status.
- Get a Collection Request Looks up one request by Request ID, returning its Name, Owner and Last Revision. Turn on Populate for more detail.
- Get a Collection Response Fetches the saved example response behind a Response ID, with the Request it belongs to, plus its Name and Owner.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Better Stack and Postman integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Better Stack and Postman.
References
List of sources used to gather information about the Better Stack and Postman integration.
- Better Stack and Postman integration source code, module specs and credentials implementation.
- Our Better Stack and Postman integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Better Stack and Postman, 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.
- Better Stack integration information
- Postman integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Better Stack and Postman integration page documentation. Used sources, the role of AI, and how the team validates the result.