Skip to content
Proud to collaborate with Microsoft for Startups

chat.conversation.send-message.return-payload ​

Assemble the canonical send-message response payload

Echo the assembled chat turn back as the DAG's final step output.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-chat
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
conversation_uuiduuidYes——
user_message_uuiduuidYes—Public uuid of the user-turn ChatMessage
assistant_message_uuiduuidYes—Public uuid of the assistant-turn ChatMessage
assistant_messagejsonYes——
workflow_run_uuiduuidNo——
workflow_run_idstringNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
assistant_messagejsonYes—Final assistant payload returned to the API caller
conversation_uuiduuidNo——
user_uuiduuidNo——
organization_uuiduuidNo——
user_messagestringNo——
provided_inputsjsonNo——
confirmed_actionjsonNo——
llm_connection_uuiduuidNo——
streambooleanNo——
deep_reasoningbooleanNo——
proactivebooleanNo——
workflow_run_uuiduuidNo——
workflow_run_idstringNo——
last_message_previewstringNo——
dgi_workflow_uuiduuidNo——
user_message_uuiduuidNo——
assistant_message_uuiduuidNo——
failure_reasonstringNo—Engine-stamped human-readable failure reason
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped step name (DAG path)
failed_layerintegerNo—Engine-stamped layer index (DAG path)
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "chat.conversation.send-message.return-payload",
  "initial_data": {
    "conversation_uuid": "value",
    "user_message_uuid": "value",
    "assistant_message_uuid": "value",
    "assistant_message": "value"
  }
}