Example Workflows and Use Cases

The Davix H2I n8n node is designed for workflow-driven use across four resource groups:

  • H2I
  • Image
  • PDF
  • Tools

Because the node processes input items one by one, reads resource and operation selections per item, and can optionally attach binary output for supported resources, it fits workflows where rendering, transformation, extraction, or analysis needs to be chained into downstream automation steps. The implementation-backed documentation also confirms that the node supports both JSON-only output and optional binary output, depending on the selected resource and settings.

This page documents example workflow categories and use cases that are directly supported by the repository’s documented resource and operation model.

How to read these examples #

Each example in this page is based on:

  • one of the documented resources
  • one or more documented operations
  • the documented input model
  • the documented output model
  • the documented binary-download behavior when applicable

These examples are presented as workflow patterns rather than full exported n8n workflow JSON, because the loaded SSOT files document the node through its resource model, fields, binary handling, and runtime behavior.

Workflow category overview #

The node supports these workflow categories:

  • HTML rendering workflows
  • image transformation workflows
  • PDF processing workflows
  • image-analysis workflows
  • binary-download workflows

Example 1: HTML to Image workflow #

One of the clearest documented uses of the node is rendering HTML into an image through the H2I resource.

Resource and operation

  • Resource: h2i
  • Operation: image

Typical fields

  • html
  • css
  • width
  • height
  • format
  • optional downloadBinary
  • optional outputBinaryProperty

Request model

  • JSON request body to /v1/h2i
  • no input binary files required

Output model

  • backend response in json
  • optional downloaded binary output if downloadBinary is enabled and the response contains a URL

Use cases

  • render HTML content into an image
  • generate image output from template-like HTML and CSS
  • pass either response metadata or downloaded binary image content into later workflow steps

[Image placeholder — H2I image workflow in n8n showing HTML, CSS, and image output settings]

Example 2: HTML to PDF workflow #

The same H2I resource also supports rendering HTML into PDF output.

Resource and operation

  • Resource: h2i
  • Operation: pdf

Typical fields

  • html
  • css
  • width
  • height
  • pdfFormat
  • pdfLandscape
  • preferCSSPageSize
  • scale
  • printMode
  • printBackground
  • optional downloadBinary
  • optional outputBinaryProperty

Request model

  • JSON request body sent to /v1/h2i

Output model

  • backend response in json
  • optional binary PDF download when enabled and when the response includes a URL

Use cases

  • produce PDF output from HTML and CSS
  • pass rendered PDF output to downstream workflow steps
  • keep the result as JSON metadata or convert it into binary output for later nodes

Example 3: Image format conversion workflow #

The Image resource supports format-oriented image processing workflows.

Resource and operation

  • Resource: image
  • Operation: format

Typical fields

  • imageBinaryProps
  • imageFormat
  • optional imageWidth
  • optional imageHeight
  • keepMetadata
  • optional imageDownloadBinary
  • optional imageOutputBinaryProperty

Request model

  • multipart formData to /v1/image
  • uploaded image binaries attached under the multipart field name images

Use cases

  • convert uploaded images to another format
  • prepare outputs for later delivery or storage
  • keep response metadata while optionally attaching the transformed file as binary output

Example 4: Image resize workflow #

The node supports image resizing through the Image resource.

Resource and operation

  • Resource: image
  • Operation: resize

Typical fields

  • imageBinaryProps
  • imageWidth
  • imageHeight
  • enlarge
  • normalizeOrientation
  • keepMetadata
  • optional binary-download controls

Use cases

  • resize input images before later workflow steps
  • normalize image orientation during processing
  • keep the resulting file as workflow binary output for later use

Example 5: Image watermark workflow #

The node supports text and optional image watermark workflows under the Image resource.

Resource and operation

  • Resource: image
  • Operation: watermark

Typical fields

  • imageBinaryProps
  • watermarkText
  • watermarkFontSize
  • watermarkColor
  • watermarkOpacity
  • watermarkPosition
  • watermarkMargin
  • watermarkScale
  • optional watermarkImageBinaryProp
  • optional binary-download controls

Request model

  • main image files uploaded under images
  • optional watermark image attached under watermarkImage

Use cases

  • apply watermark text to uploaded images
  • control watermark styling and positioning
  • optionally use a dedicated watermark image file in the same request path

[Image placeholder — Image watermark workflow showing watermark text fields and watermark image binary property]

Example 6: Image multitask workflow #

The Image resource also supports combined image-processing workflows through Multitask.

Resource and operation

  • Resource: image
  • Operation: multitask

Typical fields

  • imageBinaryProps
  • actions
  • grouped parameters covering format, resize, crop, transform, compression, enhancement, padding, frame, background, and watermark behavior
  • optional watermarkImageBinaryProp
  • optional binary-download controls

Validation

  • at least one selected action is required

Use cases

  • apply multiple image actions in one execution path
  • keep one combined transformation step inside a workflow
  • avoid splitting several Image operations across separate nodes when the multitask model fits the workflow

Example 7: PDF to images workflow #

The PDF resource supports conversion of PDF pages into images.

Resource and operation

  • Resource: pdf
  • Operation: to-images

Typical fields

  • pdfBinaryProps
  • pages
  • toFormat
  • pdfWidth
  • pdfHeight
  • dpi
  • optional pdfDownloadBinary
  • optional pdfOutputBinaryProperty

