Data masking

Workato job history stores data going in and out of every recipe step. In certain use cases there may be sensitive information for example, employee SSN, date of birth, etc. that should not be visible to Workato account admins.

Data masking enables users to disable display of data at the trigger and step level - users can control display of job history data at every step.

Data masking is only available for certain users. Reach out to your Customer Success Manager to learn more.

Data masking and data storage

Trigger and action steps

When a trigger or action step is masked, input, and output data is not stored by Workato.

The Input and Output tabs for a trigger or action step do not display the data in the UI when you enable data masking.

However, the trigger event data is stored by Workato. The trigger event data is used to repeat a job. Trigger event data is distinct from job details data such as the trigger and step input and output data. Trigger event data represents information required to repeat a job.

Activity audit log

Input and output data aren't included in your Activity audit log or streamed to your Audit log streaming destination when you mask a trigger or action step. Workato uses a placeholder step in the audit log instead of the trigger or action data.

Enable data masking

Data can be masked for individual recipe steps, and both input and output data display will be disabled in the job history. To turn off display of this data as part of job history, you will need to check the Enable data masking field, found under the Comment section for each recipe step.

The following shows enabled data masking for the Salesforce New/Updated Account trigger.

Enabling data masking. Example recipe (opens new window)

The following shows job history before data masking.

Job detail before masking. Example recipe (opens new window)

The following shows job history after data masking.

Job details after masking. Example recipe (opens new window)