Which announced API deadlines hit this workflow?
Drop an n8n workflow export (JSON) or a Make blueprint (JSON) below. You get back every third-party API the workflow depends on, every announced shutdown date that applies to it, and the vendor's own recommended replacement.
The workflow file never leaves your browser. Parsing happens in this page's JavaScript — there is no upload, no server, no account, no copy kept. Open your browser's Network tab and check: the only requests this page makes are for its own fonts, its own deadline table, and Cloudflare's page-speed measurement. None of them carries your workflow. That is the whole reason we built it this way, because the workflow is your client's business logic, not ours.
Drop a workflow export here
or choose a file · or paste the JSON below
Paste JSON instead
Zapier is not supported — Zapier has no public export format to read. If your work is in Zapier, the deadlines on this site still apply to it; you just have to check each Zap by hand, and the paid tier covers Zapier accounts through the vendor changelogs rather than through an export.
This was one workflow, one moment in time
Your clients depend on OpenAI, Shopify, Meta, Slack, Google and a dozen others — each with its own changelog, each publishing new deadlines all the time. This page only knows the deadlines announced as of the date shown above. Watching all of it, per client, continuously, and sending you one digest per client is the paid job.
Honest fine print
This report is only as complete as the deadline table behind it, which is hand-maintained and lists its source for every entry — see coverage. Model ids are matched on the whole string, never by prefix, so gpt-4o and gpt-4.1 are correctly treated as not being shut down while gpt-4 is. Anything read from an expression evaluated at runtime rather than typed into the workflow cannot be seen by a static read — of this page or of any other tool. Best-effort, not a guarantee.