Skip to main content
Edit a draft safely, resolve node requirements, and verify changes before publishing them.

​
Prerequisites

  • A workflow you can edit.
  • A test scenario that exercises the node being changed.

​
Save and validate

  1. Open the workflow from the Console.
  2. Select a node and choose its edit action.
  3. Update the node fields, then save the node.
  4. Review the canvas status and resolve missing required values or disconnected paths.
  5. Run the workflow tester against the draft before publishing.

​
Keep each conversation step focused

Give each node one task and each outgoing connection an observable condition. When a later node collects service-request details, the opening node should identify that intent and route to it. Avoid asking the opening node to complete the whole request as well. During a call, the agent receives the current node and its available outgoing transitions. The agent is instructed to call the matching transition when its condition is met and wait for the next node’s instructions. A single outgoing connection still requires its condition to be met. These instructions also apply to nodes with the global prompt disabled. After a successful transition, the next reply uses the new node’s instructions and available tools while retaining tool results and the existing tool-call limit. The model stream is closed when a response finishes, fails, or is interrupted. Test both a caller who meets a transition condition and one who asks an unresolved question. Check that the active node changes at the intended point and that the next node takes over its own task. Prompt instructions guide the model; they do not guarantee every routing decision. Keep confirmation language tied to real outcomes. Collecting a preferred time does not save a booking. Say a booking is saved or confirmed only after a configured booking integration succeeds; otherwise explain the pending next step.

​
Add quiet call ambience

Open Settings → General → Ambient Noise, enable Use Ambient Noise, and save the general settings. Without a custom file, the agent plays the built-in office ambience continuously beneath its voice, including during pauses. Ambience is disabled by default. Start with the default volume of 0.3 and test a call. The range is 0–1; 0 is silent. Keep names, numbers, and quiet speech easy to understand. The same setting applies to browser and telephone calls. You can upload an audio file up to 10 MB instead. Use a recording you have permission to use, without intelligible private conversations or sudden loud sounds. Removing the custom file restores the office preset. An unavailable custom file plays no ambience; a background playback failure leaves the voice call running. Ambience ends when the agent session closes, including transfer to a human. Test the saved draft before publishing it for future production calls. Disable Use Ambient Noise and publish again to remove it.

​
Constraints and failure states

Test mode uses the latest draft, while production execution uses the published agent. A change that is saved but not published does not change production behavior. Required fields, invalid references, and graph constraints must be corrected before a reliable test. Browser playback timing is recorded only after audio starts playing. Blocked, paused, muted, or zero-volume playback does not count as an audible response. Allow audio playback before comparing response times.

​
Protect your data

Keep test prompts and context synthetic. If a field accepts a credential or customer data, use a managed reference and limit the value to the smallest necessary scope.

​
Completed test calls

When an agent ends a browser call, the tester returns to its finished state. An unexpected connection loss still offers Retry. Run durations appear in minutes and seconds, for example 1m 39s. A transcript can be available without a recording when the recording upload fails; successful transcript saving alone does not confirm audio storage.