Parsing Files with OneTrust Workflows

You can configure OneTrust integrations with Parsing File actions to read a file and retrieve a specific list of items. This parsing allows each identified row to become an element in an array of JSON objects which can then be referenced in logic steps, such as Apply to Each, later in the flow.

Note:

This is currently a preview feature. Contact your account executive to have it enabled for your environment.

Supported File Types

OneTrust supports most to any delimited text files for parsing. To inquire about support for specific file types, please contact your account executive or OneTrust Support.

To create a parsing file action

  1. On the Integrations menu, select Integrations.

    The Integrations screen appears.

  2. Click on the name of an existing integration or create a new workflow.
    Note:

    For more information on creating new workflows, see Creating Integrations.

    The Integration Builder screen appears.

  3. In the Add OneTrust Trigger section, there should be an initial action that provides a file reference or a trigger, such as a webhook, that allows the passing of a file to the integration created here.
  4. After this initial action, click the Add Action button.
  5. Click the Logic tab, then select Parse File to List.


  6. Enable one of the following settings:

    Setting

    Action Taken

    Parse file up to 10 MB in size

    The action will parse a file up to 10 MB in size. The output is a list so it can be referenced in future actions in the workflow.

    Parse large file and send chunks to subflow

    This use case allows parsing files larger than 10MB to another subflow to prevent timeout when processing large files. This is different than the standard parse to list option where you can group the data in smaller batches and build processing with a subflow.

    With this option, two additional fields will populate:

    • For Select Subflow, select an existing subflow to handle the batch processing. This subflow can be referenced in future actions in the workflow.

    • For Lines per Subflow, the number input will default to 1000 but supports a range of 100 to 10,000.
  7. In the File Reference field, select the desired file property from a prior action or from a given event payload.
    Note:

    This action supports parsing text or CSV files up to 10MB in size.

  8. Enter the number of row(s) to exclude from processing. Enter 1 to exclude the header row.
  9. Select which character should separate columns in the file. Only one delimiter can be used at this time. Available delimiters:

    • Comma

    • Semicolon

    • Space

    • Tab

    • Other

      Note:

      Selecting this option will populate the Enter Other Delimiter field for you to enter your desired delimiter. You can only enter one character.

  10. Enter the column names in the order in which they should appear in the file. You can check Ignore to pass any irrelevant column(s), and use the plus icon button to add additional columns.
    Note:

    Click the Upload Sample button to import a file to auto-generate column names. The file needs to contain a header row. This will override any existing column names.

  11. Click the Done button.


  12. Click the Save button for the workflow, then click the Activate button.
  13. This parsing step can then be referenced in an Apply To Each to act upon the following step in the logic sequence. The API will call for each element in the array that is produced from the Parse File to List action.

    If you selected the second parse file to subflow option, this logic would go inside the subflow to handle the batch processing.