Integration
Connect CallMaker and PagerDuty
When Booking Created fires in CallMaker, your agent runs Create Note on Incident in PagerDuty, or New Incidents in PagerDuty to Create Customer Card in CallMaker. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want CallMaker and PagerDuty to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What CallMaker and PagerDuty can do together
From CallMaker to PagerDuty
When Booking Created in CallMaker
then Create Note on Incident in PagerDuty
When Number Change Created in CallMaker
then Add Responders in PagerDuty
From PagerDuty to CallMaker
When New Incidents in PagerDuty
then Create Customer Card in CallMaker
When List Maintenance Windows in PagerDuty
then Confirm Order by Order Id in CallMaker
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 CallMaker and PagerDuty
Triggers and actions 17 triggers · 36 actions
Trigger
Booking CancelledFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled bookings.
Trigger
Booking ConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed bookings.
Trigger
Booking CreatedTriggers when a new booking is created.
Trigger
Booking RestoredFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored bookings.
Trigger
Booking UnConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed bookings.
Trigger
Meeting AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (true) to act only on accomplished meetings.
Trigger
Meeting Not AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (false) to act only on meetings that did not take place.
Trigger
Meeting Not SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (false) to act only on unsuccessful meetings.
Trigger
Meeting SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (true) to act only on successful meetings.
Trigger
Number Change CreatedTriggers when a new number change (a processed customer card) is recorded; returns its ID.
Trigger
Order CancelledFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled orders.
Trigger
Order ConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed orders.
Trigger
Order CreatedTriggers when a new order is created.
Trigger
Order RestoredFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored orders.
Trigger
Order UnConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed orders.
Action
Confirm Order by Order IdConfirms an order and returns the updated order.
Action
Create Customer CardCreates a customer card in a Callmaker project and list, with the field values you supply.
Action
Edit Customer CardUpdates field values on an existing Callmaker customer card.
Action
Edit Order Status by Order IdChanges the status of an order.
Action
Find Booking by Booking IdReturns one Callmaker booking (meeting) by its booking ID, including its customer card, user, times and confirmation state.
Action
Find Descendants Workflows by Workflow IdReturns the IDs of all workflows beneath a workflow.
Action
Find Number by Number IdReturns a number (customer record) by its ID.
Action
Find Order by Order IdReturns an order by its ID.
Action
Find Resource by Resource IdReturns a resource by its ID.
Action
Find User by User IdReturns a user by their ID.
Trigger
List Maintenance WindowsGets a list of maintenance windows.
Trigger
New IncidentsPolls for new incidents in PagerDuty.
Action
Add RespondersRequest additional responders (a user or escalation policy) to help with an incident.
Action
Add Team MemberAdd a user to a team with a given role.
Action
Create IncidentCreates an incident in PagerDuty.
Action
Create Note on IncidentCreates a note on a given incident.
Action
Delete or End a Maintenance WindowDeletes a maintenance window that hasn't started yet, or ends one that is ongoing.
Action
Get Escalation PolicyRetrieve a single escalation policy by its ID.
Action
Get IncidentRetrieve a single PagerDuty incident by id.
Action
Get ScheduleRetrieve a single on-call schedule by its ID.
Action
Get ServiceRetrieve a single PagerDuty service by id.
Action
Get TeamRetrieve a single team by its ID.
Action
Get User InformationGets a user's information based on provided ID.
Action
List Escalation PoliciesList PagerDuty escalation policies.
Action
List Incident NotesList all notes attached to an incident.
Action
List IncidentsList PagerDuty incidents with filters (statuses, service_ids, urgencies, date range).
Action
List On-CallsList current on-call entries — who is on call now, by escalation policy/schedule/user/time window.
Action
List Schedule OverridesList overrides on a schedule within a required since/until time window.
Action
List SchedulesList PagerDuty on-call schedules.
Action
List ServicesList PagerDuty services.
Action
List TeamsList all teams in the account.
Action
List UsersList PagerDuty users.
Action
Manage IncidentsBulk acknowledge or resolve multiple incidents in a single call.
Action
Snooze IncidentSnooze 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 windowCreates 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 incidentCreates or updates an incident for use with two-way sync triggers. Use only with two-way sync triggers.
Action
Update IncidentUpdates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.
Action
Update Maintenance WindowUpdates a maintenance window.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from CallMaker
CallMaker to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallMaker to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallMaker to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallMaker to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallMaker to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallMaker to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PagerDuty
HubSpot to PagerDutyHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to PagerDutySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to PagerDutyMailchimp marketing automation and email platform.
JIRA to PagerDutyAtlassian JIRA Cloud — issue tracking and project management.
Freshdesk to PagerDutyFreshdesk is a cloud-based customer support and helpdesk platform.
Klaviyo to PagerDutyKlaviyo is a marketing automation platform for email and SMS.
Questions
CallMaker and PagerDuty, answered
What can start an automation from CallMaker?
Any of CallMaker's 15 triggers in the catalog, including Booking Created, Number Change Created, Order Created and Booking Confirmed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PagerDuty when something happens in CallMaker?
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 CallMaker?
Yes. When something happens in PagerDuty, your agent can act in CallMaker too. This page covers both directions: PagerDuty's triggers and CallMaker's actions are listed here as well.
Do I have to build a connector for CallMaker 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 CallMaker 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.