Data masking

Understanding the Quickwork Journey Builder. Quickwork is a no-code, API-based SaaS platform with pre-integrated apps to automate business and consumer workflows.

Quickwork Journey Builder stores complete data flow within every journey trigger and step(s). In certain use cases, there are long trails of sensitive information of users or customers such as IDs, SSNs, DOBs, etc. which should be prohibited to Quickwork admins who are executing the journey.

Data masking enables users to disable the display of I/O data at the trigger and step level. The masked data of a trigger or a particular action step does not get stored in the execution history of a journey.

Enable trigger data masking

Quickwork's triggers, both real-time and polling, are capable enough to capture incoming events precisely and kick start a journey. While listening for incoming events, there are various confidential information and sensitive data that rush through and pass to the further steps defined in a journey. Quickwork Journey Builder has thus provided a provision to mask such crucial data at each entry-point so that it remains invisible in the output state.

To mask trigger data, click the horizontal ellipses on the trigger bar and toggle On the Mask option. In this case, the Gmail trigger has been masked:

Figure 1: Masking trigger data

Now, whenever the journey executes successfully, the data flows completely between trigger and actions. However, the trigger I/O data cannot be seen in the History section:

Figure 2: Masked trigger I/O data

Enable step data masking

Data can be masked for all action steps of a journey depending on your data security policy requirements. To disable the action step I/O data in the execution history, click the horizontal ellipses on the step bar and toggle On the Mask option. In this case, the Google Sheets action has been masked:

Figure 3: Masking an action data

The following image shows the execution history before the action data being masked:

Figure 4: Unmasked action step's I/O data

The following image shows the execution history after the action data being masked:

Figure 5: Masked steps I/O data