--- title: "Connect Groove and PagerDuty - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Create Note on Incident\" in PagerDuty." canonical: "https://apiant.ai/connect/groove-to-pagerduty" --- # Connect Groove and PagerDuty When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Create Note on Incident** in [PagerDuty](https://apiant.ai/connections/pagerduty), or **New Incidents** in PagerDuty to **Add label to ticket** in Groove. Describe the whole flow and it is built, tested on every scenario and kept running. Groove **9** triggers Groove **15** 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 Groove 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) Example flows ## What Groove and PagerDuty can do together ### From Groove to PagerDuty - When **Customer Added** in Groove then **Create Note on Incident** in PagerDuty - When **Note Added** in Groove then **Add Responders** in PagerDuty ### From PagerDuty to Groove - When **New Incidents** in PagerDuty then **Add label to ticket** in Groove - When **List Maintenance Windows** in PagerDuty then **Add message** in Groove 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 Groove and PagerDuty ## Triggers and actions 11 triggers · 41 actions - Trigger **Agent Replied** Triggers when an agent replies to a ticket. - Trigger **Customer Added** Triggers when a customer is created. - Trigger **Customer Replied** Triggers when a customer replies to a ticket. - Trigger **Note Added** Triggers when a note is added to a ticket. - Trigger **Ticket Assigned** Triggers when a ticket is assigned. - Trigger **Ticket Closed** Triggers when a ticket is closed. - Trigger **Ticket Opened** Triggers when a ticket is opened. - Trigger **Ticket Started** Triggers when a new ticket is created. - Trigger **Ticket Tagged** Triggers when a ticket is tagged. - Action **Add label to ticket** Adds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket. - Action **Add message** Adds a new message (reply or private note) to an existing Groove ticket. - Action **Add Note** Adds a private note to a Groove ticket, visible only to agents. - Action **Change Assigned Agent** Assigns a Groove ticket to a different agent, identified by the agent's email address. - Action **Change Ticket Mailbox** Moves a ticket into a different mailbox. - Action **Change Ticket State** Changes the state of a Groove ticket (unread, opened, pending, closed or spam). - Action **Close Ticket** Closes a Groove ticket by setting its state to closed. - Action **Create New Ticket** Creates a new ticket in Groove from a customer or agent, with its first message. - Action **Get customer** Returns one Groove customer, looked up by email address, including their contact details and custom attributes. - Action **Get ticket** Returns a single Groove ticket by its ticket number. - Action **List agents** Returns the agents on your Groove account, optionally limited to one group. - Action **List mailboxes** Returns all mailboxes in the Groove account, with each mailbox's name and email address. - Action **List messages** Returns the messages and notes on a Groove ticket. - Action **Reopen Ticket** Reopens a Groove ticket by setting its state to opened. - Action **Update customer** Updates a customer's profile details, such as name, company, title and contact info, identified by their email address. - 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 - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **PagerDuty** PagerDuty is an incident management and on-call alerting platform.](https://apiant.ai/connections/pagerduty) Reviews ## What our customers say ## More from Groove - [ **Groove to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/groove-to-hubspot) - [ **Groove to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/groove-to-salesforce) - [ **Groove to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/groove-to-slack) - [ **Groove to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/groove-to-mailchimp) - [ **Groove to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/groove-to-stripe) - [ **Groove to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/groove-to-shopify) ## 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 ## Groove and PagerDuty, answered ### ### What can start an automation from Groove? Any of Groove's 9 triggers in the catalog, including Customer Added, Note Added, Agent Replied and Customer Replied. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in PagerDuty when something happens in Groove? Any of PagerDuty's 26 actions, including Create Incident, Create Note on Incident, Update Incident and Update Maintenance Window. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from PagerDuty to Groove? Yes. When something happens in PagerDuty, your agent can act in Groove too. This page covers both directions: PagerDuty's triggers and Groove's actions are listed here as well. ### ### Do I have to build a connector for Groove 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 Groove 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.