Integrations

The One Status integrates with the broader The One Stack ecosystem and with external tools via webhooks and the public API.

The One Stack Integrations

Hub (Authentication)

The One Status management console uses Hub SSO for authentication. Users sign in with their Hub account — no separate credentials required.

• Data flow: Hub validates the session and provides user identity (user ID, organization)
• What breaks if misconfigured: Users cannot log in to the management console. Ensure the Hub API URL is correctly configured in the Status deployment.

Outbound Webhooks → PSA

Trigger PSA ticket creation when a major incident is declared:

1. In your PSA, create an inbound email address or webhook endpoint that creates tickets
2. In The One Status, create a webhook pointing to that endpoint
3. Subscribe to incident.created (and optionally incident.resolved)
4. Use a middleware function to transform the Status webhook payload into the PSA's expected format

When a critical incident fires, a ticket is automatically created in your PSA, alerting your technicians without requiring manual action.

Outbound Webhooks → RMM

Send component status changes from The One Status to your RMM for alerting:

• Subscribe to component.status_changed events
• Route to an RMM webhook endpoint or alert channel

This creates a two-way health signal: RMM alerts trigger The One Status incidents, and The One Status component changes can update RMM dashboards.

Client Portal

Embed The One Status on your client portal using the public API or an iframe:

• Summary badge: Show overall status (operational, degraded, major_outage) on the portal dashboard
• Full page embed: Embed the full status page in an iframe within the portal
• Components list: Fetch /public/{subdomain}/components.json and render a custom component status table

See Embed Widget for code examples.

External Tool Integrations

UptimeRobot / Pingdom / Better Uptime

These external monitoring tools detect when a URL goes down. To connect them with The One Status:

Option 1 — Inbound webhook (recommended):

1. Create an API key in The One Status (Settings → Security → API Keys)
2. Use UptimeRobot's alert integrations to POST to the Status API when a monitor triggers:

   POST /api/status-pages/{pageId}/incidents
   Authorization: Bearer your-api-key

3. Automatically create an incident with the affected component and severity

Option 2 — The One Status as the only monitor: Configure automated monitoring directly in The One Status (per component URL) and skip the external monitor for components you track here.

Slack

See Webhooks & Alerting → Integrating with Slack.

Microsoft Teams

See Webhooks & Alerting → Integrating with Microsoft Teams.

PagerDuty / OpsGenie

Route incident.created webhooks to your on-call platform to trigger pages for critical incidents. Route incident.resolved to auto-resolve the PagerDuty/OpsGenie alert.

Zapier / Make (Integromat)

Use Zapier or Make as a middleware layer between The One Status webhooks and any other system:

1. Create a Webhook Catch trigger in Zapier/Make
2. Use that URL as the webhook endpoint in The One Status
3. Map fields from the Status payload to the target system's fields
4. Enable the Zap/scenario

This pattern works for: ServiceNow, ConnectWise Manage, Autotask, HubSpot, and any other platform with a Zapier/Make connector.

Data Flows Summary

Integration	Direction	Data
Hub	Inbound	User authentication and session
Outbound webhooks	Outbound	Incident/maintenance/component events as JSON POST
Public API	Outbound	Status page data (summary, components, incidents) — read-only
Management API + API key	Inbound	Create/update incidents programmatically

What Breaks If Misconfigured

Integration	Misconfiguration	Impact
Hub auth	Hub API URL wrong or Hub is down	Users cannot log in; subscribers still receive notifications, public page still works
Outbound webhook	Endpoint URL returns non-2xx	Delivery fails silently; check the webhook delivery log for failures
Outbound webhook	Secret rotated but endpoint not updated	Signature verification fails at the receiving end; deliveries succeed from Status's perspective but are rejected by the receiver
API key auth	Key revoked	Automated incident creation stops; existing incidents and public page unaffected
Custom domain DNS	CNAME misconfigured	Status page served on the default subdomain URL; custom domain returns DNS error
Custom domain SSL	DNS propagation delay	SSL cert provisioning delayed; page may show insecure during propagation
Component monitoring URL	URL inaccessible from Status infrastructure	All checks fail; component marked Major Outage; subscribers notified