The Get Scenario Data workflow provides a simple way to retrieve structured configuration for chatbot scenarios. Each scenario includes its own prompt, rules, mood options, animations, and text-to-speech (TTS) settings, allowing your chatbot to adapt behavior and personality dynamically.
Triggered by Another Workflow
scenario
→ the key identifying which scenario’s configuration should be retrieved.Scenarios Definition
A predefined list of scenarios is stored inside the workflow. Each scenario contains:
prompt
→ system instruction for the chatbot’s role.rules
→ constraints or behavioral guidelines.mood
→ array of emotional tones available.animation
→ available animation states.tts-prompt
→ detailed TTS voice and delivery instructions.tts-voice
→ voice name to use.Get Scenario Data
scenario
key in the stored definitions.scenarioData
.scenario
(string, e.g. "customer-service"
){ "scenario": "" // Key of the desired scenario (e.g. "customer-service" or "wellness-center"). }
{ "scenario": "", // The key of the requested scenario. "scenarioData": { "prompt": "", // The system prompt defining the chatbot's role and behavior. "rules": "", // Specific rules and constraints for the chatbot. "mood": [], // Array of moods the chatbot can express. "animation": [], // Array of animation states available for the chatbot. "tts-prompt": "", // Instructions for the TTS voice and style. "tts-voice": "" // The name of the TTS voice to use. } }
This workflow is called from chat and text-to-speech workflows to dynamically load scenario configurations.
Pass the scenario
key to retrieve the corresponding setup.
Use the returned scenarioData
to:
Comes preloaded with two scenarios:
customer-service
wellness-center
Easily extendable by adding more entries in the Scenarios Definition node.