Know before an API change breaks your workflows
Third-party APIs publish breaking changes and shutdown dates all the time — buried in changelogs nobody reads until something stops working. We read them for you, map them to the workflows you actually run, and warn you while there's still time to fix things calmly. Whether you run them for clients or for your own company.
Every date on that board can silently stop a production workflow
These deadlines are published by the vendors themselves, weeks or months ahead — the information is public, just scattered across changelogs nobody has time to follow. A workflow built once for a client keeps running on borrowed time until the date hits, then fails on its next run. If there's no error branch, the client notices before the agency does.
How it works
-
01
Tell us what your workflows depend on
Send an n8n workflow export or Make blueprint — or just a plain list of the APIs in play. One workspace per client if you're an agency, or one workspace for your own stack.
-
02
We map dependencies to announced changes
Every workspace gets a dependency map with the deadlines that actually apply to it — not a firehose of every vendor's changelog.
-
03
You get a weekly digest per client — under your brand
On Agency plans the digest is white-labeled, so you can forward it to your client as your own monitoring service.
How is this different from generic API watchers?
Generic watchers exist and some are good. But this work doesn't live in a GitHub repo — it lives in n8n, Make and Zapier. As of Aug 30, 2026, none of the tools below mention any of those platforms.
| API Sunset / DepWatch | Breakwatch | api/breaks | |
|---|---|---|---|
| Watches vendor changelogs | yes | yes | yes |
| Reads n8n / Make / Zapier workflows | no | no — scans GitHub repos | yes — that's the point |
| Maps changes to a specific workflow set | no | per repo, not per workflow | yes — one workspace each |
| White-label digest your client can read | no | no | yes — from $59/mo |
| Priced how agencies bill | per API | per repo | per client workspace |
Pricing
- 1 workspace — one client, or your own stack
- Dependency map + applicable deadlines
- Weekly digest + dated-change alerts
- 5 client workspaces
- Everything in Starter
- White-label digest — forward to clients under your brand
- 15 client workspaces
- Everything in Agency
- More than 15 clients? Talk to us
Annual billing: pay for 10 months, get 12. Onboarding is hands-on in the first weeks — your first briefing is prepared by a human who read your dependency map, not by a template.
Free: a one-time dependency report, right now
Drop an n8n workflow export or a Make blueprint into the free report page and get the answer in seconds: which third-party APIs that workflow depends on, which announced shutdown dates apply to it, and the vendor's own recommended replacement for each one.
The workflow file never leaves your browser. Parsing runs in the page's own JavaScript — no upload, no account, no server, no copy kept. That is deliberate: the workflow is your client's business logic, not ours.
Prefer a human to read it? Email the export to support@apibreaks.com and we'll send the report back — that path still exists, it's just slower than doing it yourself. Zapier has no public export format, so Zaps can't be read either way.
Honest fine print
Monitoring is best-effort, not a guarantee — no one can promise to catch every change every vendor makes. What we commit to: sourcing from official vendor changelogs and deprecation pages, publishing which vendors and sources we cover, and telling you the publication date of everything we report.