What is the purpose of the Compress PDF (CustomJS) node in an n8n workflow?
This node is designed to reduce the file size of PDF documents by executing optimized CustomJS logic. It functions as a crucial processing node between input and output Integrations.
How does the Compress PDF node handle input files?
The node accepts PDF files, typically as binary data passed from a preceding node, applies the compression script, and outputs the resulting smaller PDF file, ready for subsequent nodes.
Can this component be used as the starting point for my automation?
No, the Compress PDF (CustomJS) node is a utility node for processing data. Workflows must start with a dedicated trigger, such as a Webhook or an application-specific trigger, before this compression node can run.
What typical Integrations follow the use of this compression node?
After compression, users commonly integrate this node with storage services (like S3 or Google Drive) or email services to share the compressed file. It connects various nodes to complete the workflow.
Why use a CustomJS node specifically for PDF compression?
Using CustomJS provides greater flexibility and control over compression settings and algorithms, allowing advanced users to tailor the compression ratio and quality exactly how they need it within the node environment.