What is the main purpose of the PDF To PNG (CustomJS) node?
This utility node is designed to convert input PDF binary data streams directly into individual PNG images within an n8n workflow. It is essential for automating document transformation tasks.
What kind of input data does this node require?
The PDF To PNG node requires binary data that represents a PDF file. This data usually comes from a preceding file operation node or an Integrations source, and it outputs one item per generated PNG image.
Why is this specific component labeled as "CustomJS"?
The CustomJS label indicates that this node utilizes custom JavaScript libraries internally to handle the complex rendering and conversion process of the PDF document content, ensuring high-quality output within the n8n node environment.
How do I use the PDF To PNG node in a workflow?
This node typically follows an initial data trigger or another node that retrieves the PDF file (e.g., from cloud storage). It is never used as the starting trigger itself, but rather as an intermediate processing step in your workflow automation.
Can this node handle multi-page PDF files?
Yes, the node automatically processes every page of the input PDF. For a multi-page file, it will output a separate data item for each page, allowing downstream nodes or Integrations to handle the individual PNG files independently.