# PagerDuty AI agent for Slack & Microsoft Teams Viktor is an AI employee that connects to PagerDuty in one click via OAuth and helps you monitor application errors and incidents, running 31 PagerDuty actions for you like List Users, List Teams, and Get Incident. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in PagerDuty and reports back. Setup takes about two minutes. - Tool: PagerDuty - Category: Developer Tools - Connection: One-click OAuth - Actions available: 31 - Works from: Slack and Microsoft Teams - Page: https://viktor.com/integrations/pagerduty ## What can you ask Viktor to do in PagerDuty? - "Summarize the new errors in PagerDuty from the last 24 hours and flag any regressions." - "Check PagerDuty for the root cause of last night's incident and report back." - "Watch PagerDuty for a new critical alert and page me immediately." - "Post a summary of this week's PagerDuty incident count to #eng every Friday." ## What can Viktor do in PagerDuty? (31 actions) - **Update Incident** - Update an incident's status, title, urgency, priority, escalation policy, or assignments. Use List Incidents or Get Incident to find the incident ID. To acknowledge: set status to acknowledged. To resolve: set status to resolved. Use List Users to find user IDs for assignments and List Priorities for priority IDs. - **Update Escalation Policy** - Update an escalation policy's name, description, loop count, or escalation rules. By default, performs a read-then-merge: fetches the current policy and merges your changes before writing, so you only need to specify the fields you want to change. Set fullReplacement: true to replace all rules wholesale — use with caution as this is destructive. Use List Escalation Policies to find the policy ID. Each escalation rule targets one or more users or schedules: provide targets as an array of objects with id and type (userreference or schedulereference). - **Trigger Incident** - Deprecated — use Create Incident instead. Trigger an incident. - **Start Incident Workflow** - Start an automation workflow on an active incident. Use List Incident Workflows to discover available workflow IDs. Use List Incidents or Get Incident to find the incident ID. Requires Business+ plan — accounts without this plan will receive a 402 error. - **Resolve Incident** - Deprecated — use Update Incident instead. Resolve an incident. - **List Users** - List users in the PagerDuty account, searchable by name or email. Returns user IDs, names, emails, and roles. Optionally filter by team membership using team IDs from List Teams. - **List User ID Options** - Retrieves available options for the User ID field. - **List Teams** - List teams in the PagerDuty account, optionally filtered by name. Returns team IDs and names useful for filtering incidents, users, and services. - **List Status Pages** - List configured PagerDuty status pages. Use status page IDs with List Status Page Posts to retrieve posts on a specific page. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. - **List Status Page Posts** - List posts on a PagerDuty status page. Use List Status Pages to discover status page IDs. Set activeOnly: true to filter to currently active posts (client-side filter). Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. - **List Services** - List services, optionally filtered by team or searched by name. Returns service IDs, names, status, and htmlurl. Use List Teams to discover team IDs for filtering. - **List Service ID Options** - Retrieves available options for the Service ID field. - **List Schedules** - List on-call schedules in the PagerDuty account, optionally filtered by name. Returns schedule IDs and names useful for List On-Calls and Create Schedule Override. - **List Priorities** - List the priority levels configured for this PagerDuty account. Returns priority IDs and names (e.g. P1, P2, critical) useful for Create Incident and Update Incident. - **List On-Calls** - List on-call entries — who is on call right now or during a given time window. Filterable by schedule IDs or escalation policy IDs. Use List Schedules to discover schedule IDs and List Escalation Policies to discover policy IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set earliest: true to get one on-call entry per unique (schedule, escalation policy, escalation level) combination. - **List On-Call Schedule ID Options** - Retrieves available options for the On-Call Schedule ID field. - **List Log Entries** - List log entries (the audit trail of actions taken on an incident or across the account). When incidentId is provided, scopes results to that incident's log entries. Otherwise returns account-wide log entries. Use List Incidents or Get Incident to find incident IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set isOverview: true to get only the most recent action per incident. - **List Incidents** - List and filter incidents by status, urgency, service, or team. Default statuses are triggered and acknowledged (open incidents). Use List Services to discover service IDs and List Teams for team IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. - **List Incident Workflows** - List available incident automation workflows. Use workflow IDs with Start Incident Workflow to run automation on an active incident. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. - **List Incident Change Events** - List change events (deployments, config changes) correlated to an incident. Change events show what changed in your systems around the time the incident was triggered. Use List Incidents or Get Incident to find the incident ID. - **List Escalation Policy ID Options** - Retrieves available options for the Escalation Policy ID field. - **List Escalation Policies** - List escalation policies in the PagerDuty account. Supports both exact name match (name) and substring search (query), plus team filtering. Use policy IDs with Create Incident, Create Service, and Update Escalation Policy. - **Get Service Analytics** - Get incident volume and MTTR (mean time to resolve) metrics for one or more services over a time range. Use List Services to discover service IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. - **Get Incident** - Get full details for a single incident by ID, including its current status, urgency, assignments, and htmlurl. Use List Incidents to find the incident ID. - **Get Event Orchestration for Service** - Get the active event orchestration routing rules configured for a service. Event orchestration routes incoming events to the right responders based on conditions. Use List Services to discover service IDs. - **Find Oncall User** - Find the user on call for a specific schedule. - **Create Service** - Create a new PagerDuty service. A service represents a system or application that generates incidents. Use List Escalation Policies to find a valid escalation policy ID (required). Set autoResolveTimeout to 0 to disable auto-resolve. Set acknowledgementTimeout to 0 to disable re-triggering after acknowledgment. - **Create Schedule Override** - Override a schedule layer to assign a specific user for a time window. Use List Schedules to find a schedule ID and List Users to find the user ID. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Always include the UTC offset — do not assume UTC; using the wrong offset will place the override in the wrong time slot. - **Create Incident** - Trigger a new incident on a PagerDuty service. Use List Services to find a service ID and List Escalation Policies to find a policy ID. Use List Priorities to find priority IDs. Set incidentKey to a stable value derived from the alert source (e.g. a hash of title + service ID) to prevent duplicate incidents on retry — PagerDuty deduplicates open incidents with the same key on the same service. - **Add Note to Incident** - Add a text note to an incident. Notes are visible in the incident timeline and useful for documenting investigation steps, resolution details, or handoff notes. Use List Incidents or Get Incident to find the incident ID. - **Acknowledge Incident** - Deprecated — use Update Incident instead. Acknowledge an incident. ## How does Viktor work with PagerDuty? 1. Add Viktor to Slack or Microsoft Teams. 2. Connect PagerDuty with one-click OAuth - Viktor handles authentication. 3. Ask in plain English. Viktor runs the PagerDuty actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval. ## What is a PagerDuty AI agent? A PagerDuty AI agent is an AI that connects to your PagerDuty account and completes work in it - it doesn't just answer questions about PagerDuty, it takes the actions. Viktor is that agent: an AI employee that works in PagerDuty on your behalf and delivers the finished result in Slack or Microsoft Teams. Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right PagerDuty actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs. ### About PagerDuty Real-Time Operations and Incident Response ## Security and permissions - One-click OAuth - Viktor never sees your password, and you can revoke access at any time. - Review-first approvals: sensitive PagerDuty actions wait for your sign-off before they run. - Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models. - SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ## FAQ ### Does Viktor integrate with PagerDuty? Yes. PagerDuty is one of the 3,200+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in PagerDuty from Slack or Microsoft Teams - no workflow builder, no code. ### How do I connect PagerDuty to Viktor? Ask Viktor in Slack or Microsoft Teams to connect PagerDuty, then approve the one-click OAuth prompt. Viktor never sees your password, handles authentication itself, and starts working right away. Setup takes about two minutes, and you can revoke access at any time. ### What can Viktor do in PagerDuty? Viktor can run 31 PagerDuty actions, including List Users, List Teams, and Get Incident - and chain them with other tools in a single request. In practice that means Viktor helps you monitor application errors and incidents. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. ### Do I need to build workflows to automate PagerDuty? No. Viktor isn't a workflow builder - there are no triggers to map and no workflows to maintain. You ask for the outcome in plain English in Slack or Microsoft Teams, and Viktor decides which PagerDuty actions to take, runs them, and reports back. ### Is my PagerDuty data secure with Viktor? Yes. Viktor connects to PagerDuty in one click via OAuth, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ### How much does the PagerDuty integration cost? Nothing extra - every integration, including PagerDuty, is available on every plan. You can start free with up to $100 in credits, no credit card required; paid plans start at $50/month. ### Can Viktor use PagerDuty together with my other tools? Yes - that's the point. Viktor connects to 3,200+ tools and works across them in a single run: it can pull data from PagerDuty, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in Slack or Microsoft Teams. ## Viktor uses PagerDuty together with - [Slack](https://viktor.com/integrations/slack) - [Gmail](https://viktor.com/integrations/gmail) - [Google Sheets](https://viktor.com/integrations/google-sheets) - [HubSpot](https://viktor.com/integrations/hubspot) - [Notion](https://viktor.com/integrations/notion) - [Salesforce](https://viktor.com/integrations/salesforce) ## More Developer Tools integrations - [Pipedream Utils](https://viktor.com/integrations/pipedream-utils) - [Databricks (OAuth - Service Principal)](https://viktor.com/integrations/databricks-oauth-service-principal) - [Universal API](https://viktor.com/integrations/universal-api) - [ServiceNow](https://viktor.com/integrations/servicenow) - [Formatting](https://viktor.com/integrations/formatting) - [Helper Functions](https://viktor.com/integrations/helper-functions) - [Snipe-IT](https://viktor.com/integrations/snipe-it) - [Pipefy](https://viktor.com/integrations/pipefy) ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 3,200+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.