For platforms whose partners build integrations
Integration PulseLet partners see their own broken integration - and reach them before their customers do.
Classify your integration support tickets and paste each integration's numbers. Your browser checks every failure class against what integrators can see today, splits error rates into 4xx, 5xx and 429 against each integration's own baseline, catches integrations that went silent, reads whose fault a spike is against your deploys and their releases, ranks the breaking ones by installs, ranks the visibility, request-ID and alerting rungs, and reads the gates. Then the visibility design, and the outreach.
The platform, and a short interview free
The ticket pile and the signals free
The audit and the signals free
What the page flags
The gates
Failure classes against today's surface
Every integration, breaking first
The rungs
Area by area
Your audit table free
The table the skill starts from - failure class against what an integrator can see today - with the surface that closes each gap.
Audit (Markdown)
The visibility design metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved pulses
How it works - and what is sourced
The audit follows the skill: each failure class in your ticket pile is diagnosable only with its own surface - a request log for synchronous errors, a delivery-attempt log (or replay) for webhooks that never arrived, a request log or a state-change alert for auth, rate-limit headers or the log for 429s, an event or request log for silent mismatches, a volume-drop signal for an integration that stopped calling. Failure counts alone never count: they say something is wrong and give no way to act. A request ID resolves only when it is on every response and searchable where the integrator looks.
Error rates are split into 4xx (theirs), 5xx (ours) and 429 (neither) and compared with each integration's own baseline: it is breaking when the rate reaches twice its baseline and at least five points above it, or when calls fall under a tenth of baseline. A break within two days after one of your deploys is yours, unless 4xx dominate and their own release came later. Breaking integrations are ranked by installs, never by error count. The rungs follow the skill's ranking, moved by webhooks, the ticket pile, how fast partners lose money, providers, bodies, deadline and effort.