PagerDuty
PagerDuty is on the roadmap. Agents will read incidents, services and who is on call, gather the context around a page, and draft the update for you — while acknowledging, escalating and resolving incidents stay behind explicit human approval.
What your agents can do with PagerDuty
- Read incidents and on-call schedules
- Gather context around a page
- Acknowledge or escalate (with approval)
- Trigger workflows on new incidents
How to connect PagerDuty to Velaris
- 1
Get early access
Join the waitlist — we open access in waves.
- 2
Request PagerDuty
Vote for the PagerDuty connector in the community.
- 3
Get notified
We'll ping you the moment PagerDuty goes live.
Popular ways to use it
PagerDuty + Velaris — common questions
Can an agent acknowledge or resolve a PagerDuty incident?
Not on its own. Acknowledging, escalating and resolving are destructive-tier actions that need your explicit approval, and every one is logged against your account.
Can Velaris tell me who is on call right now?
Yes — reading schedules, escalation policies and current on-call is a plain read, so an agent answers it immediately with no approval step.
Can an agent write the incident timeline for a postmortem?
Yes — it can pull the incident's notes, log entries and linked alerts, then draft a timeline for you to edit before it goes anywhere.