PagerDuty
Observability
Read incident context, on-call schedules, and deployment-linked change events. Write tools require approval by default.
Available connection methods
d5s may offer more than one governed way to reach the same service. Choose the method that matches the account and authorization flow your workspace is prepared to manage.
API token (EU)
Remote MCPUse a user or account REST API key for your PagerDuty EU account. Some user and team filters require a user key.
Access tokenAPI token (US)
Remote MCPUse a user or account REST API key for your PagerDuty US account. Some user and team filters require a user key.
Access tokenConnect in d5s
- Open Connectors in the workspace and find PagerDuty.
- Choose a connection method and complete its authorization flow.
- Activate the resulting workspace credential on the project or agent that needs it.
- Review operation policy where it is available. Otherwise use a read-only or narrowly permissioned external account before allowing external actions.
Follow Connect and manage a connector for the complete workflow.
Keep access bounded
A connection uses the permissions of the external account that authorized it. Prefer a dedicated account or the narrowest provider permissions that still support the job. Project activation and d5s operation policy narrow where and how the credential may be used when those controls are available. They cannot grant access the external account does not already have.