Silent API Schema Changes Can Corrupt n8n Workflows Without Triggering Errors
A workflow that pulled records from an external API kept running normally while its output quietly degraded after the provider made an unannounced change. A status field became null and a numeric count arrived as a string, yet the HTTP call still returned 200 and nothing failed. The author argues that API responses are untrusted input and should be validated for required fields, expected types, and known enum values before any downstream processing. The recommended approach stops execution on breaking changes, ignores harmless additions, pins API versions, and runs a daily contract check that logs raw responses for diagnosis.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in