View Image

Node catalog Transformations
On this page

Display an image from a URL or base64 data

Usage and specifics

Prepare an image preview from a URL or base64. MIME type and alternative text describe the image; this is not file hosting.

Technical type : view_image. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter Type Default Values / limits
sourceType enum "url" url, base64
source string "" -
mimeType string "image/webp" -
alt string "" -

Configuration help

sourceType
Source type
Direct URL, workflow field, or base64 data.
source
Image source
Direct URL or path to an HTTP response (e.g. nodes.http1.body). Binary images (webp, png…) are detected automatically.
mimeType
MIME type
Explicit MIME type when not auto-detected.
alt
Alt text
Alternative text shown if the image fails to load.

Examples

  • HTTP: nodes.http1.body after a GET image/webp
  • Base64: nodes.http1.body.data or {{ nodes.edit_image1.data }}

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json
{
  "sourceType": "url",
  "source": "",
  "mimeType": "image/webp",
  "alt": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : Expressions and data, Executions, Node catalog.