Tracing the Blast Radius: The Workflow Dependency Graph
A new dependency graph in Workflows lets you ask what breaks before you change a shared credential or subworkflow, instead of finding out after.
If you've ever hesitated before editing a shared credential or a subworkflow because you weren't sure what else depended on it, Workflows now has a direct answer instead of a manual audit.
The graph
The editor includes a dependency panel backed by a graph endpoint that maps how your workflows relate to each other — which ones call a given subworkflow, which ones share a credential, which ones sit downstream of something you're about to touch.
The part that actually matters: impact
The useful move isn't just viewing the graph, it's querying it. A separate impact endpoint answers the specific question — "if I change this, what else is affected" — directly, rather than making you trace the lines yourself. Before you rotate a shared credential, rename a subworkflow, or change something several automations rely on, you can check exactly what's connected to it first.
Why this is worth having
"What breaks if I touch this" is a real source of hesitation for anyone who has accumulated more than a handful of interconnected automations — most tools leave you to answer it by memory or by manually clicking through every workflow that might be affected. Treating it as a queryable graph instead means you find out before you make the change, not after something downstream quietly stops working.
This pairs naturally with the reliability score we're also introducing — one tells you whether a workflow has been behaving, the other tells you who's depending on it before you touch it.