PDF4me

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: binary data from a previous node, a base64 encoded string, or a URL pointing to the image file. The flipped image is then output as binary data with a customizable filename.

Common scenarios where this node is useful include:

• Image preprocessing workflows where images need to be mirrored or flipped before further processing.
• Automated content creation pipelines that require image orientation adjustments.
• Preparing images for display or printing where flipping is necessary.

Practical example:

• A user receives product images via URL and wants to flip them vertically before uploading to their catalog.
• An automation workflow processes scanned documents and flips them horizontally to correct orientation issues.

Properties

Output

The node outputs the flipped image as binary data under the specified binary data output name (default is "data"). The output includes the flipped image file with the chosen output filename. This binary data can be used by subsequent nodes for further processing or saving.

Dependencies

• No external API keys or services are explicitly required based on the static code.
• The node depends on internal image processing capabilities provided by the bundled action module responsible for flipping images.
• No special environment variables or configurations are indicated.

Troubleshooting

• Common Issues:

  • Providing an incorrect binary property name when using binary data input may cause the node to fail to find the image.
  • Invalid or inaccessible URLs will result in errors fetching the image.
  • Malformed base64 strings will cause decoding failures.
  • Unsupported image formats might not be processed correctly.

• Error Messages:

  • Errors related to missing binary data typically mean the specified binary field does not exist in the input.
  • Network errors when using URL input indicate connectivity or URL validity problems.
  • Decoding errors suggest invalid base64 content.

• Resolutions:

  • Verify the binary property name matches exactly the name of the binary data field from the previous node.
  • Ensure URLs are accessible and point directly to image files.
  • Validate base64 strings before input.
  • Use supported image formats (commonly JPEG, PNG).

Links and References

• n8n Documentation on Working with Binary Data
• Base64 Encoding Reference
• Image Processing Concepts