Callable Journey
The Callable Journey feature lets you call another journey within a current journey enabling the execution of both the journeys (the current and the called) synchronously or asynchronously, depending on your requirements. Callable journeys are similar to regular journeys except that they are called/triggered with the help of a call/event in the actions section of another journey instead of having a typical trigger event in the same journey.
Callable Journeys are usually used to replace a common set of actions that need to be repeated in many journeys. Using a callable journey enables the user to write those actions down once and use them wherever needed. This reduces the complexity of building lengthy journeys and makes understanding easier.
Advantages:
Easy understanding: Breaks down a long journey into a series of steps and clubs the standard set of actions into a single journey. Later, call that common journey in other journeys whenever those standard sets of actions are required. Thus the complexity of length gets reduced.
Easier to test: By grouping a similar set of actions instead of calling them repeatedly, one can test a journey more precisely.
Quick sharing across journeys: By using callable, one can create journey A, say for error policy, and then call it in other journeys B, C, and D and create a centralized error notification system. This will reduce redundancies and save time for the users.
"Whenever a manager specifies the employee name on Quickwork Chat, check the employee's daily task status recorded in a designated sheet and send a message with details of the same. If the name entered is correct and the record is present, then reply with the exact number of tasks in the open, in progress, and done stages of that employee. Else, reply with a message saying that the record for the name entered could not be found.
To get this use case done, two journeys (a parent journey and a child journey) are to be built and executed asynchronously. Let's begin!
First of all, let's have a Google Sheet containing a few sample record of a few employees' daily tasks:
The name of the sheet is Daily Task Sheet. We'll be parsing this sheet and its header elements such as User, Open, InProgress, and Done to the action fields of the journey we create.
Let's configure our callable journey first so that we can call it later in our other journey.
Go to Quickwork Journey Builder and create a new journey, say Daily Tasks Callable Journey. Let's start configuring the trigger:
Search and select the Callable journey option in the App field drop-down displayed right below the New Trigger block.
Select the New Call trigger event from the Triggers list right next to the Apps drop-down menu.
In the Name field, provide the name for this journey i.e., Get daily tasks in this case. Note: Input provided in the Name field becomes the actual name of the child journey.
In the Request Type field, select application/json. Repeat the same for the Response Type field too.
Provide a sample JSON input in the Input field. E.g.,
{"User": ""}. Note: Sample JSON is a syntactical structure in which you want to get the response. For string data{"user": "A"}and for integers{"User": 1}Similarly a sample JSON output in the output field. E.g.,
{"UserFound" : "", "User" : "John", "Open" : 2, "InProgress": 1, "Done": 1}
To do so, follow these steps:
Under the Steps section, click on the Simple Action button. Choose the Google Sheets app from the drop-down menu in the App field.
Select the action, Search cell using query, from the drop-down menu in the Actions field.
For authorization, select an existing account or create a new account to authorize and connect Google Sheets. If you are not logged in to your Google Sheets account, you will be asked to do so.
Once a connection is created, the following fields will open up in which you need to enter the following details:
Select the spreadsheet, Daily Task Sheet, under the Spreadsheet drop-down field.
In the Query String field, type
Select * Where B='' This query will operate on the User column in the Google Sheets.
Specify the same sample response in the Sample response field as provided for the trigger i.e.,
{"UserFound" : "", "User" : "John", "Open" : 2, "InProgress": 1, "Done": 1}Select Sheet 1 for the Worksheet field:
To continue configuring the journey, click the + icon and click on the Business Logic button. Then, select the If Else Condition block. You'll get a tree-structured if...else block where you need to specify the if condition and configure the required actions.
In Setup If condition block, switch to the Formula mode in the Left Value field and pass the 
Select the Greater than condition from the drop-down menu in the Condition field. In the Right Value field, enter 0 as the filter keyword. Once successfully done, your If Condition block will look like the following screenshot with a heading as if rowsCount Greater then 0 then do:
The If condition we have specified here ensures the count of the rows in Google Sheets should not be 0, otherwise the journey will directly jump to the Else condition.
To configure this, follow these steps:
Choose the Callable Journey app from the drop-down menu in the App field.
Select the action, Return Response, from the drop-down menu in the Action field.
Select Success in the Response type drop-down menu field and type Yes in the User Found field.
Now pass the relevant data pills to each relevant input fields as shown in the following screenshot:
When the If condition is satisfied, the journey will execute this block and respond to the user accordingly.
If the column field value is equal to 0 i.e., there's no user record in the Google Sheet, then the action defined in this block will execute. Take a look at the following steps to configure:
Choose the Callable Journey app from the drop-down menu in the App field.
Select the action, Return Response, from the drop-down menu in the Action field.
Select Success in the Response type drop-down menu field and type No in the User Found field.
Here, you don't need to pass the relevant data pills to each relevant input field:
Once you are done configuring these actions, your child journey structure will look something like this:
Now, save and start this journey. This journey acts as a repository that you can call into other journeys without adding the same steps again and again that this journey includes.
To get the automation-ready as per our use case, we will be configuring the Quickwork Chat trigger, its action under If Else condition, and then call the child journey Get Daily Tasks.
To start configuring a Quickwork Chat trigger, you need to first create a human agent service named Demo and deploy it on a webpage successfully. Click here to know more.
Now, create the parent journey and name it as Send message on QC. To begin configuring this journey, follow the steps given below:
Choose the Quickwork Chat from the Apps drop-down menu given right below the New Trigger button.
Select the trigger event, New text message, in the Trigger Event field.
Connect Quickwork Chat by either selecting an existing connection from the drop-down or by creating a new connection. To create a new connection, follow these steps:
Click the Link Account button.
The Connect to QW Chat window will pop up. Enter the Connection Name, API Key, and the Inbox ID respectively.
Click the Link Account button. Your connection is now established.
Now click on the input of the Event field and write a name for the event whenever a new text message is received.
The journey builder will return a Webhook URL that looks somewhat like this:
https://automation.quickwork.co/staticwebhook/api/quickwork_chat/notify?Copy it. Now go to the Quickwork Chat support panel and enter the settings window or simply click here and select your inbox to edit its settings.
Navigate to the Webhook section with the help of the top navigation bar and add the webhook copied and click on the Save Changes button:
In this step, we will ask the user for the name whose record needs to be checked. For this, we will be using the Ask question action of the Quickwork Chat app:
First, choose Quickwork Chat as the app from the drop-down menu in the App field.
Now select the Ask Question action from the drop-down menu in the Action field.
In the User Question field, you need to type the question you want to ask. In our case, we can add something like:
Enter the name of the employee whose record you want to check.Now select Text as the Answer Type as we expect the answer to be in simple and plain text format.
For Conversation ID, we need to add the Conversation ID we receive in the Data Tree Output of our trigger.
The Retry help field is to show a message whenever the user enters an invalid answer. Here we can add something like
Enter a valid nameto match our use case:
This is a crucial part of the journey in terms of execution. Follow these steps:
Click on the + icon and then click on the Simple Action button to add a new simple action.
Choose the Callable Journey app from the drop-down menu in the App field.
Select the Call journey action from the drop-down menu in the Action field.
The name of the child journey we created will automatically appear in the Name drop-down menu. Select Get daily tasks. Note: Ensure the child callable journey is in the execution state. If not, the name will not appear in the drop-down list.
The execution of both the journeys should be synchronous, i.e., the parent journey will start its execution only when the child journey execution finishes. Hence, select No from the Asynchronous drop-down field.
In the Child Journey Input field, drag and drop the
key from Quickwork Chat's Ask question action output:
Using If Else condition
To progress configuring the journey, click the + icon and then click on the Business Logic button. Then select the If Else Condition block. You'll get a tree-structured if...else block where you need to specify the if condition and configure the actions.
Now, in the Left Value field, add the User Found data pill by clicking on the Callable Journey action under the Data Tree Output window on the right-hand side of the automation builder.
Select the Equals condition from the drop-down menu in the Condition field. In the Right Value field, enter Yes as the filter keyword. Once successfully done, your If Condition block will look like the following screenshot with a heading as If UserFound equals Yes then do:
Configuring Quickwork Chat action under If condition
Click on the Please choose an action bar.
Choose the Quickwork Chat from the App field drop-down menu.
Select the trigger event, Send text message, in the Action field.
In the Message field, type type the message as shown in the screenshot below and drag and drop the data pills from the Data Tree Output of the callable action as shown here:
5. In the Conversation ID field, pass the Conversation ID key from the Quickwork Chat's
New text message trigger output:
Clone the Quickwork Chat action configured under the If condition and place it under Else.
Specify No Record Found under the Message field and pass the
Conversation IDdata pill in the Conversation ID field from the Quickwork Chat's New text message trigger output:
Once you have completed configuring the actions, your complete journey will look like this:
Save your journeys and run them by clicking the Save Journey button. Now, go to the Quickwork Chat widget on your customized webpage.
Here, we will perform A/B testing to know the accuracy of the Callable Journey execution. First, we will specify a valid user name to QW Chat whose record is saved in the Google Sheets. Second, we will specify an invalid user name to see how callable journey responds.
In the Quickwork Chat window, type John as a user name. You'll get its task details as per the Google Sheets record:
To get the insights into this execution, go to the History tab of both the journeys (parent and child) and click on the latest execution statuses. Switch between input and output tabs of events and actions to get a clear idea about the flow of data from one step to another.
In the Quickwork Chat window, type Bill as a user name. You'll get a negative response as its details are unavailable in Google Sheets:
