Testing Your Agent

The Test Drawer

Flow Builder at the Flow Builder includes a built-in test panel on the right side of the canvas. This is where you simulate conversations with your flow before deploying it to production. Click the Test button in the top toolbar to open the test drawer.

The test drawer connects directly to your flow's engine, using your configured API key and default model. It behaves exactly as a live deployment would, including transitions, variable extraction, API calls, and all node processing.

Starting a Test Conversation

1. Open your flow at the Flow Builder.
2. Ensure you have an API key configured (see Setting Up Your API Key).
3. Click the Test button in the toolbar.
4. The test drawer opens on the right side. The flow's start node fires automatically, and you see the agent's opening message.
5. Type a message in the input field and press Enter to continue the conversation.

As the conversation progresses, you can watch the canvas highlight the active node in real time. This visual feedback shows exactly where your flow is in its execution path.

Resetting a Session

Click the Reset button at the top of the test drawer to clear the conversation and start fresh. This wipes the conversation history, resets all variables to their initial state, and returns the flow to the start node.

Reset frequently during development. Flows often behave differently on the first visit to a node versus subsequent visits, and stale variable values from previous tests can mask bugs.

Reviewing Conversation History

The test drawer displays the full conversation history, including:

• Agent messages — responses generated by Conversation nodes
• User messages — your test inputs
• System events — node transitions, variable changes, and API call results

This gives you visibility into what is happening behind the scenes. If a transition fires unexpectedly or a variable is not populated correctly, the system events reveal the cause.

Variable Inspector

During a test session, you can inspect the current state of all flow variables. This shows you what data has been extracted, what values have been set, and what the engine is working with at any point in the conversation.

Use this to verify that Extraction nodes are capturing data correctly and that Variable nodes are composing values as expected.

Voice Testing

If your flow is configured for voice deployment, the test drawer also supports voice testing. This lets you hear how the agent sounds with text-to-speech applied, test interruption handling, and validate that speak-during-execution filler plays correctly during tool calls.

Voice testing is especially important for validating that static-mode messages sound natural when spoken aloud, and that transition timing feels responsive.

Tips for Effective Testing

• Test edge cases. Try unexpected inputs, empty responses, and off-topic messages to see how your transitions handle them.
• Watch the canvas. The highlighted node path tells you if the flow is routing correctly.
• Check variables after extraction. Use the variable inspector to confirm data is being captured accurately.
• Test the full path. Walk through every branch of your Logic nodes to ensure all paths lead to valid destinations.
• Reset between scenarios. Do not rely on variable state from a previous test when testing a new scenario.

Tip: If the test drawer shows no response, check that your API key is configured and that your start node is designated correctly.