FOR n8n · MAKE · ZAPIER AGENCIES

Know before an API change breaks your clients' workflows

Third-party APIs publish breaking changes and shutdown dates all the time — buried in changelogs nobody reads until a client calls. We read them for you, map them to the workflows you run for each client, and warn you while there's still time to fix things calmly.

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

  1. 01

    Tell us what each client depends on

    Send an n8n workflow export or Make blueprint — or just a plain list of the APIs a client uses. One client = one workspace.

  2. 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.

  3. 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.


Privacy by design: we keep only the dependency list — API names, node types and the deadlines that apply. Raw workflow exports are discarded right after parsing, and hard-coded keys are scrubbed at ingest. Your clients' business logic never sits in our database.

How is this different from generic API watchers?

Generic watchers exist and some are good. But agency 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 client no per repo, not per client yes — one workspace per client
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

STARTER
$29 /month
  • 1 client workspace
  • Dependency map + applicable deadlines
  • Weekly digest + dated-change alerts
Start now
AGENCY PLUS
$99 /month
  • 15 client workspaces
  • Everything in Agency
  • More than 15 clients? Talk to us
Start now

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

Not ready to subscribe? Email a workflow export (n8n JSON or Make blueprint) to support@apibreaks.com and we'll send back a one-time report: which third-party APIs the workflow depends on, and which announced deadlines apply. Free, once per agency. The export is discarded after parsing, as above.

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.