With long, involved workflows, authors may want to allow end-users to complete the entire workflow in separate sessions. So an end-user could start using the workflow, go to lunch, and reopen the workflow at a later time and finish the session. The state of the workflow is saved at all times.

To make this work, the URL that opens the workflow needs to have a unique identifier attached to it, in the session_id parameter of the URL. So when you launch the workflow, you will need to provide this parameter. And when the end-user relaunches the workflow, the same URL needs to be used.  

Important: The session_id needs to be unique across all Zingtree customers and sessions.

For example, if your URL is this:

https://zingtree.com/live/141123244

You would create a unique session ID (like 141112232-xyz), and launch the URL like this:

https://zingtree.com/live/141123244?session_id=141112232-xyz

Please Note: In order for Pause and Resume to work properly, the workflow ID must be the same in both the initial URL and the resumed URL.

Resuming a Session from a Different Node

You can move a session to a new node by simulating a click on the tree. You need to provide some "click text" as if a button was clicked, and a new node number where the session will resume. The click text will appear in the session history and button click reporting.

For example, to move a session to node #99, as if a button named "Next" was clicked, you would add this to the URL along with the session ID:

&click_text=Next&next_node=99

Note that any spaces in the click text need to be replaced with + .

• Integrations: Adding Agent Scripts into any CRM
• How to Email a Link to Resume a workflow Session