Previewer enhancements & HTTP Call node name change

Release Summary

This release focused on enhancing the flow Previewer (a.k.a. the emulator) to provide flow-builders with a powerful tool to view and test their flows and get a real feel for their end-users' experience. We've also updated the name of our HTTP Call node to be the more descriptive API Integration node.

Node name change

We renamed the HTTP Call node to API Integration so that the name is more descriptive and accurate to the node's function, and so it better aligns with the existing "API Integration" section.

Emulator (previewer) enhancements

Test your current flow without a route

Previously, as a flow-builder, you first had to configure a route in the Routing section before you could preview your current workflow on the emulator. We've removed this unnecessary step and now allow you, once you've saved the flow, to preview it in the emulator immediately, without having to set up a route first. This makes it quicker and easier to test the flow you are currently working on.

Once you click Preview, the selected route in the emulator defaults to "This Flow". You can simply add a mobile number and click "Start". You can also select another route from the drop-down if you want to test something else. This changes the flow structure visible on the canvas so that the emulator and canvas are always in sync.

Focus on the current node and highlight the execution path

Previously, the workflow that you were testing and the emulator you were testing on, were completely separate. This meant that, when you spotted something on the emulator that you wanted to edit or fix in the workflow, you had to scroll through the whole flow in search of the particular step or node you wanted to adjust.

With this release, we've made the canvas more 'dynamic' so that what you see on the canvas and what you see on the emulator are more in sync.

As you move through the flow's steps on the emulator, the flow structure on the canvas moves with it, keeping the current step in focus at the center of the canvas. The path taken based on the end-user's input and menu option selections will be highlighted with the untaken path slightly greyed out.

This helps you with visual indicators to understand the flow behavior better and to troubleshoot and fix your flows easier.​​​​​​​

Execution Logs

The Execution Logs assist you to gather insight about and troubleshoot your flows.

When previewing your flow on the emulator, you can select the 'Logs' button in the bottom left of the canvas. This opens a panel with detailed information about how the flow was executed in this session.

The following tabs are available:

• Logs - Displays every step, action, input, output, and action that was executed.

• Keywords - Shows all keywords that were used during the session, including their destination.

• API Calls - Indicates all the API calls made during the session. You can deep-dive into the API call details, viewing the API Request, API Response, and the variables within the API payload.

• Variables - Presents you with all the variables that are available to use in the session, and what was entered by the end-user as inputs.