For the complete documentation index, see llms.txt. This page is also available as Markdown.

image Kind

Image in workflows.

Image in workflows

Data representation

External

External data representation is relevant for Workflows clients - it dictates what is the input and output format of data.

Type: dict

Internal

Internal data representation is relevant for Workflows blocks creators - this is the type that will be provided by Execution Engine in runtime to the block that consumes input of this kind.

Type: WorkflowImageData

Details

This is the representation of image in workflows. Underlying data type has different internal and external representation. As an input we support:

Update added in Execution Engine v1.2.0

video_metadata added as optional property - should be injected in context of video processing to provide necessary context for blocks dedicated to video processing.

  • np.ndarray image when Workflows Execution Engine is used directly in inference python package (array can be provided in a form of dictionary presented below, if video_metadata is intended to be injected)

  • dictionary compatible with inference image utils:

Whe using Workflows Execution Engine exposed behind inference server, two most common type values are base64 and url.

Internally, WorkflowImageData is used. If you are a Workflow block developer, we advise checking out usage guide.

Last updated

Was this helpful?