PDF4me icon

PDF4me

Comprehensive PDF and document processing: generate barcodes, convert files, extract data, manipulate images, and automate workflows with the PDF4ME API

Actions80

Overview

The node provides a variety of PDF and image processing operations through the PDF4me service. Specifically, for the "Upload File To PDF4me" operation, it allows users to upload files to the PDF4me platform in different formats: as binary data from a previous node, as a base64 encoded string, or via a URL pointing to the file. This operation is useful when you want to send files to PDF4me for further processing or storage, leveraging PDF4me's cloud capabilities.

Common scenarios include:

  • Uploading a PDF or image file obtained earlier in an automation workflow for subsequent PDF manipulations.
  • Sending a document fetched from a URL directly to PDF4me without intermediate storage.
  • Providing raw file content as a base64 string for upload when the file is generated or transformed within the workflow.

Practical example:

  • You receive an invoice PDF from an email trigger node, extract its binary data, and upload it to PDF4me for OCR or conversion tasks.
  • You have a publicly accessible document URL and want to upload it to PDF4me for watermarking or compression.

Properties

Name Meaning
Input Data Type Choose how to provide the file to upload. Options: Binary Data (file from previous node), Base64 String (base64 encoded file content), URL (link to the file).
Input Binary Field Name of the binary property containing the file (used only if Input Data Type is Binary Data). Default is "data".
Base64 File Content Base64 encoded file content (used only if Input Data Type is Base64 String).
File URL URL to the file to upload (used only if Input Data Type is URL).
File Retention Hours Number of hours to keep the uploaded file available on PDF4me platform. Range: 1 to 24 hours.

Output

The output JSON contains information about the uploaded file as returned by PDF4me. Typically, this includes metadata such as file identifiers, URLs for accessing the uploaded file, and status information confirming successful upload.

If the node supports binary data output, it would represent the uploaded file or related processed files in binary form, but for this operation, the main output is JSON metadata about the uploaded file.

Dependencies

  • Requires an active connection to the PDF4me API service.
  • Needs appropriate API authentication credentials configured in n8n to authorize requests to PDF4me.
  • The node depends on the PDF4me SDK or API client bundled internally to perform the upload action.

Troubleshooting

  • File Not Found or Invalid Binary Property: If using binary data input, ensure the specified binary property name exists and contains valid file data.
  • Invalid Base64 Content: When providing base64 content, verify that the string is correctly encoded and complete.
  • URL Access Issues: For URL input, confirm the URL is publicly accessible and points directly to a downloadable file.
  • File Retention Hours Out of Range: The retention time must be between 1 and 24 hours; values outside this range may cause errors.
  • API Authentication Errors: Check that the API key or authentication token is correctly set up and has sufficient permissions.
  • Network or Service Unavailability: Temporary network issues or PDF4me service downtime can cause upload failures; retry after some time.

Links and References

Discussion