Better Stack and PagerDuty Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Better Stack and PagerDuty 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 PagerDuty

Detailed info you need to know about Better Stack and PagerDuty integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Better Stack

    • Developer Tools
    • 2 triggers
    • 59 searches
    • 77 actions

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

  • PagerDuty

    • Developer Tools
    • 2 triggers
    • 69 searches
    • 79 actions

    Incident management and on-call with services, schedules, escalation policies and incidents with webhook subscriptions.[6]

How to connect Better Stack to PagerDuty

Set up your Better Stack and PagerDuty integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Better Stack and PagerDuty work in WEXTL?

WEXTL exposes actions and triggers for Better Stack and PagerDuty 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 triggersPagerDuty 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.

PagerDuty modules

  • Add a User to a Team Puts a user on a team, optionally with a given Role.
  • Add an Escalation Policy to a Team Attaches an existing escalation policy to a team and links the two.
  • Add Notification Subscribers Signs up people or teams as Subscribers for the status updates on one incident. The response includes the Result for each subscriber.
  • Assign Tags Adds and removes tags on an escalation policy, incident, service, team or user in one call. Use Add Tags for new or existing tags and Remove Tags to detach tags the entity already has.
  • Cancel Responder Requests for an Incident Cancels responder requests on an incident for the chosen Responder Request Targets, made by the Requester.
  • Change the Impact of an Incident on a Business Service Sets whether an incident impacts a business service, through Relation (Impacted or Not Impacted). The output returns the Relation.
  • Convert the Event Rules of a Service into Event Orchestration Rules Converts event rules from a service into event orchestration rules. The output reports a Convert Status and where they were Converted To.
  • Create a Change Event Records a change in PagerDuty from a Summary and a Source. Use Timestamp to set when the change occurred (it defaults to now) and Custom Details to attach more information.
  • Create a Maintenance Window Stops the listed Services from creating incidents from a Start Time until an End Time, when they start creating incidents again.
  • Create a New Integration Creates an integration on a service from a Type or a Vendor. For email integrations, add Email Filters and choose Email Incident Creation to control how messages open incidents.
  • Create a Note on an Incident Posts a note on an incident. Output includes the Channel and Created At of the note.
  • Create a Responder Request for an Incident Asks users or escalation policies to respond to an incident, sending a Message from the Requester.
  • Create a Schedule Builds an on-call rotation in a Time Zone from one or more Schedule Layers. Give it a Name and Description, and allow Overflow to let shifts run past the end of the range.
  • Create a Service Adds a service that incidents attach to, tied to an Escalation Policy. Add Auto Resolve Timeout, Acknowledgement Timeout, Alert Grouping or Support Hours to shape how incidents behave.
  • Create a Status Update on an Incident Posts a Message as a status update on an incident. Fill Subject and HTML Message to send a custom HTML email update.
  • Create a Tag Makes a tag from a Label. Attach it to entities with Assign Tags.
  • Create a Team Makes a team in PagerDuty from a Name. Use Description to describe the team and set Default Role to Manager or None.
  • Create a User Adds a user from a Name and Email, with an optional Role, License ID, Job Title, Color and Time Zone for the profile.
  • Create a User Contact Method Gives a user a new way to be reached, such as an email address or phone number. Fill Type, Label and Address, then Country Code if it is a phone.
  • Create a User Handoff Notification Rule Warns a user before an on-call shift changes hands, through a chosen Contact Method Type. Add a Notify Advance in Minutes delay before the rule fires.
  • Create a User Notification Rule Adds a step to how a user is alerted for incidents of a given Urgency. Wait before it fires with Start Delay in Minutes and choose the channel with Contact Method Type.
  • Create a User Status Update Notification Rule Defines how a user receives incident status updates, through a Contact Method Type.
  • Create an Escalation Policy Creates an escalation policy from a Name and ordered Escalation Rules. Use Number of Loops to repeat the policy after the last rule.
  • Create an Event Rule on a Service Creates an event rule on a service that matches incoming events by Conditions and then runs its Actions. Use Position to set its index, Time Frame to restrict when it applies and Disabled to create it switched off.
  • Create an Incident Raises an incident on a Service, under a Title. Rank it with Urgency and Priority, route it by Escalation Policy, and add an Incident Key to avoid duplicates.
  • Create Notification Subscriptions Signs one user up for the Subscribables listed, with a Result returned per entry.
  • Create One or More Overrides Replaces who is on call during specific time ranges on a schedule. Each entry of Overrides names a user and its own start and end. Output lists the Status and Errors of every override.
  • Create Team Notification Subscriptions Subscribes a team to the Subscribables listed. The output gives a Result per subscription.
  • Delete a Note on an Incident Removes a single note attached to an incident in PagerDuty.
  • Delete a Schedule Removes an on-call schedule from PagerDuty, given its Schedule ID.
  • Delete a Service Deletes the whole service with this Service ID from your PagerDuty account.
  • Delete a Tag Deletes the tag label with this ID from the tag list of your PagerDuty account.
  • Delete a Team Removes a team. Use Reassignment Team to move its unresolved incidents to another team.
  • Delete a User Removes a person from PagerDuty by User ID.
  • Delete a User Contact Method Deletes one contact method of a user in PagerDuty, found with User ID and Contact Method ID.
  • Delete a User Handoff Notification Rule Removes a rule that warned a user ahead of on-call shift changes.
  • Delete a User Notification Rule Removes one alert step from the incident notifications of a user.
  • Delete a User Session Ends one login session of a user, found by its Type.
  • Delete a User Status Update Notification Rule Deletes the rule that sent a user incident status updates through one contact method.
  • Delete All User Sessions Signs a user out by ending every session they have, browser and API alike.
  • Delete an Escalation Policy Deletes an escalation policy from your PagerDuty account, using the policy ID.
  • Delete an Event Rule from a Service Deletes one event rule of a service in PagerDuty, picked by the service and rule IDs.
  • Delete an Override Deletes one override from an on-call schedule, found by Schedule ID.
  • Delete or End a Maintenance Window Ends a maintenance window that is running, or deletes a scheduled one that has not started yet.
  • Enable a Webhook Subscription Enables a webhook subscription. The output shows whether it is Active along with its Delivery Method and Events.
  • Get a Change Event Reads one change event with its Summary, Timestamp, Services and Integration.
  • Get a Log Entry Reads a single entry from the PagerDuty log. Use Time Zone to show its times in a chosen zone.
  • Get a Maintenance Window Loads a maintenance window and reports its Sequence Number, Start Time and End Time. Use Include to add more models.
  • Get a Schedule Retrieves a schedule with its Schedule Layers, restricted to the Since to Until range. Add Include Next Oncall For User to see the next shift of one person.
  • Get a Service Pulls up a service with its Name, Description, Auto Resolve Timeout and Acknowledgement Timeout.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Better Stack and PagerDuty integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Better Stack and PagerDuty on WEXTL®

