n8n 2.48.0 Fixes Webhook Decoding, Log Redaction and Agent Bugs

n8n released version 2.48.0, published on November 10, 2026. The release contains only bug fixes, spread across the core runtime, the editor, the AI builder, and several integration nodes.

Among the changes, n8n now applies its redaction policy to log streaming, telemetry, and error reports. Webhook bodies are decoded in the charset they declare, and the Compression node keeps custom gzip file names. The OAuth JWKS stays available when a retired signing key cannot be read. Telegram agent channels now receive button clicks, and the Continue On Fail setting is honored for initial connection errors. The release also restores npm installation of n8n on all platforms and preserves API version headers regardless of case.

Why it matters

Several fixes affect how data leaves a workflow, including redaction in logs and error reports and correct webhook decoding. Teams that run automations in production benefit most from fixes to retry backoff and error handling. Operators who rely on Telegram agents or the RabbitMQ node also get reliability fixes.

What to do

Read the full release notes on GitHub before upgrading, especially if you process webhooks with non-UTF-8 content or use community package scans in CI. Test your critical workflows in a staging environment first. The release notes do not cover pricing or plan changes, so confirm those on the vendor’s site.