PagerDuty, without opening PagerDuty.
Read-only on-call and incidents: who is paged, what is firing, what changed.
In your channel
Ask Ray for something in PagerDuty and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in PagerDuty
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in PagerDuty
- Retrieve oncall list
- Fetch incident list
- Retrieve incident by incident id
- Get alerts by incident id
- Get incident alert details
- Get incident log entries by id
- Retrieve notes for incident
- Retrieve past incidents
- Fetch related incidents by id
- Fetch related change events for incident
- Retrieve postmortem by id
- Get schedules
- Retrieve schedule by id
- Retrieve users by schedule id
- Fetch escalation polices list
- Get escalation policy by id
- Retrieve list of services
- Retrieve service by id
- Retrieve users list
- Retrieve user by id
- Retrieve team list
- Retrieve current user info
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Add a note to PagerDuty incident
- Post a status update on PagerDuty incident
- Update PagerDuty incident
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete account subscription by id
- Delete addon by id
- Delete alert grouping setting
How Ray works with PagerDuty
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect PagerDuty
One click, right where you asked. Ray posts a connect card, you authorise PagerDuty with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in PagerDuty, and tell Dana it is being looked at.
Add a note to PagerDuty incident
- Waiting on
- your approval
What does connecting PagerDuty to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect PagerDuty and it can do the PagerDuty part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own PagerDuty account, so Ray can only reach what that person can already reach, and the history in PagerDuty shows who actually asked.
Security and permissions
- You authorise PagerDuty on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect PagerDuty in a message, or uninstall Ray and every connection it held is revoked.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in PagerDuty.
Free to start, no credit card, and it asks before it acts.