Actions8
Overview
The node integrates with CloudConvert, a versatile file conversion and processing service. It supports multiple operations including converting files between formats, merging multiple files into a single PDF, creating archives, generating thumbnails, adding watermarks, extracting metadata, optimizing files, and capturing website screenshots or PDFs.
Specifically for the Merge Files operation, the node merges multiple input files into a single PDF document. This is useful in scenarios such as combining several reports, invoices, or documents into one consolidated PDF for easier sharing or archiving.
Practical examples:
- Combining multiple scanned pages into a single PDF.
- Merging several contract documents into one file before sending to a client.
- Aggregating multiple image files into a PDF portfolio.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with CloudConvert API. Options: "OAuth2 (Recommended)" or "API Key". |
| Operation | The action to perform. For this summary, fixed to "Merge Files" which merges multiple files into a single PDF. |
| Output Format | The desired output format of the merged file. For merging, typically "pdf". This property dynamically loads available output formats based on the selected operation. |
| Binary Input Data | Whether the input files are provided as binary data within the workflow. If true, the node reads files from a specified binary property; if false, it uses text content and filename inputs. |
| Input File Content | Text content of the input file(s) when not using binary data. Required if Binary Input Data is false. |
| Input Filename | Filename (including extension) of the input file(s) when not using binary data. Required if Binary Input Data is false. |
| Binary Property | Name of the binary property containing the input file data when Binary Input Data is true. Defaults to "data". |
Output
The node outputs JSON data representing the result of the merge operation. Typically, this includes:
- A reference to the merged PDF file, usually as binary data attached to the output item under a binary property.
- Metadata about the merged file such as filename, size, and MIME type.
If binary data is output, it represents the actual merged PDF file ready for further use or download.
Dependencies
- Requires an active CloudConvert account and API access.
- Needs either OAuth2 authentication or an API key credential configured in n8n.
- Internet connectivity to communicate with CloudConvert's API endpoints.
- No additional external dependencies beyond the CloudConvert API.
Troubleshooting
Common Issues:
- Invalid or missing authentication credentials will cause authorization errors.
- Incorrect input file data or missing binary properties can lead to failures in uploading files.
- Unsupported output formats for the merge operation may cause errors.
- Network issues or API rate limits might interrupt the process.
Error Messages:
"Invalid operation merge": Indicates the operation parameter was not recognized; ensure "merge" is correctly set.- Errors related to file upload or conversion usually indicate problems with input data or format compatibility.
- Authentication errors suggest checking API keys or OAuth2 token validity.
Resolutions:
- Verify credentials and re-authenticate if necessary.
- Confirm that input files are correctly provided either as binary data or text content with filenames.
- Check the output format is supported for merging (usually PDF).
- Review CloudConvert API status and usage limits.