Claim your 3-day trial to build Better Stack with PagerDuty integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Better Stack and PagerDuty.

How do I connect Better Stack and PagerDuty?

Connect your Better Stack and PagerDuty accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Better Stack and PagerDuty?

Example: when the "Watch Events" trigger in Better Stack fires, WEXTL can "Add a User to a Team" in PagerDuty. Better Stack has 2 triggers (including Watch Events and Watch New Incidents). PagerDuty has 148 actions (including Add a User to a Team, Add an Escalation Policy to a Team, and Add Notification Subscribers). Add filters and transforms between steps when you need them.[1]

Can Better Stack trigger actions in PagerDuty, and PagerDuty in Better Stack?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Better Stack and PagerDuty?

No. Better Stack-to-PagerDuty automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Better Stack integrate with PagerDuty in real time?

Yes. Trigger-based automations start the moment Better Stack (or PagerDuty) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Better Stack + PagerDuty integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Better Stack with PagerDuty?

You can build your Better Stack + PagerDuty automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Better Stack and PagerDuty integration.

  1. Better Stack and PagerDuty integration source code, module specs and credentials implementation.
  2. Our Better Stack and PagerDuty integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Better Stack and PagerDuty, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Better Stack integration information
  6. PagerDuty integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Better Stack and PagerDuty integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Better Stack and PagerDuty, or get started