Skip to main content
When components transmit or receive state, parameters, or content within a workflow session, the payload conforms precisely to structured Value Objects. Value objects provide strict typing enabling components to parse routing cleanly. All standard type objects require a rigid "type" string mapped uniquely to their implementation.

text

Represents explicit string content. Schema:
Value:

integer / float

Represents numeric data, distinguishing purely integer numbers from decimals. Schema:
Value:

boolean

Represents a binary true/false state. Schema:
Value:

choice

Used in dropdowns or rigid enum selection inputs. Schema:
Value:

message

The comprehensive payload unit representing generative AI prompts, replies, and contexts. It is structured to support tool usage, multimodal content via file attachments referenced by alias, and other components. Schema:
Value:
Messages can include file attachments via file content blocks, which reference file session objects by alias. The order of blocks is significant — a file block may sit between text blocks, and multimodal consumers read the file at that position rather than after the text. For details on the file session object and its properties, see File session object.

messages

An array containing sequential message objects, representing structured conversation strings or dialogue logs. Schema:
Value:

credential

Abstract identifier mapping to a securely stored alias in BlobHub’s secret vault. Schema:
Value: