Application Inputs

Learn about the application inputs for Flow

Voice-enabled applications often need to react to events beyond user speech. For instance:

• A user pauses for too long, requiring a prompt to keep the conversation going
• An external notification or system event which must be conveyed during a voice conversation

To handle these scenarios, the application can send an AddInput message to the Flow system. This allows non-verbal or system-driven inputs to be injected into the conversation dynamically.

{
  "message": "AddInput",
  "input": "<string>",                // Required: The input text to be incorporated
  "interrupt_response": "<boolean>",  // Optional: If true, interrupts the current response (default: false)
  "immediate": "<boolean>"            // Optional: If true, processes the input immediately after the current turn ends (default: false)
}

Application Input variables

See API reference for complete schema.

inputstringrequired

The information that the LLM must incorporate in the response

interrupt_responseboolean

If true, the response will be interrupted by the new input.
If false, the response will continue until it is complete, defaults to false.

Default value: false

immediateboolean

If true, the input will be treated as urgent and will be sent to LLM immediately.
If false, new input will be added to current prompt and sent to LLM as a part of the next request.

Default value: false