Quickwork Glossary

App

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.

Action

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.

API Management

API Management allows you to create API collections and endpoints. Using the collection and endpoints, you can create API calls that execute callable journeys in the backend with just one click.

Audit Logs

The Audit Logs section maintains records of each activity a user performs in Quickwork, regardless of a free or a paid user. Through audit logs, a user gets the ability to view and track all the operations performed on various components such as journey, folder, connection, and Team. The user can also view details of the user's login/out from the account. All these details are recorded with the name of a user, time, the IP address of a system, and browser details through which the user accessed the Quickwork account.

Business Logic

The condition 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 supports five Business Logic features:

• If Condition
• If Else Condition
• Foreach Loop
• Stop Journey
• Try Catch

Callable Journey

Callable Journey 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.

Constants

Constants are user-defined parameters that are accessible for all the journeys account-wide. These are JSON-like name-value pairs that are customizable as per the users' choice eliminating the manual efforts to specify the same input again and again.

Connection

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 permission is granted, Quickwork will perform the defined task on your behalf. For example, if you have chosen the Gmail app in your journey, you need to first log in to your Gmail account and then allow Quickwork to access the Gmail scopes with read/write permissions.

Some apps need access 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.

Customized Transaction Table

A Transaction Report can be customized in the form of key-value pairs to show crucial information about the journey transaction instantly. The Customized Transaction Table feature lets you create a column for each I/O recorded in the journey transaction, pair it with a respective value of your choice, and get it displayed on the History tab.

Data Tree Output

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. The data pills and their values differ for each app configured in a trigger or action(s). These data pills are intended to be used as an input value for the actions down the line, specifically when providing input to an input field is complex.

Data pills

Data pills are elements of the app data tree. They represent each application’s output that can be used in subsequent steps to pass data from one app to another.

Databases

Databases help to store self-created rows and columns with custom data filled as per business requirements. These rows and columns are stored in a collection. A collection is referred to as a cross-reference table that allows you to look up (search) for the most frequently used data in a journey. 

Folders

Folders are virtual storage locations in which multiple user-created journeys are stored in a well-organized manner.

A folder stores all your configured journeys in one place. In case you have journeys that are related and can be grouped together, you can create a folder with a unique group name and save the journeys in that folder. The configuration-related information of each journey gets automatically saved in its respective folder.

Input Fields

Input Fields are form fields that are part of a trigger or action. These allow users to populate data that they wish to pass to the application. The data can be in the form of a string, number, JSON, Boolean, decimal, date, and a few other supported formats. You can fill up a field by entering a hardcoded value or dynamically by using data pills.

Journey Configuration Manager 

Clicking on the Create Journey button on the Folders window will open up the Journey Configuration Manager.

Journey

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 or complex journeys as per your use case by using the apps we support.

Logger

Logger allows you to record the output of triggers and actions while a journey is in the execution state. This feature is useful to visualize the complete set of data flowing between each action through which you can debug the journey process, in case of unexpected results. You can also backtrack to each action step where you believe that a small tweak in the inputs would give you better results.

Step

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.

Trigger

A trigger is an event or an occurrence that kick-starts step(s) configured 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. 

Team

Working in collaboration with other team members not only helps to achieve targets in time but also helps to solve issues effectively. With the help of the Team feature, users can invite their colleagues, partners, and customers to collaborate to build journeys by assigning roles as per the business requirements.

Transaction

A complete end-to-end flow of a journey is regarded as one transaction. Each time a journey is triggered, it is considered as one transaction even if a journey fails, succeeds, or remains in a pending state—no matter how many steps you have in any given journey.

For example, you have a journey that fetches a message from Facebook Messenger and forwards it as an email to a Gmail account. Right from listening to messages on Facebook Messenger to sending each of them as an individual email, the complete journey execution counts as one transaction. Quickwork allots you the transactional credits as per the plan you have opted for.