Resource and Operation Reference

The Davix H2I n8n node organizes its functionality through a resource-and-operation model. You first choose a Resource, and the node then shows the operations that belong to that resource. This structure is defined directly in the node’s UI and runtime model.

The four supported resources are:

• H2I
• Image
• PDF
• Tools

Each resource maps to a specific API endpoint path and uses its own operation set, request style, and field group.

[Image placeholder — n8n node editor showing the Resource selector with H2I, Image, PDF, and Tools options]

Resource model overview #

The Resource field in the node UI is an options field with these values:

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

This field controls which operation selector is shown and which runtime request branch the node uses. It is not sent as an API parameter itself.

Operation selector behavior #

The node defines a separate operation selector for each resource:

• one operation selector when resource = h2i
• one operation selector when resource = image
• one operation selector when resource = pdf
• one operation selector when resource = tools

This means operations are grouped by resource rather than mixed into one combined list.

Endpoint mapping model #

All runtime API calls are sent through the shared davixRequest helper, which constructs the final request URL from the configured Base URL plus the selected endpoint path and injects the x-api-key header.

The resource-to-endpoint mapping is:

• H2I → POST /v1/h2i
• Image → POST /v1/image
• PDF → POST /v1/pdf
• Tools → POST /v1/tools

Resource: H2I #

The H2I resource is labeled in the node UI as H2I (HTML → Image) and is used for HTML rendering workflows.

Supported H2I operations #

• Render HTML to Image → image
• Render HTML to PDF → pdf

These operations are shown only when the selected resource is h2i.

H2I execution behavior #

At runtime, the H2I resource sends a JSON request body to /v1/h2i. It does not require binary input properties. Instead, it uses fields such as HTML, CSS, dimensions, and rendering options.

When binary download is enabled, the node can download the returned URL and attach it as binary output.

H2I workflow scope #

The H2I resource supports:

• HTML-to-image rendering
• HTML-to-PDF rendering
• optional binary download of returned output URLs

Resource: Image #

The Image resource is labeled as Image (Transform / Export PDF) and is used for image-processing, metadata, export, and combined-action workflows.

Supported Image operations #

• Format → format
• Resize → resize
• Crop → crop
• Transform → transform
• Compress → compress
• Enhance → enhance
• Padding → padding
• Frame → frame
• Background → background
• Watermark → watermark
• PDF Export → pdf
• Metadata (JSON only) → metadata
• Multitask → multitask

These operations are shown only when the selected resource is image.

Image execution behavior #

At runtime, the Image resource sends multipart formData to /v1/image. It reads one or more image binaries from the configured imageBinaryProps list and attaches them under the multipart field name images.

Operation-specific fields are added according to the selected action.

Image workflow scope #

The Image resource covers:

• format conversion
• resizing
• cropping
• transforms such as rotation and flipping
• compression
• enhancement
• padding
• frame and border output
• background processing
• watermarking
• image-to-PDF export
• metadata output
• multitask workflows that combine multiple selected actions

Image public behavior notes #

The Image resource supports optional binary download for most operations. When enabled, the node downloads returned URLs and attaches them to the output item as binary data. For the metadata operation, binary download is forced off.

Image multitask also has runtime validation: at least one selected action is required.

[Image placeholder — n8n node editor showing the Image resource with the operation dropdown open]

Resource: PDF #

The PDF resource is labeled as PDF (Merge/Split/Compress/Convert) and is used for workflows that operate on PDF binaries.

Supported PDF operations #

• To Images → to-images
• Merge → merge
• Split → split
• Compress → compress
• Extract Images → extract-images
• Watermark → watermark
• Rotate → rotate
• Metadata → metadata
• Reorder → reorder
• Delete Pages → delete-pages
• Extract Pages → extract
• Flatten → flatten
• Encrypt → encrypt
• Decrypt → decrypt

These operations are shown only when the selected resource is pdf.

PDF execution behavior #

At runtime, the PDF resource sends multipart formData to /v1/pdf. It reads one or more PDF binaries from pdfBinaryProps and attaches them under the multipart field name files. Some PDF operations also support an optional watermarkImage file input.

PDF workflow scope #

The PDF resource supports workflows such as:

• page-to-image conversion
• merge
• split
• compress
• extract images
• watermark
• rotate
• metadata
• reorder
• delete pages
• extract pages
• flatten
• encrypt
• decrypt

PDF public behavior notes #

The PDF resource supports optional binary download when the response includes downloadable URLs. That output is controlled by the PDF binary-download settings rather than being always enabled.

The reorder operation also includes runtime validation for invalid JSON arrays and invalid page-order arrays.

Resource: Tools #

The Tools resource is labeled as Tools (Analyze Images) and is used for image-analysis workflows.

Supported Tools operations #

• Single Tool → single
• Multitask → multitask

These operations are shown only when the selected resource is tools.

Supported tool selections #

The documented tool set includes:

• metadata
• colors
• detect-format
• orientation
• hash
• similarity
• dimensions
• palette
• transparency
• quality
• efficiency

Tools execution behavior #

At runtime, the Tools resource sends multipart formData to /v1/tools. It reads image binaries from toolsBinaryProps and attaches them under the multipart field name images. Tool-specific fields are added according to the selected single tool or multitask tool set.

Tools public behavior notes #

The Tools resource is JSON-oriented. The current node implementation does not include a binary-download output branch for Tools, so Tools results are documented as JSON output.

Runtime validation also applies here:

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

[Image placeholder — n8n node editor showing the Tools resource with Single Tool and Multitask operations]

Request-style summary by resource #

The request style differs by resource:

• H2I → JSON body
• Image → multipart formData
• PDF → multipart formData
• Tools → multipart formData

This affects what kind of input the node expects:

• H2I is driven by text and rendering options
• Image, PDF, and Tools are driven by binary input properties plus operation-specific parameters

Validation behavior tied to operations #

The loaded source files document several operation-specific validations:

• Image multitask requires at least one selected action
• Tools single requires one selected tool
• Tools multitask requires at least one selected tool
• PDF reorder validates order input
• binary-download branches require a URL in the response when download is enabled

These validations are part of the node’s runtime operation model and help define what counts as a valid request for each operation type.

How to use this page with the rest of the n8n docs #

This page defines the high-level structure of the node:

• which resources exist
• which operations belong to each resource
• which endpoint path each resource uses
• which request style each resource uses

Use the Field Reference page for operation-specific parameter details, the File and Binary Handling page for binary input and output behavior, and the Error Handling and Troubleshooting page for validation and execution failures.