I’m currently developing a workflow that extracts data from a .docx file. Previously, I was using Mammoth to convert the .docx file into HTML, and it worked well—I was able to successfully extract all the content from the file.
However, after updating n8n to version 2.0.3, I configured Mammoth as an environment dependency when running n8n. While it seems that Mammoth is now available within the workflow, the code that previously worked for extracting HTML from the .docx file no longer behaves as expected. Instead, it returns an error similar to the one shown in the image.
Has anyone encountered a similar issue after updating n8n? I would really appreciate any guidance or suggestions on how to resolve this.
@jeimuzu18 Thank you so much! I have tried all your approaches but the Docx Extractor and the Convert File to Json node return the errors shown in the images. I have also tried your recommendations to change my code when using mammoth but they still return the same error. I think the main problem here is likely the Docx file format (i tried different .docx files but nothing changed)