Native Statuspage connector with integration-statuspage graph module — pages, incidents, and components traverse live via API alongside PagerDuty, Datadog, and Slack for cited ops context.
Pages
Incidents
Components
Auto-provisions graph module: integration-statuspage — live API types install when you connect credentials.
Statuspage tracks customer-facing incidents — but engineering context lives in PagerDuty, Jenkins, and Slack elsewhere.
Teams prep comms updates by copying Statuspage links instead of joining deploy and CRM context in one cited summary.
Statuspage dashboards cannot multihop to deal blockers, on-call rotations, and cited exec briefs in one query.
integration-statuspage installs statuspage_*_live remote types — agents query live Statuspage API data.
Multihop queries link Statuspage incidents to Vercel deploys, HubSpot renewals, and Slack war-room threads.
Federate Statuspage with PagerDuty, Datadog, ServiceNow, and institutional memory.
Claude and Cursor access Statuspage through the same cited graph as product and revenue teams.
Join active Statuspage incidents with HubSpot renewal stage and support ticket volume — cited comms summary.
Correlate Statuspage component outages with Jenkins builds and Datadog alert timestamps.
Link Statuspage incidents to PagerDuty pages and Notion postmortems in one federated query.
Statuspage API key and optional page ID in Settings → Integrations.
1. Start a free trial at app.gyri.io · 2. Open Settings → Integrations · 3. Run your first federated query with cited answers.
Free trial — API credentials, auto graph module, cited federated answers.
