Data masking

Secure the confidential information flowing through a journey in Quickwork. This feature hides the action data of workflow automation in the transaction report storing no data in memory.

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

Data masking enables users to disable the storage and display of I/O data at the step level. A particular action step does not get stored in the execution history of a journey if mask data is enabled.

Enable step data masking

Data can be masked for all action steps of a journey as per your requirements. To disable the action step I/O data in the execution history, hover on the step bar and click the Data Masking button to turn it ON. In this case, the Google Sheets action has been masked:

Figure 3: Data masking

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

Figure 4: Action's I/O data masked

Copying the JSON data from the Input and Output tab and pasting it in any editor of your choice won't show you the data passed in the journey. Since the Data Masking button is enabled, it will return the following message in the editor:

{
  "data": "masked"
}

To turn OFF the data masking option, hover again on the step bar and click the Data Masking button. Everything will restore to normal.