n8n n8n@2.36.7 released on 25-08-2026
n8n n8n@2.36.7 is out now. It tightens API request handling and fixes binary data behaviour, plus addresses cluster and proxy issues that affected licence renewal and OAuth2 token requests.
See the release on the n8n GitHub for the full notes and upgrade guidance before updating production instances.
What’s in this release
- API: Adapted the binary data endpoint to fix handling of binary assets (resolves observed upload/download issues).
- API: Decorator routes that accept a body now require a JSON Content-Type header (Content-Type: application/json) to prevent ambiguous or malformed requests.
- API: Removed the offset query parameter from the list workflow history endpoint — clients must stop relying on the offset parameter.
Upgrade notes
- Audit and update any API clients that use the list workflow history endpoint and remove any use of the offset query parameter; ensure requests to decorator routes include Content-Type: application/json and verify binary upload/download workflows after the change.
- If a rollback is necessary, revert to the prior release (n8n@2.36.6) and retest. In clustered deployments confirm licence auto-renewal behaviour after leader election and ensure proxy environment variables (HTTP_PROXY/HTTPS_PROXY/NO_PROXY) are set for every n8n process so OAuth2 token requests route correctly.
Share feedback or any issues you encounter on the n8n GitHub or community channels so integrators and operators can learn from your experience.
