Platform · Module
Connector Health Center
A health score for every connection, and agents that stop acting on stale data
Connector Health Center scores every connection from 0 to 100, applies freshness targets and explains degraded modes. Agents call a kernel health check before acting, and autonomy is restricted when data is stale.
Make reliability visible
Integrations fail quietly. A token expires, a webhook stops, a schema changes, and an agent keeps acting on yesterday's data. Connector Health Center exists so that never goes unnoticed.
The score
Each connection is measured on freshness, completeness, 24-hour error rate, auth health, webhook timeliness and reconciliation quality. The Health Score is a fixed formula:
30·Freshness + 20·Completeness + 20·(1 − ErrorRate) + 15·AuthHealth + 10·WebhookTimeliness + 5·ReconciliationQuality
Bands are Healthy at 85 or above, Degraded from 60 to 84, and Unhealthy below 60 or when auth has expired. Freshness targets have defaults per object family (messaging, CRM, ads, SEO, billing) and can be tuned per plan.
Agents check before acting
A kernel helper lets every agent ask for a connection's health before acting. The check is recorded in the trace, and the Action Bus gates agent Actions that depend on connector data according to the band. In the UI and in Copilot answers, degraded data carries banners and staleness labels.
Screens
The tenant screen, planned for Wave 1, lists every connection with score, freshness, last error, auth expiry, a re-auth button and a plain-language degraded-mode explanation.
Planned for Wave 2: an agency view of health across sub-accounts with bulk re-auth reminders; a One3 internal view of provider-wide incidents, the schema-drift quarantine queue and dead-letter redrive; status-page integration that shows provider incidents as "third-party degraded"; health history and target attainment reports; and drift alerts for schema changes and volume anomalies.
Predictive auth-expiry and rate-limit alerts are planned for Wave 3, and provider dependency targets in enterprise contracts for Wave 4.
Features
What Connector Health Center includes
Health metrics
Freshness, completeness, error rate, auth health, webhook timeliness and reconciliation quality per connection. W1.
Health Score 0–100
A published weighted formula. W1.
Health bands
Healthy 85+, Degraded 60–84, Unhealthy below 60 or auth expired. W1.
Kernel helper for agents
Agents check health before acting; check recorded in the trace and enforced by the Action Bus. W1.
Tenant health screen
Score, freshness, last error, auth expiry, re-auth and degraded explanation. W1.
Freshness defaults
Per object family and tunable per plan. W1.
Staleness labels
Degraded banners in the UI and Copilot answers. W1.
Agency health view
Health across sub-accounts with bulk re-auth reminders. W2.
Status-page integration
Provider incidents shown as third-party degraded. W2.
History and drift alerts
Target attainment reports; alerts on schema changes and volume anomalies. W2.
Predictive alerts
Auth expiry and rate-limit exhaustion predicted in advance. W3.
Workflow
Token expiry on a client's ad account
- 1
Auth health drops and the score falls below 60.
- 2
The connection turns Unhealthy and the agency is notified.
- 3
The ads agent's next budget Action is gated by the health check.
- 4
The agency re-authenticates in one click.
- 5
Health recovers and the agent resumes.
AI
AI skills and Digital Employees
Degraded-mode explanations
Plain-language reasons and next steps; the score itself is a deterministic formula. W1.
Predictive expiry and rate-limit alerts
Flags problems before they happen. W3.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
How is the health score calculated?
It is a published weighted formula across freshness, completeness, error rate, auth health, webhook timeliness and reconciliation quality.
What do agents do when a connection is degraded?
They check health before acting, and the Action Bus restricts their Actions on that connector's data until health recovers.
Can agencies see all client connections?
An agency view across sub-accounts with bulk re-auth reminders is planned for Wave 2.
See Connector Health Center in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.