01
Support knows before the customers do
A workflow triggered by a PagerDuty incident tells the inbox what is down, so the team answering "is it just me?" already knows the answer.
Integrations · Developer & monitoring
PagerDuty in the conversation.
Incident response — who is on call, what is broken, and who was told about it. Connect it once and your copilot works with incidents, services, schedules, on-calls and escalation policies without leaving the thread — and your workflows can act on it while the customer is still typing.
No credit card required · 7-day free trial
PagerDuty
Developer & monitoring
01 · COPILOT
Ask for it in plain language. It does the PagerDuty part.
Copilot rides inside the inbox. With PagerDuty connected it reads incidents, services, schedules, on-calls and escalation policies and acts on them from the same panel as the conversation — no second tab, no copying an order number across.
- Create a ruleset
- Create new service
- Create user object
- Delete addon by id
- Create incident record
- Create an incident type
What a specific connection exposes is decided by PagerDuty, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
02 · WORKFLOWS
Read PagerDuty from inside a workflow.
PagerDuty is a place a workflow looks things up rather than one that starts it. Trigger on a conversation, a schedule or another app's event, then use an AI Agent step to work in PagerDuty and hand the answer to the steps that follow — a message, a CRM update, an escalation.
If PagerDuty does publish events to your workspace, they appear in the trigger picker the moment the connection is made.
03 · THE AI AGENT STEP
One step that decides which PagerDuty tools to call.
A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.
You declare the output
The rows you name become the variables downstream steps read, so a branch can test what PagerDuty said.
You cap the effort
A step budget and a model tier per node — the loop stops where you told it to.
Only what you switched on
The loop can call the PagerDuty tools you left enabled and nothing else.
What teams do with it
Two ways PagerDuty earns its connection.
02
Reach the person actually on call
When a conversation turns into an outage, the copilot reads who is on call right now rather than @-ing a channel and hoping.
Setup
Connect PagerDuty in about a minute.
- 1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
- 2
Find PagerDuty in Browse
The catalogue runs to hundreds of apps and is searchable. Connect PagerDuty from its card.
- 3
Authorize with your own PagerDuty account
You sign in on PagerDuty's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
- 4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.
PagerDuty questions.
How do I connect PagerDuty to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for PagerDuty. Connecting it opens PagerDuty's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in PagerDuty?
Work of this kind: create a ruleset; create new service; create user object; delete addon by id; create incident record; create an incident type. The exact list depends on what your PagerDuty account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which PagerDuty tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only PagerDuty connection is a matter of leaving the writes off.
Can a workflow use PagerDuty without a trigger from it?
Yes. PagerDuty is read from inside a workflow rather than starting one: a workflow triggered by a conversation, a schedule or another app's event uses an AI Agent step to work in PagerDuty and hand its answer to the steps that follow.
Who in my team can connect PagerDuty?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the PagerDuty account that authorized it, so a developer & monitoring connection is only ever as broad as the account behind it.
More developer & monitoring
Rarely just one app.
SentryError tracking — the place a bug is a stack trace with a count next to it.BenchBenchmarking tool.
BitbucketBitbucket is a Git-based code hosting and collaboration platform supporting private and public repositories, enabling teams to manage and review code through pull requests and integrations.
ContentfulContentful is a headless CMS allowing developers to create, manage, and distribute content across multiple channels and devices with an API-first approach.
CrowdinCrowdin is a localization management platform that streamlines the translation process, offering tools for collaboration, content centralization, and workflow automation.
DaytonaDaytona is a development environment management platform that provides cloud-based development workspaces with API access for automation.See it on your own inbox
Try the whole thing, today.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.