Connect PagerDuty integrations

Verified

Incident management and on-call — services, schedules, escalation policies, and incidents with webhook subscriptions — connect PagerDuty to WEXTL workflows and AI agents. Replace glue scripts around PagerDuty with visual workflows. Start from Watch Events, then run Get a Change Event or Get a Log Entry.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • PagerDuty
  • WEXTL
  • Better Stack
  • CircleCI
  • Contentful
  • Crowdin
  • Apify
  • AWS S3
  • Agenty
  • Bright Data
  • Currents
  • Browse AI
  • CloudConvert
  • Clerk
  • Cloudflare
  • AWS Cognito
  • Bunny.net
  • AWS Lambda
  • Azure Storage
  • AssemblyAI
  • Cortex

Supported triggers and actions for PagerDuty integration

Triggers can detect changes in PagerDuty and run actions that can create, search or modify data inside PagerDuty automatically[3] — exactly how you set them.

  • Watch Events Triggers when PagerDuty delivers a subscribed v3 webhook event.
  • Watch Incidents Triggers when an incident is created or updated after the cursor.
  • Get a Change Event Returns a single change event.
  • Get a Log Entry Returns a single log entry.
  • Get a Maintenance Window Returns a single maintenance window.
  • Get a Schedule Returns a single schedule.
  • Get a Service Returns a single service.
  • Get a Tag Returns a single tag.
  • Get a Team Returns a single team.
  • Get a User Returns a single user.
  • Get a User's Contact Method Returns a single user's contact method.
  • Get a User's Delegation Returns a single user's delegation.
  • Get a User's Handoff Notification Rule Returns a single user's handoff notification rule.
  • Get a User's Notification Rule Returns a single user's notification rule.
  • Get a User's Session Returns a single user's session.
  • Get a User's Status Update Notification Rule Returns a single user's status update notification rule.
  • Get a Vendor Returns a single vendor.
  • Get a Webhook Subscription Returns a single webhook subscription.
  • Get an Alert Returns a single alert.
  • Get an Escalation Policy Returns a single escalation policy.

How to integrate PagerDuty in automation workflow?

3 simple steps to make your PagerDuty connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.

How PagerDuty connects and integrates with WEXTL

Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever PagerDuty 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 PagerDuty supports.

Full PagerDuty API documentation

The following table illustrates what fields PagerDuty integration require during authorization flow inside our workflow builder[4].

Connect PagerDuty

  • API Key*Text

    ••••••••

Demonstration of PagerDuty connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
API KeyRequired
password

Create an API key in PagerDuty under Integrations → API Access Keys.

Connect PagerDuty to popular apps on WEXTL

Enter a name of the other app you want to sync with PagerDuty below. Click on selected app to explore integration options with PagerDuty. 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 PagerDuty integration

Select Watch Incidents trigger from PagerDuty - this will be a starting point in your automation. Whenever event happens in PagerDuty, workflow will start[7] from Watch Incidents node.

Search for Create a Note on an Incident, connect it as the next step of integration sequence. You can use filters between Watch Incidents and Create a Note on an Incident, so only important data pass from Watch Incidents to the next step. WEXTL gives you full control over the process of PagerDuty automation. All parts of workflow are visible on the canvas[4].

PagerDuty on WEXTL has 150 modules for creating developer tools automations. Explore PagerDuty documentation for more.

  • PagerDutyWatch Incidents
  • Better StackPerforms action

OR

  • Better StackTriggers
  • PagerDutyCreate a Note on an Incident
Demonstration of how visual PagerDuty automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating PagerDuty in your workflows.

What triggers does PagerDuty support?

PagerDuty has 2 triggers, including "Watch Events" and "Watch Incidents". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in PagerDuty?

Integration has 148 actions, including "Get a Change Event", "Get a Log Entry", and "Get a Maintenance Window", and more. Refer to our PagerDuty Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases[4].

Is the integration secure?

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

How does WEXTL integrate with PagerDuty?

The PagerDuty integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by PagerDuty official API and covered in documentation[3]. WEXTL handles the request signing and pagination for you.

Can I use webhooks with PagerDuty?

Absolutely. Where PagerDuty provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever PagerDuty or any other service sends event to webhook URL.

Why use WEXTL platform for PagerDuty automation?

WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for PagerDuty inside the workflow builder[4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with PagerDuty modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.

Automate PagerDuty on WEXTL®

Claim your 3-day trial to build PagerDuty integrations and access every WEXTL® feature.

Cancel anytime.

References

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

  1. PagerDuty integration source code, module specs and credentials implementation.
  2. Internal PagerDuty integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official PagerDuty vendor API documentation — 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. WEXTL® Apps Library
  6. WEXTL® PagerDuty App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain PagerDuty app documentation

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