APIs move. A path gets renamed, a method changes, a query parameter becomes required — and a test that was green last month fails for reasons that have nothing to do with bugs. Healing compares your flow’s request nodes against your OpenAPI/Swagger spec and proposes concrete fixes.
Two things worth knowing up front:
- It’s deterministic — a structural comparison, not a model guessing. The same flow and spec always produce the same findings.
- It’s fully offline and needs no AI key.
Healing a flow
- Open the flow and click Heal… in the toolbar (next to Run; disabled while the file has a parse error).
- Pick your spec — the modal lists the
.json/.yamlfiles in your workspace. Change spec lets you switch afterwards. - Read the report. The summary line says how many request nodes match the spec; each
finding names the node, what drifted, and the message — e.g.
/users/7doesn’t exist in the spec; closest match is/users/{id}. - Click Apply on a finding to rewrite that node’s config with the fix. The check runs again immediately, so the list updates as you go.
Nothing is modified until you click Apply, and only the node in that finding changes.
What it detects
| Finding | Meaning |
|---|---|
path-not-found | The URL’s path isn’t in the spec; the closest spec path is suggested. |
method-changed | The path exists, but with a different HTTP method. |
missing-required-query | The spec requires a query parameter the node doesn’t send. |
missing-required-header | The spec requires a header the node doesn’t send. |
deprecated | The operation is marked deprecated (informational — no fix to apply). |
Make it a habit
Keep the spec in the workspace (an openapi.yaml next to your flows) and heal when the
backend ships changes — it turns “why is CI red” archaeology into a one-minute checklist.
Agents can run the same check headlessly via the MCP server’s
detect_drift tool.