Run draft workflows on one real record

Teams can now test a saved workflow draft on one real record from chat, investigate recent workflow runs with clearer evidence, and let the builder read from supported connected systems before it asks for details.

Test one real record before publishing

You can now ask chat to run a saved workflow draft on one specific record and show what each step did. If you want to preview safely first, chat can stop before the first write. If a step fails, chat can surface the error, help update the draft, and run it again. This works on one named record at a time, and publishing still stays a separate confirmation step.

Investigate recent runs from chat

Chat now gives clearer answers about recent workflow runs, including what happened in a run, which step failed, and what the step returned when that evidence is available. You can also look up runs using a business reference such as an order number instead of starting with a run ID. If chat only searched part of the requested window, it can say so rather than implying nothing was found.

Let the builder read before asking

The workflow builder can now read supported lists and records from your connected system so it can use your organization’s existing names more often instead of asking you to type them in. For supported setups, the builder reads from either NikoHealth or Brightree based on your organization’s configuration, and these builder reads stay read-only. If the exact value is not available, the builder may still ask you to choose from what it found.

Approve more email actions by reply

Email chat now supports more action requests using the same durable chat engine as web chat. When an email request would make a change, the reply email shows the proposed action and waits for a YES reply before it runs. Teams can turn off actions by email in settings. Some actions still are not available over email, so unsupported requests will continue to stay out of this flow.

Smaller improvements

• Workflow builder edits are smoother: replying yes to a suggested setting now works more reliably, and some targeted workflow table edits that previously stalled can now be saved from chat.

• Desktop users can start a new chat from the Chats header and delete their own chats from the sidebar. Deleted chats are removed from lists and search, but direct links to those chats still open.

• When resolving a document flag, teams can now add an optional resolution note and see it later in the flag’s history.

• Workflows now include a NikoHealth action for adding diagnosis codes to a patient when the workflow selects those codes.