Integration
Connect GitHub and PagerDuty
When New Branch fires in GitHub, your agent runs Create Note on Incident in PagerDuty, or New Incidents in PagerDuty to Add Labels to Issue in GitHub. 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 GitHub 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 GitHub and PagerDuty can do together
From GitHub to PagerDuty
When New Branch in GitHub
then Create Note on Incident in PagerDuty
When New Collaborator in GitHub
then Add Responders in PagerDuty
From PagerDuty to GitHub
When New Incidents in PagerDuty
then Add Labels to Issue in GitHub
When List Maintenance Windows in PagerDuty
then Create Issue in GitHub
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 GitHub and PagerDuty
Triggers and actions 17 triggers · 45 actions
Trigger
Issue ClosedTriggers when an issue in a repository is closed.
Trigger
New BranchTriggers when a new branch is created in a GitHub repository.
Trigger
New CollaboratorTriggers when a new collaborator is added to a GitHub repository.
Trigger
New CommitTriggers when a new commit is pushed to a GitHub repository's default branch.
Trigger
New Commit CommentTriggers when someone comments on a commit in a repository.
Trigger
New GistTriggers when you create a new gist on GitHub.
Trigger
New Global EventTriggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
Trigger
New IssueTriggers when a new issue is created in a repository.
Trigger
New LabelTriggers when a new label is added to a GitHub repository.
Trigger
New MilestoneTriggers when a new milestone is created in a repository.
Trigger
New Pull RequestTriggers when a new pull request is opened in a repository.
Trigger
New ReleaseTriggers when a new release is published in a GitHub repository.
Trigger
New Repo EventTriggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
Trigger
New RepositoryTriggers when a new public repository appears under a GitHub user or organization.
Trigger
New WatcherTriggers when someone starts watching a repository.
Action
Add Labels to IssueAdds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
Action
Check Organization MembershipChecks whether a GitHub user is a member of an organization and returns true or false.
Action
Create BranchCreates a new branch in a repository, starting from the commit you choose.
Action
Create CommentAdds a comment to an issue or pull request in a GitHub repository.
Action
Create GistCreates a new gist with one file on the connected GitHub account.
Action
Create IssueCreates a new issue in a GitHub repository.
Action
Create or Update FileCreates a new file in a repository, or replaces an existing file's contents, as a commit.
Action
Create Pull RequestOpens a pull request asking to merge one branch into another.
Action
Delete BranchDeletes a branch from a repository. Any open pull request from that branch is closed.
Action
Find BranchFinds a branch in a GitHub repository by name and returns its latest commit and protection status.
Action
Find IssueFinds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
Action
Find OrganizationFinds a GitHub organization by its login and returns its profile details.
Action
Find Pull RequestFinds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
Action
Find RepositoryReturns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
Action
Find UserFinds a GitHub user by username and returns their public profile.
Action
Get File ContentsReturns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
Action
Submit ReviewSubmits a review on a pull request: approve it, request changes, or leave a review comment.
Action
Update IssueUpdates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
Action
Update Pull RequestChanges a pull request's title, description, target branch, or open/closed state.
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 GitHub
GitHub to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
GitHub to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
GitHub to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
GitHub to Google SheetsGoogle Sheets
GitHub to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
GitHub 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.
JotForm to PagerDutyJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
Questions
GitHub and PagerDuty, answered
What can start an automation from GitHub?
Any of GitHub's 15 triggers in the catalog, including New Branch, New Collaborator, New Commit and New Commit Comment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PagerDuty when something happens in GitHub?
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 GitHub?
Yes. When something happens in PagerDuty, your agent can act in GitHub too. This page covers both directions: PagerDuty's triggers and GitHub's actions are listed here as well.
Do I have to build a connector for GitHub 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.