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

This node operation "Flip Image" allows users to flip an image either horizontally, vertically, or both. It supports multiple input methods for the image file, including binary data from a previous node, a base64 encoded string, or a direct URL to the image. The flipped image is then output as binary data with a customizable filename.

Common scenarios where this node is beneficial include:

  • Image preprocessing in automation workflows, such as preparing images for display or printing.
  • Adjusting image orientation in batch processing pipelines.
  • Flipping images dynamically based on user input or other workflow conditions.

Practical example:

  • A user receives product images from various sources and wants to standardize their orientation by flipping them vertically before uploading to a website.

Properties

Name Meaning
Input Data Type Choose how to provide the image file to flip: Binary Data (from previous node), Base64 String, or URL
Input Binary Field Name of the binary property containing the image file (used if Input Data Type is Binary Data)
Base64 Image Content Base64 encoded image content (used if Input Data Type is Base64 String)
Image URL URL to the image file to flip (used if Input Data Type is URL)
Output File Name Name for the output flipped image file (e.g., "flipped_image.jpg")
Orientation Type Orientation to flip the image: Horizontal, Vertical, or Horizontal and Vertical
Async Enable asynchronous processing (true/false)
Binary Data Output Name Custom name for the binary data in n8n output (default is "data")

Output

The node outputs the flipped image as binary data under the specified binary data output name (default "data"). The output includes the flipped image file with the chosen output filename.

  • json: Contains metadata or any additional information related to the processed image (not detailed in the source).
  • binary: Contains the flipped image file data, ready for use in subsequent nodes or export.

Dependencies

  • No external API keys or services are explicitly required for this operation.
  • The node relies on internal image processing capabilities bundled within the node's codebase.
  • No special environment variables or n8n configurations are needed beyond standard node setup.

Troubleshooting

  • Common issues:

    • Providing an incorrect binary property name when using binary data input will cause the node to fail to find the image.
    • Invalid base64 strings or inaccessible URLs will result in errors during image loading.
    • Unsupported image formats might cause processing failures.

  • Error messages and resolutions:

    • "Binary property not found": Verify that the binary property name matches the actual property in the incoming data.
    • "Failed to load image from URL": Check the URL accessibility and correctness.
    • "Invalid base64 content": Ensure the base64 string is properly encoded without extra characters or line breaks.

Links and References

Discussion