Field Reference

The Davix H2I n8n node uses a field-driven UI model. The fields shown in the node panel depend on the selected Resource and Operation. This behavior is defined in the node’s description.properties through resource-specific operation selectors and field-level display conditions.

This page documents the field model for the node as a user-facing reference:

• global selection fields
• H2I fields
• Image fields
• PDF fields
• Tools fields
• output download fields
• field visibility behavior
• request mapping behavior

How the field model works #

The node defines:

• one global Resource field
• one resource-specific Operation field for each resource
• operation-specific fields that appear only when their display conditions match the selected resource and operation

This means the node does not show every field at once. Changing the selected resource and operation changes both the visible form and the request structure used at runtime.

Global fields #

Resource #

The Resource field is a global options field. It controls the top-level behavior of the node and determines which operation selector and field groups are shown.

Documented values:

• H2I (HTML → Image) → h2i
• Image (Transform / Export PDF) → image
• PDF (Merge/Split/Compress/Convert) → pdf
• Tools (Analyze Images) → tools

Documented default value:

• h2i

The field-level documentation states that this field:

• controls node branch selection
• is not sent as an API parameter
• drives visibility and behavior for the rest of the UI through display conditions

[Image placeholder — n8n node editor showing the Resource selector at the top of the node panel]

Operation #

The node defines a separate Operation field for each resource. Each is an options field shown only when its matching resource is selected.

Documented defaults:

• H2I → image
• Image → format
• PDF → merge
• Tools → single

The field-level documentation states that the Operation field maps to the request action for the selected resource.

H2I fields #

The H2I resource exposes fields for HTML rendering workflows. These fields are shown when resource = h2i, with some fields further restricted by operation = image or operation = pdf.

Core H2I input fields #

HTML

• internal name: html
• type: string
• required: yes
• shown for: H2I → image, pdf
• default: empty string
• maps to request parameter: html

CSS

• internal name: css
• type: string
• required: no
• shown for: H2I → image, pdf
• default: empty string
• maps to request parameter: css

Width

• internal name: width
• type: number
• required: no
• shown for: H2I → image, pdf
• default: 1000
• maps to request parameter: width

Height

• internal name: height
• type: number
• required: no
• shown for: H2I → image, pdf
• default: 1500
• maps to request parameter: height

The field documentation notes that number fields such as width and height are converted to strings and omitted when the value is 0.

H2I image-render fields #

Shown when:

• resource = h2i
• operation = image

Format

• internal name: format
• type: options
• default: png
• values:
  • PNG → png
  • JPEG → jpeg
• maps to request parameter: format

H2I PDF-render fields #

Shown when:

• resource = h2i
• operation = pdf

PDF Format

• internal name: pdfFormat
• type: options
• default: a4
• values:
  • A4 → a4
  • Letter → letter

PDF Landscape

• internal name: pdfLandscape
• type: boolean
• default: false

Prefer CSS Page Size

• internal name: preferCSSPageSize
• type: boolean
• default: true

Scale

• internal name: scale
• type: number
• default: 1

Print Mode

• internal name: printMode
• type: boolean
• default: false

Print Background

• internal name: printBackground
• type: boolean
• default: true

H2I output-download fields #

Download Result as Binary

• internal name: downloadBinary
• type: boolean
• default: false
• shown for: H2I → image, pdf
• purpose: controls post-response file download, not an API request field

Output Binary Property

• internal name: outputBinaryProperty
• type: string
• default: data
• shown when:
  • resource = h2i
  • operation = image or pdf
  • downloadBinary = true
• purpose: output binary key name in n8n output

When H2I binary download is enabled, the node downloads a returned URL, converts it to n8n binary data, and stores it under the configured output binary property.

[Image placeholder — H2I operation fields showing HTML, CSS, width, height, and Download Result as Binary]

Image fields #

The Image resource exposes fields for binary image input, transformation, export, metadata, and multitask processing. These fields are shown when resource = image, with additional conditions depending on the selected Image operation.

Image input field #

Input Binary Properties

• internal name: imageBinaryProps
• type: string
• default: data
• shown for: Image → Global
• purpose: comma-separated binary property names read from the input item and attached as multipart images files

Multiple files are supported because the field is split by comma, trimmed, and iterated.

Shared Image fields #

Some Image fields are broadly available across multiple operations.

Format

• internal name: imageFormat
• type: options
• shown for: Image → Global
• default: webp

Width / Height

• internal names: imageWidth, imageHeight
• type: number
• shown for:
  • Width → resize, format
  • Height → resize, format

Keep Metadata

• internal name: keepMetadata
• type: boolean
• shown for:
  • format, resize, crop, transform, compress, enhance, padding, frame, background, watermark, pdf
• purpose: controls metadata retention behavior for those operations

Image operation field groups #

Resize

• fields include: imageWidth, imageHeight, enlarge, normalizeOrientation

Crop

• fields include: cropX, cropY, cropWidth, cropHeight, backgroundColor, normalizeOrientation

Transform

• fields include: rotate, flipH, flipV, colorSpace

Compress

• fields include: backgroundColor, colorSpace, targetSizeKB, quality

Enhance

• fields include: normalizeOrientation, blur, sharpen, grayscale, sepia, brightness, contrast, saturation

Padding

• fields include: pad, padTop, padRight, padBottom, padLeft, padColor, borderRadius

Frame

