VOICE → PAGERDUTY · SAFETY-FIRST

Make PagerDuty voiceable.

A spoken word never executes.

Operate PagerDuty by voice — safely. Every destructive action is gated behind a deliberate confirmation.

5 actions · 4 writes · 4 gated as destructive

Get early access

EXAMPLE COMMANDS

What you can say to PagerDuty.

Generated from the PagerDuty spec — these are the real utterances the parser is built to handle.

PER-ACTION SAFETY

Every write, classified.

Destructive actions are gated; reads run free. No destructive action is ever left unflagged.

ActionEndpointClassWhyBlast radius
listIncidentsGET /incidentsread-onlyread-only — safe to run without a gateNo side effect. Read-only.
createIncidentPOST /incidents⚠ destructiveirreversible/costly action: “page”Pages a real human on call.
acknowledgeIncidentPUT /incidents/{id}/acknowledge⚠ destructiveirreversible/costly action: “acknowledge”Changes incident state and silences re-pages to others.
resolveIncidentPUT /incidents/{id}/resolve⚠ destructiveirreversible/costly action: “resolve”Closes the incident and stops escalation.
createMaintenanceWindowPOST /maintenance_windows⚠ destructiveirreversible/costly action: “suspend”Suspends alerting — real pages may be silently dropped.

AUTH & SETUP

Connecting to PagerDuty.

PagerDuty authenticates with Bearer token. Voxy stores only a vault reference — your secret is never written inline in the config or sent to the browser.

SchemeBearer token
HeaderAuthorization: Bearer <token>
Where to get itCreate a token / API key in the API's dashboard, then store it in your vault.
How Voxy stores itAs a vault reference (keyring:voxy/pagerduty) — never the literal secret. The gate and execution run server-side; the secret never reaches the client.

FAQ

Questions about PagerDuty by voice.

How do I authenticate Voxy with PagerDuty?

PagerDuty uses Bearer token. You generate the credential in the PagerDuty dashboard and store it as a vault reference; Voxy never holds the literal secret and never sends it to the browser. The credential is attached server-side when a confirmed action runs.

What can I do in PagerDuty by voice?

This page exposes 5 PagerDuty actions generated from its OpenAPI spec: listIncidents, createIncident, acknowledgeIncident, resolveIncident, createMaintenanceWindow. For example, you can say things like “list incidents with statuses <statuses> and urgencies <urgencies>”.

Which PagerDuty actions need confirmation?

4 of the 5 actions are classified destructive or costly and are gated behind a deliberate click: createIncident, acknowledgeIncident, resolveIncident, createMaintenanceWindow. Voxy shows a read-back of exactly what it will do, and nothing runs until you click confirm.

Is operating PagerDuty by voice safe?

Yes — safety is the whole point. A spoken word never executes a destructive action. Every irreversible or costly PagerDuty call (like createIncident) requires an explicit on-screen confirmation, and destructive detection runs at 100% recall, so nothing dangerous is silently executed.

Do I need a PagerDuty API key to try the demo?

No. The demo on this page is parse-only: it understands your command, shows the parsed call and read-back, and stops at the gate. It never calls PagerDuty and needs no keys. A key is only required when you wire Voxy to your live PagerDuty account.

Does Voxy change my PagerDuty setup or require code?

No code and no changes to PagerDuty. Voxy reads the PagerDuty OpenAPI spec to generate the voice layer; you keep using PagerDuty exactly as before and add a safe voice/natural-language way to run these actions.

Give PagerDuty a voice.
Keep the safety.

Early access is rolling out across the Tier-1 APIs. Point Voxy at your spec and get a gated voice agent.

Request access