Integration
Connect Diagrams.so and PagerDuty
When something happens in Diagrams.so or PagerDuty, your agent does the next thing in the other. Describe it 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 Diagrams.so 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)Diagrams.so turns text and infrastructure code into editable draw.io architecture diagrams, while PagerDuty holds your incidents, services, schedules and on-call rotations. Connecting them means a new diagram can raise a review incident with its Well-Architected findings attached, and an incident can pull up the diagram of the system it touches.
Example flows
What Diagrams.so and PagerDuty can do together
From Diagrams.so to PagerDuty
When New diagram in Diagrams.so
then List On-Calls in PagerDuty
From PagerDuty to Diagrams.so
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 Diagrams.so and PagerDuty
Triggers and actions 3 triggers · 40 actions
- New diagram
Fires when a new diagram is created in the account.
- Delete diagram
Delete a diagram.
- Edit diagram
Edit an existing diagram with a follow-up natural-language prompt.
- Export diagram
Export a diagram as draw.io XML or SVG.
- Find gallery templates
Search public community-shared architecture diagram templates in the gallery.
- Fix diagram warning
Apply an automated fix to a flagged Well-Architected warning on a diagram.
- Fork gallery template
Fork a public gallery template into the account's own diagrams.
- Get diagram
Retrieve a single diagram by id.
- Get diagram version
Retrieve a specific saved version of a diagram.
- Get diagram warnings
Retrieve the Well-Architected findings and score for a diagram.
- Import diagram
Import an existing draw.io file as a new diagram.
- List diagrams
List the diagrams in the account.
- List diagram versions
List the saved versions of a diagram.
- Relayout diagram
Start an automatic re-layout job on a diagram to clean up its arrangement.
- Update diagram
Update a diagram's metadata (name, visibility, tags, etc).
- 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 Diagrams.so
Diagrams.so to DocuSealDocuSeal is an open-source platform for electronic document signing and management, offering secure, legally...
Diagrams.so to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Diagrams.so to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Diagrams.so to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Diagrams.so to Google SheetsGoogle Sheets
Diagrams.so to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
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.
Klaviyo to PagerDutyKlaviyo is a marketing automation platform for email and SMS.
Questions
Diagrams.so and PagerDuty, answered
Can the agent attach diagram findings to a PagerDuty incident?
Yes. It can retrieve the Well-Architected findings and score for a diagram in Diagrams.so, then create an incident in PagerDuty and add the findings as a note on it. The agent tests every scenario before it runs on real diagrams.
What starts a run on the Diagrams.so side?
Diagrams.so reports new diagrams created in the account, and that is the event the agent watches. From there it can read the diagram, its warnings or its versions, and act in PagerDuty using the incident, service or on-call lookups you point it at.
What can start an automation from Diagrams.so?
Any of Diagrams.so's 1 trigger in the catalog, including New diagram. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PagerDuty when something happens in Diagrams.so?
Any of PagerDuty's 26 actions, including List On-Calls, Create Incident, Create Note on Incident and Update Incident. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PagerDuty to Diagrams.so?
Yes. When something happens in PagerDuty, your agent can act in Diagrams.so too. This page covers both directions: PagerDuty's triggers and Diagrams.so's actions are listed here as well.
Do I have to build a connector for Diagrams.so 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.