Rootly

Manage incidents with Rootly

Category: Developer Tools
Primary Subcategory: Observability, Monitoring & Incident Response

Integration details

Description

Connect ChatGPT and Codex to Rootly to investigate incidents, summarize alerts and timelines, review on-call schedules and escalation paths, and manage incident follow-up work.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Developer Tools
Primary Subcategory: Observability, Monitoring & Incident Response
Secondary Subcategories: None listed
Brand: Rootly
Access: Account required
First tracked: 2026-09-04
Tool count: 253
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Observability, Monitoring & Incident Response

View Category

Listed in alphabetical order

Primary Subcategory

BirdieComing soonGet notified

ConnhexComing soonGet notified

Datadog (Preview)Coming soonGet notified

elmah.io MCPComing soonGet notified

HOME AI NodeComing soonGet notified

RootlyComing soonGet notified

Tools

253 tools agents can invoke

Attach alerts to an incident from provided data
Check if any at-risk responders (based on On-Call Health analysis) are scheduled for on-call. Integrates with On-Call Health (oncallhealth.ai) to identify responders with elevated workload health risk and checks if they are scheduled during the specified period. Optionally recommends safe replacement responders. Privacy: This tool surfaces identifiable employee workload health data from On-Call Health. It is an opt-in feature — an administrator must explicitly configure the ONCALLHEALTH_API_KEY environment variable to enable it. On-Call Health displays a visible indicator on each responder's profile page showing their health score and risk level, ensuring employees are aware that workload analytics are collected and visible to their organization. Requires ONCALLHEALTH_API_KEY environment variable.
Check if specific users are scheduled for on-call in a date range. Use this to verify if at-risk users (from On-Call Health) are scheduled, or to check availability before assigning new shifts. Returns scheduled users with their shifts and total hours, plus users who are not scheduled.
Collect a bounded working set of incidents across multiple pages for audits and analysis. Use this instead of list_incidents when you want a compact batch of incidents in one tool call, while keeping payload size under control. Argument caps: max_results <= 100, batch_size between 10 and 100. Values outside those bounds are clamped and reported, not rejected.
Creates a new alert from provided data
Creates a new alert event
Creates a new alert group. **Note**: For enhanced functionality and future compatibility, consider using the advanced alert grouping with `conditions` field instead of the legacy `group_by_alert_title`, `group_by_alert_urgency`, and `attributes` fields.
Creates a new alert route from provided data. **Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this feature, please contact Rootly customer support.** ## Asynchronous Rule Creation For organizations with large numbers of routing rules, Rootly supports asynchronous rule processing to improve performance. When enabled, rule creation happens in the background. **Important**: When async processing is enabled, the rules list in the API response will not be up-to-date immediately after creation. You should refetch the alert route after a few minutes to get the updated rules. If you experience slow operations when managing alert routes with many rules, contact Rootly customer support to enable asynchronous rule processing for your organization.
Creates a new alert routing rule from provided data. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this endpoint. If you don't know whether you are an advanced user, please contact Rootly customer support.**
Creates a new alert urgency from provided data
Creates a new alert source from provided data
Creates a new catalog from provided data
Creates a new Catalog Entity from provided data
Creates a new cause from provided data
[DEPRECATED] Use form field endpoints instead. Creates a new custom field from provided data
Creates a new custom form from provided data
Creates a new dashboard from provided data
Creates a new environment from provided data
Creates a new escalation level from provided data
Creates a new escalation level from provided data
Creates a new escalation path from provided data
Creates a new escalation policy from provided data
Creates a new form_field from provided data
Creates a new form_field_option from provided data
Creates a new form_set from provided data
Creates a new functionality from provided data
Creates a new heartbeat from provided data
Create an incident with a scoped set of fields for agent-driven workflows.
Creates a new action item from provided data
[DEPRECATED] Use form field endpoints instead. Creates a new incident custom field selection from provided data
Creates a new event from provided data
Creates a new incident form field selection from provided data
Creates a new incident_type from provided data
Creates a new Live Call Router from provided data
Creates a new On-Call Role from provided data
Creates a new on call shadow configuration from provided data
Recommend replacement responders for an override shift. Finds users in the same schedule rotation who are not already heavily loaded during the period. Returns recommended replacements sorted by current load (lowest first), plus a ready-to-use override payload for the top recommendation.
Creates a new override shift from provided data. If any existing override shifts overlap with the specified time range, they will be automatically deleted and replaced by the new override. This endpoint is idempotent: re-sending an identical override (same user and same start/end time) returns the existing override with a 200 status and does not recreate it.
Creates a new playbook from provided data
Creates a new pulse from provided data
Creates a new retrospective process from provided data
Creates a new schedule from provided data
Creates a new schedule rotation from provided data
Creates a new schedule rotation active day from provided data
Creates a new schedule rotation user from provided data
Creates a new service from provided data
Creates a new severity from provided data
Creates a new status page from provided data
Creates a new template from provided data
Creates a new Sub-Status from provided data

Rootly FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Rootly alternatives on ChatGPT?

As of 2026-09-04, Rootly competes with Birdie, Connhex, Datadog (Preview), elmah.io MCP, HOME AI Node, Honeycomb, Is It Down? Availability Check, Resolve AI, SiteTriage, Threpoly, Watchgoose in ChatGPT Observability, Monitoring & Incident Response, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.