n8n 1.123.68: Backported Fix for Onfleet Trigger Content-Type Handling

This patch corrects how the Onfleet Trigger node interprets incoming content types, preventing failures in webhook-driven workflows. Because it's a backport to the 1.x line, it targets users who remain on the older stable branch - typically self-hosted or enterprise-stabilized deployments that require conservative upgrade strategies.

Operationally, the fix matters to any workflow that relies on Onfleet to trigger downstream automations: missed or malformed triggers can disrupt dispatch, notifications, and SLA-driven operations. Even a small content-type mismatch can cascade into missed deliveries, duplicated work, or manual reconciliation tasks that erode the value of automation in logistics and field services.

Recommended actions: teams using Onfleet integrations on n8n 1.x should apply this patch or upgrade to the latest compatible release, validate webhook delivery end-to-end in a staging environment, and add synthetic tests that assert trigger behavior under varied content-type headers. If you maintain multiple deployment tracks (e.g., stable vs. canary), consider backporting equivalent tests to your stable track so regressions are detected before reaching production.

From a governance perspective, this release underlines the trade-offs around staying on long-term branches versus moving to the latest releases. Establish a clear policy for backports and security/bug-fix adoption that balances stability with the operational risk of running older code, and ensure communication channels between platform maintainers and business stakeholders are explicit about the cost of delayed upgrades.