To understand the functionality of Quickwork Journey Builder, it is crucial to know its terminology. Don't worry; these terminologies are very easy to deal with. It's just a nomenclature through which the components of the tool are being addressed. So, let's dig deeper into this document and know what the tool has.
A folder stores all your configured journeys in one place. In case you have similar-featured journeys and want them to be distinguished, you can create n number of folders and save the journeys accordingly. Also, the configuration related information of the journey gets automatically saved in its folder.
Click here and know more about folders.
An app is a popular acronym for 'application'. In our context, an app is an application, service, or system integrated with or being used on our platform. An app can perform multiple logical operations or steps and trigger events to meet the objective for which it was created. Refer to the App directory page on our website to see a list of third-party apps we support for integration.
A step is a logical operation that performs an action within an app. The action can be one of the four types: create, read, update and delete.
A journey consists of a set of steps that are connected logically to meet an objective. It is a set of steps configured to automate your task. For example, create a new task in JIRA and send its details via email using Gmail. You can create more simple and complex journeys—as per your use case—by using the appswe support.
Once you are clear with the terminology, refer to our step-by-step guide for creating your first journey.
A trigger is an event or an occurrence that kick-starts a set of steps in a journey. It is a mechanism that initiates the execution of a journey. For example, if your journey is "Whenever a new task is created in your JIRA account then send its details via email using your Gmail account", then the first part, i.e., "Whenever a new task is created in your JIRA account" is your trigger. You can configure only one trigger for a journey.
Refer to the Triggers guide to understand better.
An action is a set of user-defined steps that performs a task whenever a trigger event occurs. Referring to the journey use case discussed in the Trigger section, the last part, "send its details via email using your Gmail account" is an action. You can add one or more actions while setting up a journey.
Each app has several actions that you can use. For example, the Google Task service that we support has actions such as Create Task, Create Tasklist, Delete Task, Delete Tasklist, etc. Click here to know more about action.
Data Tree Output is a collection of all the output data pills of a configured trigger and actions. The output data values such as identifiers, version numbers, date and time stamps, snippets, and other crucial information that users find difficult to remember are grouped in this tree. However, the data pills and their values differ for each app configured in a trigger or action.
These data pills are intended to be used as an input value for the following actions down the line, especially where providing an input to an input field is complex:
Simply drag and drop the data pill in the input field. A help text is provided beneath the input field whenever a data pill needs to be used in an input field.
Creating an app connection is a process of granting permission to Quickwork to access information of the third-party apps used in a journey. Once granted, Quickwork will perform the defined task on your behalf, achieving complete automation. For example, if you have chosen the Gmail app in your journey, you need to first login to your Gmail account and then allow Quickwork to access the Gmail scopes with read/write permissions.
Some apps need access to tokens or API keys to establish a connection with Quickwork. To get these credentials easily, Quickwork has defined the steps for each app in the connection window. Just follow these steps and get your app connected. To understand the app connection steps in detail, visit the App Resources section on our Helpdesk.
Also, click here to know more about the connection.
The conditioning feature brings granularity to a journey. It lets you add filter conditions between trigger and action or action and action so that the data you receive is a fine-tuned output. Specify a condition between actions, and a journey executes only when a condition gets satisfied. Quickwork Journey Builder supports five conditioning features:
Explore these documents and build smarter automations.