--- title: "Connect PagerDuty and Sorry - APIANT.ai" description: "When \"New Incidents\" fires in PagerDuty, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Create Note on Incident\" in PagerDuty." canonical: "https://apiant.ai/connect/pagerduty-to-sorry" --- # Connect PagerDuty and Sorry When **New Incidents** fires in [PagerDuty](https://apiant.ai/connections/pagerduty), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Create Note on Incident** in PagerDuty. Describe the whole flow and it is built, tested on every scenario and kept running. PagerDuty **2** triggers PagerDuty **26** actions Sorry **1** trigger Sorry **16** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want PagerDuty and Sorry to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What PagerDuty and Sorry can do together ### From PagerDuty to Sorry - When **New Incidents** in PagerDuty then **Update status page** in Sorry - When **List Maintenance Windows** in PagerDuty then **Add component** in Sorry ### From Sorry to PagerDuty - When **New notice** in Sorry then **Create Note on Incident** in PagerDuty - When **New notice** in Sorry then **Add Responders** in PagerDuty Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with PagerDuty and Sorry ## Triggers and actions 3 triggers · 42 actions - Trigger **List Maintenance Windows** Gets a list of maintenance windows. - Trigger **New Incidents** Polls for new incidents in PagerDuty. - Action **Add Responders** Request additional responders (a user or escalation policy) to help with an incident. - Action **Add Team Member** Add a user to a team with a given role. - Action **Create Incident** Creates an incident in PagerDuty. - Action **Create Note on Incident** Creates a note on a given incident. - Action **Delete or End a Maintenance Window** Deletes a maintenance window that hasn't started yet, or ends one that is ongoing. - Action **Get Escalation Policy** Retrieve a single escalation policy by its ID. - Action **Get Incident** Retrieve a single PagerDuty incident by id. - Action **Get Schedule** Retrieve a single on-call schedule by its ID. - Action **Get Service** Retrieve a single PagerDuty service by id. - Action **Get Team** Retrieve a single team by its ID. - Action **Get User Information** Gets a user's information based on provided ID. - Action **List Escalation Policies** List PagerDuty escalation policies. - Action **List Incident Notes** List all notes attached to an incident. - Action **List Incidents** List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range). - Action **List On-Calls** List current on-call entries — who is on call now, by escalation policy/schedule/user/time window. - Action **List Schedule Overrides** List overrides on a schedule within a required since/until time window. - Action **List Schedules** List PagerDuty on-call schedules. - Action **List Services** List PagerDuty services. - Action **List Teams** List all teams in the account. - Action **List Users** List PagerDuty users. - Action **Manage Incidents** Bulk acknowledge or resolve multiple incidents in a single call. - Action **Snooze Incident** Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires. - Action **Two-way sync add a maintenance window** Creates a maintenance window for use with two-way sync triggers. Does not update. Use only with two-way sync triggers. - Action **Two-way sync add or update an incident** Creates or updates an incident for use with two-way sync triggers. Use only with two-way sync triggers. - Action **Update Incident** Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident. - Action **Update Maintenance Window** Updates a maintenance window. - Trigger **New notice** Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page. - Action **Add component** Creates a new component on a Sorry status page, optionally nested under a parent component. - Action **Add notice** Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers. - Action **Add notice update** Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations. - Action **Add subscriber** Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices. - Action **Delete notice** Deletes a notice (incident, maintenance or general) from a Sorry status page. - Action **Delete subscriber** Permanently removes a subscriber from a status page. - Action **Get notice** Returns a single notice from a status page, including its type, state, subject, synopsis and link. - Action **Get status page** Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more. - Action **List components** Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state. - Action **List notices** Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date. - Action **List notice updates** Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content. - Action **List status pages** Returns all status pages in your Sorry account, optionally filtered by name or creation date. - Action **List subscribers** Returns the subscribers on a status page, optionally only those who receive notices for a specific component. - Action **Update component** Updates a component on a Sorry status page, such as its name, description, position or parent component. - Action **Update notice** Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance. - Action **Update status page** Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language. ## Each app on its own - [ **PagerDuty** PagerDuty is an incident management and on-call alerting platform.](https://apiant.ai/connections/pagerduty) - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) Reviews ## What our customers say ## More from PagerDuty - [ **PagerDuty to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pagerduty-to-salesforce) - [ **PagerDuty to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/pagerduty-to-stripe) - [ **PagerDuty to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/pagerduty-to-quickbooks-online) - [ **PagerDuty to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pagerduty-to-pipedrive) - [ **PagerDuty to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/pagerduty-to-trello) - [ **PagerDuty to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/pagerduty-to-zoom) ## More into Sorry - [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry) - [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry) - [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry) - [ **Google Sheets to Sorry** Google Sheets](https://apiant.ai/connect/google-sheets-to-sorry) - [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry) - [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry) Questions ## PagerDuty and Sorry, answered ### ### What can start an automation from PagerDuty? Any of PagerDuty's 2 triggers in the catalog, including New Incidents and List Maintenance Windows. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Sorry when something happens in PagerDuty? Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Sorry to PagerDuty? Yes. When something happens in Sorry, your agent can act in PagerDuty too. This page covers both directions: Sorry's triggers and PagerDuty's actions are listed here as well. ### ### Do I have to build a connector for PagerDuty or Sorry? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use PagerDuty and Sorry without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.