Integration
Connect Exist and PagerDuty
When New Attribute Value fires in Exist, your agent runs Create Note on Incident in PagerDuty, or New Incidents in PagerDuty to Get User Profile in Exist. 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 Exist and PagerDuty to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)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 Exist and PagerDuty can do together
From Exist to PagerDuty
When New Attribute Value in Exist
then Create Note on Incident in PagerDuty
From PagerDuty to Exist
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 Exist and PagerDuty
Triggers and actions 3 triggers · 37 actions
- New Attribute Value
Triggers when a new daily value is recorded for the chosen Exist attribute, such as steps or mood.
- Acquire Attributes
Takes ownership of one or more Exist attributes for this app so it can write their values, creating templated attributes the user doesn't have yet.
- Create Attributes
Creates one or more new attributes in the user's Exist account, from a template or as custom attributes, and returns which succeeded and which failed.
- Get Attribute Values
Returns the daily values recorded for one of the user's Exist attributes, newest first.
- Get Averages
Returns the most recent weekly average values for your Exist attributes, optionally filtered by group, attribute and date range, including historical averages.
- Get User Profile
Returns the authenticated Exist user's profile: name, avatar, timezone, local time and unit preferences.
- Increment Attribute Values
Adds amounts to the existing daily values of attributes your app owns in Exist, returning each attribute's new total.
- List Attributes
Returns the Exist user's attributes (without values), optionally filtered by group, name, or type.
- List Attributes with Values
Returns the user's Exist attributes together with their recent daily values.
- List Owned Attributes
Returns the user's attributes that your Exist client currently owns, without values. Can be filtered by group, attribute name, manual flag and more.
- Release Attributes
Releases your ownership of one or more Exist attributes so another service can provide their data, or they become inactive.
- Update Attribute Values
Saves daily total values for attributes you own in Exist, up to 35 at a time, replacing any value already stored for those days.
- List Maintenance Windows
Gets a list of maintenance windows.
- New Incidents
Polls for new incidents in PagerDuty.
- Add Responders
Request additional responders (a user or escalation policy) to help with an incident.
- Add Team Member
Add a user to a team with a given role.
- Create Incident
Creates an incident in PagerDuty.
- Create Note on Incident
Creates a note on a given incident.
- Delete or End a Maintenance Window
Deletes a maintenance window that hasn't started yet, or ends one that is ongoing.
- Get Escalation Policy
Retrieve a single escalation policy by its ID.
- Get Incident
Retrieve a single PagerDuty incident by id.
- Get Schedule
Retrieve a single on-call schedule by its ID.
- Get Service
Retrieve a single PagerDuty service by id.
- Get Team
Retrieve a single team by its ID.
- Get User Information
Gets a user's information based on provided ID.
- List Escalation Policies
List PagerDuty escalation policies.
- List Incident Notes
List all notes attached to an incident.
- List Incidents
List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range).
- List On-Calls
List current on-call entries — who is on call now, by escalation policy/schedule/user/time window.
- List Schedule Overrides
List overrides on a schedule within a required since/until time window.
- List Schedules
List PagerDuty on-call schedules.
- List Services
List PagerDuty services.
- List Teams
List all teams in the account.
- List Users
List PagerDuty users.
- Manage Incidents
Bulk acknowledge or resolve multiple incidents in a single call.
- Snooze Incident
Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.
- 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.
- 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.
- Update Incident
Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.
- Update Maintenance Window
Updates 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 Exist
Exist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Exist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Exist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Exist to Google SheetsGoogle Sheets
Exist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Exist to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PagerDuty
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.
JotForm to PagerDutyJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
Questions
Exist and PagerDuty, answered
What can start an automation from Exist?
Any of Exist's 1 trigger in the catalog, including New Attribute Value. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PagerDuty when something happens in Exist?
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 Exist?
Yes. When something happens in PagerDuty, your agent can act in Exist too. This page covers both directions: PagerDuty's triggers and Exist's actions are listed here as well.
Do I have to build a connector for Exist 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.
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.