Overview
This node generates barcodes from input text. It supports a wide variety of barcode types, allowing users to create barcodes for different standards and use cases such as QR codes, postal codes, product codes (EAN, UPC), pharmaceutical codes, and many others.
Common scenarios include:
- Generating QR codes for URLs, contact info, or event tickets.
- Creating product barcodes for inventory management.
- Producing postal barcodes for shipping labels.
- Encoding data in specialized barcode formats for healthcare or logistics.
Practical example: You can input a product SKU as text and generate an EAN-13 barcode image to print on packaging or scan at checkout.
Properties
| Name | Meaning |
|---|---|
| Text | The text content to encode into the barcode. This is required and can be any string you want represented as a barcode. |
| Barcode Type | Select the type of barcode to generate. Options include many barcode standards such as QR Code, Code 128, EAN-13, UPC-A, Data Matrix, PDF417, Aztec, and many postal and industry-specific formats. |
| Hide Text | Boolean option to hide or display the human-readable text alongside the barcode image. Default is to hide the text. |
| Advanced Options | A collection of optional advanced settings: • Generate Inline URL: Whether to produce an inline image URL for the barcode instead of a file or other output. • Custom Profiles: JSON string to specify custom API options for barcode generation. |
Output
The node outputs JSON data containing the generated barcode. The exact structure depends on the implementation of the barcode generator action but typically includes:
- The barcode image data, often encoded as a base64 string or a URL if inline images are requested.
- Metadata about the barcode such as type and possibly dimensions.
If binary data is output, it represents the barcode image file suitable for saving or further processing.
Dependencies
- This node relies on an external barcode generation service or library accessed via API calls.
- It requires configuration of an API key credential to authenticate requests to the barcode generation backend.
- The "Custom Profiles" property allows passing additional JSON options to customize the API call behavior.
Troubleshooting
- Invalid barcode type or unsupported text: If the text does not conform to the selected barcode standard, the API may return an error. Verify that the text matches the requirements of the chosen barcode type.
- API authentication errors: Ensure the API key credential is correctly configured and has permissions to access the barcode generation service.
- Malformed JSON in Custom Profiles: If using the advanced "Custom Profiles" option, ensure the JSON string is valid and properly formatted.
- Empty or missing text input: The "Text" property is required; leaving it empty will cause the node to fail.
Links and References
- Barcode Types Reference — Overview of supported barcode standards.
- PDF4me API Documentation — For details on custom profiles and advanced API options related to barcode generation.