• fields include: pad, border, borderColor, padColor

Background

• fields include: backgroundColor, padColor, borderRadius, backgroundBlur

Watermark

• fields include: watermarkText, watermarkFontSize, watermarkColor, watermarkOpacity, watermarkPosition, watermarkMargin, watermarkScale, watermarkImageBinaryProp

The optional watermarkImageBinaryProp field can be used to attach a single watermark image file as multipart input.

Image PDF Export

• fields include: pdfMode, pdfPageSize, pdfOrientation, pdfMargin, pdfEmbedFormat, pdfJpegQuality, keepMetadata

Image Metadata

• fields include: includeRawExif

Image Multitask fields #

The Multitask operation exposes its own field set, including:

• actions
• format
• keepMetadata
• width
• height
• enlarge
• normalizeOrientation
• crop fields
• transform fields
• compression fields
• enhancement fields
• padding and frame fields
• background fields
• watermark fields
• watermarkImageBinaryProp

At least one selected action is required for Image Multitask.

Image output-download fields #

Download Result(s) as Binary

• internal name: imageDownloadBinary
• type: boolean
• shown for:
  • format, resize, crop, transform, compress, enhance, padding, frame, background, watermark, pdf, multitask

Output Binary Property

• internal name: imageOutputBinaryProperty
• type: string
• purpose: output binary property name for downloaded results

Image binary download can attach one or more downloaded files, using suffixed property names such as _0, _1, and so on for multi-file results.

[Image placeholder — Image resource fields showing Input Binary Properties and operation-specific controls]

PDF fields #

The PDF resource exposes fields for PDF upload, conversion, modification, extraction, metadata, and protection workflows. These fields are shown when resource = pdf, with further restrictions based on the selected PDF operation.

PDF input field #

Input Binary Properties

• internal name: pdfBinaryProps
• type: string
• default: data
• shown for: PDF → Global
• purpose: comma-separated binary property names used to attach multipart files inputs for the PDF resource

PDF operation field groups #

Merge

• fields include: sortByName

Split

• fields include: ranges, prefix

Extract

• fields include: mode, pages, prefix

To Images

• fields include: pages, toFormat, pdfWidth, pdfHeight, dpi

Extract Images

• fields include: pages, extractImageFormat

Watermark

• fields include: pages, watermarkText, watermarkOpacity, watermarkPosition, watermarkMargin, watermarkX, watermarkY, watermarkFontSize, watermarkColor, watermarkScale, watermarkImageBinaryProp

Rotate

• fields include: pages, degrees

Metadata

• fields include: title, author, subject, keywords, creator, producer, cleanAllMetadata

Reorder

• fields include: order

The runtime validates invalid reorder JSON and invalid order arrays.

Flatten

• fields include: flattenForms

Encrypt

• fields include: userPassword, ownerPassword

Decrypt

• fields include: password

These password inputs are defined as password-style fields in the node UI.

PDF output-download fields #

Download Result(s) as Binary

• internal name: pdfDownloadBinary
• shown for: PDF → Global

Output Binary Property

• internal name: pdfOutputBinaryProperty
• shown for: PDF → Global
• purpose: output binary key for downloaded PDF resource results

PDF results can optionally be downloaded as binary output when the response includes a downloadable URL.

Tools fields #

The Tools resource exposes fields for image-analysis workflows. These fields are shown when resource = tools. The resource supports two operations: single and multitask.

Tools input field #

Input Binary Properties

• internal name: toolsBinaryProps
• type: string
• default: data
• purpose: comma-separated binary property names used to attach multipart images inputs for Tools analysis requests

Tools selection fields #

Tool

• internal name: tool
• type: options
• shown for: Tools → single

Tools

• internal name: tools
• type: multiOptions
• shown for: Tools → multitask

Runtime validation confirms:

• Single Tool requires one tool selection
• Multitask requires at least one tool selection

Tools parameter fields #

Single Tool

• fields include: metadataIncludeRawExifSingle, paletteSizeSingle, hashTypeSingle, similarityModeSingle, similarityThresholdSingle, qualitySampleSingle, transparencySampleSingle, efficiencyFormatSingle, efficiencyQualitySingle

Multitask

• fields include: metadataIncludeRawExifMulti, paletteSizeMulti, hashTypeMulti, similarityModeMulti, similarityThresholdMulti, qualitySampleMulti, transparencySampleMulti, efficiencyFormatMulti, efficiencyQualityMulti

These fields correspond to documented tool-configuration controls for metadata, palette, hash, similarity, quality, transparency, and efficiency workflows.

[Image placeholder — Tools resource fields showing Single Tool, Multitask, and tool-parameter controls]

Field visibility behavior #

The field-level UI specification documents display-condition behavior throughout the node. In public terms, that means:

• a field appears only when its required resource is selected
• many fields appear only when both the resource and a specific operation are selected
• some output-binary fields appear only when the matching binary-download toggle is enabled

This explains why users will not see every parameter at once.

Request mapping behavior #

The field reference docs describe the field-to-request relationship as follows:

• Resource controls branch selection and is not sent as an API parameter
• Operation maps to request action
• H2I fields map into a JSON body
• Image, PDF, and Tools fields map into multipart formData
• binary-property fields are used to read uploaded input files from the n8n item and attach them as multipart files
• output-binary-property fields are used after the response to store downloaded files in the n8n output item