Key concepts & Terminology

Folders

Folders are virtual locations for organizing multiple user-created journeys. Each folder can group related journeys under a unique name, and each journey's configuration details are saved within its respective folder.

Journey

A journey is an automated workflow consisting of logically connected steps designed to automate a task. For example, creating a new task in JIRA and sending its details via email using Gmail is a journey. Journeys can be simple or complex, depending on the use case and the apps involved.

Connector

A connector is an app. When creating a workflow or journey, you can use a connector (app) to interact with data, events, and resources across different apps, services, and systems without the need to code. In a connector, each operation can act as either a trigger that initiates a journey or an action that performs a particular task. While many connectors have both triggers and actions, some connectors offer only triggers, while others provide only actions.

The various operations related to Google Tasks connector (app) include both triggers and actions that can be utilized within a journey:

• Triggers
  • Task completed: Activates when a specific task is marked as completed in Google Tasks.
  • New task: Triggers when a new task is added to Google Tasks.
• Actions
  • List tasklist: Retrieves a complete list of all task lists available in Google Tasks.
  • Find task: Searches for a specific task within Google Tasks.
  • Update task: Allows for modifications to an existing task in Google Tasks.
  • Delete task: Removes a specific task from Google Tasks.

Connections

A connection links Quickwork and the third-party app used in the journey. Creating a connection involves granting Quickwork permission to access information from third-party apps used in a journey, after which it performs the defined task on your behalf. For example, to use the Gmail app, you must log in to your Gmail account and allow Quickwork to access the necessary Gmail scopes with read/write permissions. Some apps require access tokens or API keys to establish a connection. Quickwork provides easy steps for each app in the connection window to help users connect their apps efficiently.

App

An app refers to an application (connector), service, or system integrated with Quickwork. Apps can perform trigger events, execute steps, or carry out multiple logical operations to fulfill workflow objectives.

Explore the App directory for a complete list of third-party apps supported for integration.

Step

Step refers to a segment within a journey that performs a specific function. Each step can be categorized as either a Simple Action or Business Logic depending on the complexity and the functionalities it involves.

Trigger

A trigger is an event or occurrence that initiates the execution of a journey. For example, if your journey is "Whenever a new task is created in your JIRA account, send its details via email using your Gmail account" then the first part, "Whenever a new task is created in your JIRA account," is the trigger. You can configure only one trigger for a journey.

Action

An Action is a step within a journey that performs a specific task in response to a trigger event.

Example: If your journey is: Whenever a new task is created in JIRA, send its details via Gmail, the action is 'send its details via Gmail'.

Business logic

Business Logic is a feature that adds precision to a journey by adding filters between triggers and actions or between different actions. This ensures that the journey proceeds only when certain specified criteria are met, resulting in a more targeted and effective outcome. Quickwork currently supports five Business logic types-If condition , Foreach loop, If else condition, Stop journey, and Try-catch.

Input fields

Input fields form input elements within a trigger or action. They allow users to enter data in various formats, such as string, number, JSON, boolean, decimal, or date. Fields can be hard coded or can be populated dynamically using data pills.

Data tree output

Data tree output compiles all the output data pills from the configured trigger and actions. This includes identifiers, version numbers, date and time stamps, snippets, and other essential information. Data pills vary with each configured app and are intended for use as inputs in subsequent actions.

Data pills

Data pills are elements of the app data tree representing each application’s output. They facilitate data transfer from one app to another in a journey.

History

The History feature provides a detailed view of the execution history of your journey, enabling you to track and review past activities and outcomes. This feature helps monitor the performance and effectiveness of automated workflows.

Transaction

In Quickwork, an end-to-end journey is considered one transaction, regardless of its outcome or the number of steps involved. For example, fetching messages from Facebook Messenger and forwarding them to a Gmail account counts as one transaction. Transactional credits are allocated based on your plan.

Data masking

Data masking is a security feature designed to protect confidential information within a journey. It allows you to hide sensitive input/output data at the action steps, ensuring that details such as IDs, SSNs, passwords, and email addresses are not stored or displayed in the transaction report or execution history. This feature is particularly useful when sensitive data trails need to be shielded from those executing the journey.

Versions

Versions track the history of changes made to a journey, allowing you to view modifications and revert to specific versions if needed. Each time a change is made and successfully saved, a unique version ID is created, providing a reliable way to manage and backtrack changes without starting from scratch.

API management

The API Management tool enables you to create and manage APIs for callable journeys. These APIs can be executed via a single API call. It supports the full API lifecycle, including creation, deployment, security, and monitoring, facilitating smooth data transfer across apps and cloud environments.

Constants

Constants are customizable, user-defined parameters accessible across all journeys. They are structured as JSON-like name-value pairs, simplifying the process by eliminating repetitive manual inputs.

Conversation management

The tool Conversation Management is an in-house messaging plaform that enabes creating and managing real-time messaging workflows across multiple channels like WhatsApp, Facebook Messenger, Slack, and more. Features include real-time triggers, context handling, NLP support, analytics, and seamless handover to human agents.

Databases

Databases by Quickwork is an in-house database that organizes, stores, and manages data across collections (commonly called tables), allowing for efficient data retrieval, modification, and management.

Dashboard

The Dashboard tab is a centralized interface to access comprehensive insights and reports about your activities. It includes an Analytics section with journey utilization reports, Dependency Graph to visualize the input and output relationships of a specific Quickwork resource, and Audit Logs which can be tailored to display information for a custom date range. You can monitor performance, review actions, analyze the efficiency of your workflows within specified periods, and get a detailed and customizable overview of system usage and interactions.

Audit logs

Audit logs provide a detailed record of activities within your Quickwork account, capturing interactions with journeys, folders, connections, and team activities. These logs include timestamps for each event, offering insights into the productivity and usage patterns of your resources. They are a valuable tool for monitoring and reviewing account activities to ensure compliance and operational integrity.

Dependency graph

The Dependency Graph provides a visual representation of how a selected Quickwork resource, such as a journey, constant, API interacts with other components in the system. It helps identify input and output relationships, making it easier to understand dependencies across connected assets.

Team

The team feature facilitates collaboration by allowing you to invite colleagues, partners, and customers to build journeys together and assign roles based on business needs.