Introduction
Connect PagerDuty to Sana to manage incidents and find users on-call. Trigger, acknowledge, and resolve incidents, and find out who is currently on call. In summary, the connector has the following key characteristics:
Category: Engineering
Connector type: Real-time
Auth type: OAuth
Hosting type: Managed
Capabilities
This connector is able to do the following:
Capability |
Trigger incidents |
Acknowledge incidents |
Resolve incidents |
Find on-call users |
Tools
While the capabilities above describe what the connector can do at a high level, the underlying tools show exactly which operations the agent can use when you ask Sana about PagerDuty. In practice, the agent may call one or more tools to achieve a single capability.
Tool |
Acknowledge incident |
Find oncall user |
Resolve incident |
Trigger incident |
Scope and permissions
This connector uses OAuth. When you connect your account, you will need to sign into your account and grant the required permissions.
Set up instructions
Prerequisites:
Your Sana workspace admin has enabled this integration – if the workspace admin has disabled the integration it won't appear in the list of available integrations.
Step 1: Go to the integrations page in Sana
In Sana, click on ... More in the sidebar, then select Integrations
Step 2: Find PagerDuty in the list of available integrations
Scroll to the Available integrations section and locate PagerDuty.
Step 3: Connect the integration
Click the integration card and select "Connect just for me", this will open a pop-up powered by Pipedream. Follow the steps in the pop-up to complete the set-up.
Step 4: Sign in to PagerDuty and approve the requested scopes
You'll be redirected to PagerDuty to go through their OAuth flow. Sign in and approve the scopes Sana needs to operate the connector.
Step 5: Complete the set up
You've successfully connected your PagerDuty account. Click Continue to complete the setup and start using the connector.
Known limitations
Incident details: The connector can list incidents, but it cannot read detailed information about them.
Active incidents only: The connector can only list active incidents — past or resolved incidents are not retrievable.