PagerDuty
Connect your PagerDuty account to enable CloudThinker agents to manage incidents, view on-call schedules, monitor services, and handle escalation policies.Supported Platforms
| Platform | Support |
|---|---|
| PagerDuty | All plans (Free, Professional, Business, Digital Operations) |
Setup
Open PagerDuty
Sign in to your PagerDuty account at app.pagerduty.com.
Generate a User API Key
Click your User Icon → My Profile, then scroll to User Settings → API Access and click Create API User Token:
- Description:
cloudthinker - Click Create Key
Use a User API Token, not a General Access REST API Key. User tokens scope access to what the user can see, providing better security boundaries.
Connection Details
| Field | Description | Example |
|---|---|---|
| PAGERDUTY_USER_API_KEY | PagerDuty User API Token | u+xxxxx... |
Required Permissions
Minimum (Read-Only)
A user with Observer or Responder role provides:- View incidents, services, and escalation policies
- View on-call schedules
- View teams and users
Recommended (Full Operations)
A user with Responder or Manager role provides:- All read permissions
- Acknowledge and resolve incidents
- Create incidents and status updates
- Manage on-call overrides
Agent Capabilities
Once connected, agents can:| Capability | Description |
|---|---|
| Incident Triage | List triggered and acknowledged incidents, identify patterns |
| On-Call Schedules | View who is currently on-call and upcoming rotations |
| Service Health | Monitor service status and active incident counts |
| Escalation Policies | View escalation chains and notification rules |
| Incident Actions | Acknowledge, resolve, and add notes to incidents |
| Schedule Management | View schedules and identify coverage gaps |
Example Prompts
Troubleshooting
Authentication failed
Authentication failed
- Verify the User API Token is correct
- Check the token has not been revoked
- Ensure you are using a User Token, not a REST API Key
Permission denied
Permission denied
- Verify the user has sufficient role permissions
- Check team-level access restrictions
- For write operations: ensure the user has Responder or Manager role
Missing services or incidents
Missing services or incidents
- Verify the user has access to the relevant teams
- Check team membership includes the services you want to monitor
- Ensure incidents are not filtered by team scope
Token revoked
Token revoked
- Navigate to My Profile → User Settings in PagerDuty
- Create a new API User Token
- Update the token in CloudThinker connection settings
Security Best Practices
- User token - Use a User API Token scoped to a dedicated user
- Minimal role - Assign Observer role for read-only use cases
- Dedicated user - Create a dedicated PagerDuty user for CloudThinker
- Token rotation - Rotate tokens every 90 days
- Team scoping - Limit user team membership to only the teams CloudThinker needs access to
Related
ServiceNow Connection
ITSM incident management
Datadog Connection
Observability and monitoring