Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
PagerDuty Event Orchestrations (BYOK) icon

PagerDuty Event Orchestrations (BYOK)

Read your PagerDuty global and service event orchestrations, their router, global and service rule sets, cache variables and legacy rulesets with your own REST API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderPagerDuty Event Orchestrationsunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which PagerDuty event orchestrations do I have?
Tools called
list_orchestrations
Show PagerDuty event orchestration PORCH01
Tools called
get_orchestration
How does PagerDuty orchestration PORCH01 route events to services?
Tools called
get_router_rules
What global rules does PagerDuty orchestration PORCH01 apply?
Tools called
get_global_rules
What happens to unrouted events in PagerDuty orchestration PORCH01?
Tools called
get_unrouted_rules
What event rules does PagerDuty service PXYZ789 apply?
Tools called
get_service_orchestration

About

PagerDuty Event Orchestrations (BYOK) lets an AI assistant read your own PagerDuty Event Orchestrations data through the PagerDuty Event Orchestrations API with a key you supply (REST API key). Read-only: 10 tools (list_orchestrations, get_orchestration, get_router_rules, get_global_rules, get_unrouted_rules, get_service_orchestration, get_service_orchestration_status, list_orchestration_cache_variables, list_service_cache_variables, list_rulesets). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.pagerduty.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PagerDuty Event Orchestrations. PagerDuty Event Orchestrations and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the PagerDuty Event Orchestrations API (api.pagerduty.com) with a BYOK key; documentation: https://developer.pagerduty.com/api-reference/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List orchestrationsList global event orchestrations with name, description, team, number of routes and update time.
  • Get orchestrationGet one global event orchestration by id: name, description, team, route count and version.
  • Get router rulesGet the router rules of a global orchestration: rule sets with conditions and the service each rule routes to, plus the catch-all route.
  • Get global rulesGet the global rules of an orchestration (applied to every event): rule sets with conditions and actions such as severity, priority, suppress or…
  • Get unrouted rulesGet the unrouted rules of an orchestration (applied to events that match no router rule).
  • Get service orchestrationGet the service event orchestration of a service: rule sets with conditions and actions plus the catch-all.
  • Get service orchestration statusTell whether events of a service are evaluated by its service orchestration (true) or by its legacy ruleset (false).
  • List orchestration cache variablesList cache variables of a global orchestration (event data stored for use in rule conditions): name, source, regex and enabled state.
  • List service cache variablesList cache variables of a service orchestration: name, source, regex and enabled state.
  • List rulesetsList legacy rulesets (end-of-life event rules) with name, team and creation time.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-pagerduty-event-orchestrations.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Telnyx Numbers Config (BYOK)

Read the voice and messaging settings of your Telnyx phone numbers, number orders, block orders, bulk jobs and regulatory requirements with your own API key (read-only)

Live · MCP + REST10 tools

Telnyx Messaging Setup (BYOK)

Read your Telnyx messaging profile settings, toll-free verification status, short codes, alphanumeric sender IDs, auto-reply rules and number health with your own API key (read-only)

Live · MCP + REST10 tools

Telnyx 10DLC (BYOK)

Read your Telnyx 10DLC brand and campaign registrations, vetting status, number assignments and use-case costs with your own API key (read-only)

Live · MCP + REST9 tools

Telnyx Voice Config (BYOK)

Read your Telnyx SIP connections, TeXML and fax applications, call queues, FQDN and IP routing targets and channel limits with your own API key (read-only)

Live · MCP + REST10 tools

Cloudflare Threat Intel (BYOK)

Look up domains, IP addresses, URLs, WHOIS records and passive DNS in Cloudflare's threat intelligence, and list your indicator feeds, with your own API token

Live · MCP + REST9 tools

Cloudflare Tunnels (BYOK)

Read your Cloudflare Tunnels and Mesh nodes with their health, plus private network routes, hostname routes, virtual networks and subnets, with your own API token

Live · MCP + REST10 tools

Get PagerDuty Event Orchestrations (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own PagerDuty Event Orchestrations REST API key. Create one at https://support.pagerduty.com/main/docs/api-access-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to PagerDuty Event Orchestrations. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with PagerDuty Event Orchestrations.