--- title: "Connect Better Stack and PagerDuty - APIANT.ai" description: "When \"New Monitor Status Change\" fires in Better Stack, your agent runs \"Create Note on Incident\" in PagerDuty." canonical: "https://apiant.ai/connect/better-stack-to-pagerduty" --- # Connect Better Stack and PagerDuty When **New Monitor Status Change** fires in [Better Stack](https://apiant.ai/connections/better-stack), your agent runs **Create Note on Incident** in [PagerDuty](https://apiant.ai/connections/pagerduty), or **List Maintenance Windows** in PagerDuty to **Add Incident Comment** in Better Stack. Describe the whole flow and it is built, tested on every scenario and kept running. Better Stack **3** triggers Better Stack **13** actions PagerDuty **2** triggers PagerDuty **26** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Better Stack and PagerDuty 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) Better Stack watches uptime and Better Stack incidents, while PagerDuty holds the schedules, escalation policies and teams that decide who gets woken up. Joining them means a monitor going down in Better Stack can open a PagerDuty incident for whoever is on call, and PagerDuty incidents and maintenance windows can shape what Better Stack tracks. Example flows ## What Better Stack and PagerDuty can do together ### From Better Stack to PagerDuty - When **New Monitor Status Change** in Better Stack then **Create Note on Incident** in PagerDuty - When **New or Updated Incident** in Better Stack then **Create Incident** in PagerDuty ### From PagerDuty to Better Stack - When **List Maintenance Windows** in PagerDuty then **Add Incident Comment** in Better Stack - When **New Incidents** in PagerDuty then **Create Incident** in Better Stack 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 Better Stack and PagerDuty ## Triggers and actions 5 triggers · 39 actions - Trigger **New Monitor Status Change** Fires when a monitor's status changes (up/down). - Trigger **New or Updated Incident** Triggers when new incidents are created, or when existing incidents are updated. - Trigger **On-Call Contact Changed** Triggers when an on-call contact changes. - Action **Acknowledge Incident** Acknowledges an incident. - Action **Add Heartbeat** Create a new heartbeat check. - Action **Add Incident Comment** Adds a comment to an incident. - Action **Add Monitor** Create a new uptime monitor. - Action **Create Incident** Creates an incident that notifies the team. - Action **Delete Heartbeat** Remove a heartbeat check by id. - Action **Delete Monitor** Delete an uptime monitor by id. - Action **Find Incident** Finds an Incident. - Action **Find On-Call Contact** Finds On-Call Contact. Supports time lookup. - Action **Get Monitor** Retrieve a single monitor by id. - Action **List Monitors** List all uptime monitors. - Action **Resolve Incident** Resolves an incident. - Action **Update Monitor** Update an existing monitor's settings. - 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. ## Each app on its own - [ **Better Stack** Better Stack is a tool to provide reliable monitoring with voice calls and beautiful on-call scheduling.](https://apiant.ai/connections/better-stack) - [ **PagerDuty** PagerDuty is an incident management and on-call alerting platform.](https://apiant.ai/connections/pagerduty) Reviews ## What our customers say ## More from Better Stack - [ **Better Stack to Telegram** Telegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.](https://apiant.ai/connect/better-stack-to-telegram) - [ **Better Stack to Vdocipher** Video hosting platform with DRM encryption, watermarking, and APIs to prevent piracy of streamed video...](https://apiant.ai/connect/better-stack-to-vdocipher) - [ **Better Stack to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/better-stack-to-hubspot) - [ **Better Stack to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/better-stack-to-slack) - [ **Better Stack to Google Sheets** Google Sheets](https://apiant.ai/connect/better-stack-to-google-sheets) - [ **Better Stack to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/better-stack-to-gmail) ## More into PagerDuty - [ **HubSpot to PagerDuty** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pagerduty) - [ **Slack to PagerDuty** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-pagerduty) - [ **Mailchimp to PagerDuty** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-pagerduty) - [ **JIRA to PagerDuty** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/jira-to-pagerduty) - [ **Freshdesk to PagerDuty** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/freshdesk-to-pagerduty) - [ **Klaviyo to PagerDuty** Klaviyo is a marketing automation platform for email and SMS.](https://apiant.ai/connect/klaviyo-to-pagerduty) Questions ## Better Stack and PagerDuty, answered ### ### Can the agent work out who to page before it creates the PagerDuty incident? Yes. It can use List On-Calls in PagerDuty to see who is on call for an escalation policy or schedule, then create the incident and add responders accordingly. The same lookup can feed a comment back onto the Better Stack incident. ### ### What happens when an incident is updated on one side? Better Stack's New or Updated Incident trigger can add a note to the matching PagerDuty incident, and PagerDuty's New Incidents trigger can create or resolve an incident in Better Stack. The agent tests every scenario, including updates that arrive after the incident is already open. ### ### What can start an automation from Better Stack? Any of Better Stack's 3 triggers in the catalog, including New Monitor Status Change, New or Updated Incident and On-Call Contact Changed. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in PagerDuty when something happens in Better Stack? Any of PagerDuty's 26 actions, including Add Team Member, Create Note on Incident, List On-Calls and Create Incident. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from PagerDuty to Better Stack? Yes. When something happens in PagerDuty, your agent can act in Better Stack too. This page covers both directions: PagerDuty's triggers and Better Stack's actions are listed here as well. ### ### Do I have to build a connector for Better Stack or PagerDuty? 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 Better Stack and PagerDuty 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.