PagerDuty, without opening PagerDuty.
Who is paged, what is firing, and the status update posted without leaving the thread.
- Free to start
- No card
- Nothing irreversible without your yes
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own PagerDuty details, and Ray takes it from there.
@Ray who is on call for payments, and what is open right now?
@Ray post a status update on the checkout incident that we found the cause.
@Ray has this alert fired before, and what fixed it last time?
@Ray who is on call this weekend across all the schedules?
What Ray can and cannot do in PagerDuty
Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.
22 reads wired, 2 actions Ray does at once, and 1 action that waits for your yes.
Runs on its own
What Ray reads in PagerDuty
- Incidents, their alerts, notes, and log entries
- Who is on call now, and the schedules and escalation policies behind it
- Services, teams, and the people on them
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Add a note to an incident
- Update an incident, including acknowledging and resolving it
Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.
Asks first, every time
Always waits for your yes
- Post a status update on an incident
Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, 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.
- Change schedules, escalation policies, or services
- Create or delete webhooks, teams, and maintenance windows
- Delete a subscription or an alert grouping
Exactly what Ray will ask you to approve.
Not a category of permission. These are the PagerDuty actions that stop in the thread with the real content before they happen.
- Post a status update on PagerDuty incident
Ray does these at once
- Add a note to PagerDuty incident
- Update PagerDuty incident
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Post a status update on PagerDuty incident
Showing Id and Message, each carrying the exact content that will land.
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
It lands, with an Undo
Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.
Megan
@Ray the checkout bug is back. Take a look in PagerDuty, and tell Dana it is being looked at.
Update PagerDuty incident
- Done
- just now
Ray uses PagerDuty together with the rest of your tools.
One ask can read PagerDuty, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
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 and make the change, asking first before anything that can’t be taken back.
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.
- What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
- 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.
PagerDuty and Ray, answered
The questions teams ask before they connect PagerDuty. Every answer is how this integration is built rather than a promise about it.
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 nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.