Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Loading
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.
Free to start · No credit card · SOC 2 Type 1 · Works in Slack & Microsoft Teams
Messages you'd actually send. Paste one into Slack or Microsoft Teams, swap in your specifics, and Viktor takes it from there.
“Summarize the new errors in PagerDuty from the last 24 hours and flag any regressions.”
— you, in Slack or Teams
“Check PagerDuty for the root cause of last night's incident and report back.”
— you, in Slack or Teams
“Watch PagerDuty for a new critical alert and page me immediately.”
— you, in Slack or Teams
“Post a summary of this week's PagerDuty incident count to #eng every Friday.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right PagerDuty actions, runs the work, and reports back. No workflows to build.
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 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).
Deprecated — use Create Incident instead. Trigger an incident.
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.
Deprecated — use Update Incident instead. Resolve an incident.
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.
Retrieves available options for the User ID field.
List teams in the PagerDuty account, optionally filtered by name. Returns team IDs and names useful for filtering incidents, users, and services.
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 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, optionally filtered by team or searched by name. Returns service IDs, names, status, and htmlurl. Use List Teams to discover team IDs for filtering.
Retrieves available options for the Service ID field.
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 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-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.
Retrieves available options for the On-Call Schedule ID field.
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 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 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 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.
Retrieves available options for the Escalation Policy ID field.
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 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 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 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 the user on call for a specific schedule.
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.
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.
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 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.
Deprecated — use Update Incident instead. Acknowledge an incident.
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Message Viktor in Slack like you'd message a teammate. "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." Plain English, any tool.
Viktor opens PagerDuty, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
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.
Real-Time Operations and Incident Response
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.
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.
Ask for outcomes that span tools — Viktor pulls from PagerDuty, cross-references the rest of your stack, and delivers one finished result.
Viktor connects to 3,200+ tools and works across them in a single run.
