n8n 2.23.4 is out, and it's a small but important patch. The automation tool now properly parses PDFs in its Data Loader node, thanks to a polyfill for the DOMMatrix API. This fix nips a compatibility issue that could crash workflows when extracting data from PDF files.
The changelog is short: a single bug fix. The team added a polyfill for DOMMatrix when parsing PDFs in the Data Loader. Without it, certain Node.js environments—especially older versions or specific runtimes—would throw errors because the PDF library depends on DOMMatrix, which isn't always available.
This isn't a new feature. It's a rock thrown into a pothole. But for users relying on PDF data extraction, it's the difference between a seamless workflow and a frustrating failure.
Data Loader is a core component for ingesting structured data from documents. PDFs are ubiquitous in finance, legal, and business processes. If that node breaks, entire automations grind to a halt.
The fix is straightforward—a polyfill is a fallback that provides the missing functionality. But it's the kind of proactive maintenance that keeps n8n reliable. You don't notice it until you don't have a headache.
For now, run npm update n8n or upgrade via your package manager. It's a small update with outsize impact for anyone processing PDFs. That's the nature of good software engineering—boring, essential, and quietly effective.
Official Source: https://github.com/n8n-io/n8n/releases/tag/stable