Request model

  • PDF files uploaded under the multipart field name files

Use cases

  • convert PDF pages into image outputs
  • extract page imagery into later visual-processing steps
  • attach converted outputs as n8n binary data when download is enabled

Example 8: PDF merge workflow #

The PDF resource supports combining PDF files.

Resource and operation

  • Resource: pdf
  • Operation: merge

Typical fields

  • pdfBinaryProps
  • sortByName
  • optional binary-download controls

Use cases

  • merge multiple PDF inputs from one n8n item
  • optionally sort merge inputs by name
  • return merged output metadata and optionally download merged output as binary

Example 9: PDF split or extract workflow #

The PDF resource supports splitting and extraction workflows.

Split

  • Resource: pdf
  • Operation: split
  • documented fields: ranges, prefix

Extract Pages

  • Resource: pdf
  • Operation: extract
  • documented fields: mode, pages, prefix

Use cases

  • split PDFs by range
  • extract specific pages
  • control naming behavior through the documented prefix field
  • pass outputs on as metadata or downloaded binary files when supported by the response path

Example 10: PDF watermark workflow #

The PDF resource also supports watermark workflows.

Resource and operation

  • Resource: pdf
  • Operation: watermark

Typical fields

  • pages
  • watermarkText
  • watermarkOpacity
  • watermarkPosition
  • watermarkMargin
  • watermarkX
  • watermarkY
  • watermarkFontSize
  • watermarkColor
  • watermarkScale
  • optional watermarkImageBinaryProp

Use cases

  • add watermark text to selected PDF pages
  • apply watermark position and styling options
  • optionally use a watermark image input where supported

Example 11: PDF metadata and protection workflows #

The PDF resource supports metadata and protection-related operations.

Metadata

  • Operation: metadata
  • documented fields: title, author, subject, keywords, creator, producer, cleanAllMetadata

Encrypt

  • Operation: encrypt
  • documented fields: userPassword, ownerPassword

Decrypt

  • Operation: decrypt
  • documented field: password

Use cases

  • update or clean PDF metadata
  • protect a PDF through password-related fields
  • remove password protection with the documented decrypt input field

Example 12: Tools single-analysis workflow #

The Tools resource supports single analysis operations for uploaded images.

Resource and operation

  • Resource: tools
  • Operation: single

Typical fields

  • toolsBinaryProps
  • tool
  • tool-specific parameter fields such as:
    • metadataIncludeRawExifSingle
    • paletteSizeSingle
    • hashTypeSingle
    • similarityModeSingle
    • similarityThresholdSingle
    • qualitySampleSingle
    • transparencySampleSingle
    • efficiencyFormatSingle
    • efficiencyQualitySingle

Validation

  • one tool selection is required

Use cases

  • run one analysis tool against input images
  • inspect metadata, hash, similarity, palette, transparency, quality, or efficiency depending on the chosen tool and parameters
  • return structured JSON analysis output for downstream logic

Example 13: Tools multitask-analysis workflow #

The Tools resource also supports multiple analysis tools in a single request.

Resource and operation

  • Resource: tools
  • Operation: multitask

Typical fields

  • toolsBinaryProps
  • tools
  • multitask parameter fields such as:
    • metadataIncludeRawExifMulti
    • paletteSizeMulti
    • hashTypeMulti
    • similarityModeMulti
    • similarityThresholdMulti
    • qualitySampleMulti
    • transparencySampleMulti
    • efficiencyFormatMulti
    • efficiencyQualityMulti

Validation

  • at least one tool must be selected

Use cases

  • run several image-analysis tools in one step
  • build branching logic from combined analysis output
  • keep the output in JSON form for later workflow decisions rather than binary file handling

[Image placeholder — Tools multitask workflow showing multiple selected tools and analysis settings]

Example 14: Binary-download workflow pattern #

A cross-resource pattern supported by the node is enabling binary download after a successful response.

Supported resources

  • H2I
  • Image
  • PDF

Relevant fields

H2I

  • downloadBinary
  • outputBinaryProperty

Image

  • imageDownloadBinary
  • imageOutputBinaryProperty

PDF

  • pdfDownloadBinary
  • pdfOutputBinaryProperty

Use cases

  • take a returned result URL and convert it into n8n binary data
  • pass file content to downstream nodes that require binary input
  • preserve the original backend response in json while also attaching the downloaded file in binary

Important constraint

  • if binary download is enabled but the response does not contain a URL, the node throws No URL returned to download.

Designing workflows with this node #

The repository documentation supports several general workflow design patterns.

JSON-first pattern #

Use the node for analysis or metadata retrieval and continue using item.json in downstream steps. This pattern is especially aligned with:

  • Tools workflows
  • metadata-oriented operations
  • cases where you want workflow logic based on returned data rather than file content

Binary-output pattern #

Enable binary download for H2I, Image, or PDF when the next node expects a file rather than only metadata.

Single-operation pattern #

Use one resource and one focused operation per node when you want clearer workflow separation and simpler troubleshooting. This fits the node’s resource-and-operation execution model.

Combined-operation pattern #

Use Image Multitask or Tools Multitask when the documented combined field model fits the workflow and you want to keep several related steps inside one node execution path.

Was it helpful ?
Table of contents
Login
Login
Login
Login
Scroll to Top