A important part of building something is testing it out. For this reason, we've included a simulator in the flow editor that allows you to test your flows from an end user's perspective - so you can quickly identify what works and what might need to be tweaked.

Accessing the Simulator

The simulator is accessed through the phone icon on the right side of the flow editor:

Once clicked, the simulator will initiate the first step in your flow. The text in the red boxes below represents the action log. The action log describes actions that occur within the platform that aren't visible to the end user when interacting with a flow. The action log in the flow simulated below indicates that the following: 

  • the response "Jane Doe" has been assigned to the flow variable @results.name.
  • the contact's name attribute has been updated from its previous value to "Jane Doe" via an Update the Contact action.
  • the response "Dertu" has been assigned to the flow variable @results.village.
  • the contact's village attribute has been updated from its previous value to "Dertu" via an Update the Contact action.
  • The contact has exited the flow.

Did this answer your question?