PagerDuty integration

Monitoring & Observability · 4 actions · OAuth auth

Incident management and on-call scheduling platform

Put PagerDuty to work View PagerDuty integration docs

Overview

The ModuleX PagerDuty integration lets a ModuleX agent operate PagerDuty on your behalf — working across incidents and oncall users — directly from a plain-English request, using your organization's own PagerDuty credentials. No pre-built workflow is required: the agent picks the right PagerDuty action for the task.

PagerDuty is a monitoring & observability platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right PagerDuty action — or, when you want a repeatable process, the composer assembles a PagerDuty workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive PagerDuty in plain English

Type what you want. A ModuleX agent picks the right PagerDuty action — or chains several — and runs it. No workflow to build.

Resolve a triggered or acknowledged incident in PagerDuty
resolves toresolve_incident
Show me the oncall users that match what I describe
resolves tofind_oncall_user

Use cases

What you can automate with PagerDuty

Resolve an incident as soon as it's handledresolve_incident
Find the oncall users that match what you describefind_oncall_user
Trigger a new incident on a PagerDuty servicetrigger_incident
Acknowledge a triggered incident in PagerDutyacknowledge_incident

At a glance

PagerDuty integration at a glance

VendorPagerDuty

CategoryMonitoring & Observability

Actions available4

AuthenticationOAuth

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 4 PagerDuty actions

Incidents3

trigger_incident

Trigger a new incident on a PagerDuty service

acknowledge_incident

Acknowledge a triggered incident in PagerDuty

resolve_incident

Resolve a triggered or acknowledged incident in PagerDuty

Oncall Users1

find_oncall_user

Find the user on call for a specific PagerDuty schedule

See full parameters and response schemas in the PagerDuty integration docs

Two ways

Two ways to use PagerDuty in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right PagerDuty action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires PagerDuty into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting PagerDuty

OAuthPagerDuty uses OAuth. You connect your PagerDuty account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Step-by-step setup in the PagerDuty docs

Pairs well with PagerDuty

Agents often chain PagerDuty with these — connect them once and the agent can use all of them in a single task.

incident.io46 actions

FAQ

PagerDuty + ModuleX FAQ

A ModuleX agent can run any of PagerDuty's 4 actions — across incidents and oncall users — from a plain-English request, using your organization's own PagerDuty credentials.

No. The agent selects the right PagerDuty action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through OAuth — you connect your PagerDuty account once and ModuleX stores the token encrypted, scoped to your organization.

4, spanning incidents and oncall users.

PagerDuty runs on your own credentials, so any PagerDuty usage is billed by PagerDuty directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put PagerDuty to work in ModuleX.

Connect PagerDuty once with your own credentials and let your agent run all 4 actions on demand.

Put PagerDuty to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →