Save Document to Table Block

Learning Objectives:

• Understand the purpose and configuration of the "Save Document to Table" block.
• Learn how to configure the Save to Table block to save documents to the correct collection and table.

Purpose of the Block:

• Is to store structured documents within a specified table in a Scout collection. This is crucial for workflows that need to save data securely and efficiently.

1. Add Save to Table Block:

• Depending on your workflow and use case this block may be placed at various points within your workflow. For this example, we will place this after the LLM block in the Basic RAG Workflow template.
  • Configuration Options:
    • Collection:
      • This field specifies the collection to save the document to. Ensure that the collection ID is correct to avoid saving data to the wrong collection.
    • Table:
      • This field specifies the table within the collection to save the document to. Ensure that the table ID is correct and exists within the desired Scout collection.
    • Values:
      • A list of values to be saved in the table. This field supports Jinja templating.
      • Lets work through an example:
        • For this example lets use the Basic RAG Workflow template and save the LLM response to a collection.
        • To save the query and response, your save block should look something like this:

• First we select the collection, then select the table to save to. Next we assigned the value type as a 'string', we then select the column in which to save to and finally using Jinja we assigned a value to be saved.
  • In this case we want the the LLM's response to be saved to the content column and the query to be saved as the title.
  • Your collection should look like this:

Micro-Challenge:

• Use the template below to practice configuring your save to table block. Make sure to populate your collection via a web scrape or by uploading documentation and remember to add the Save to Table block.
  • Save to Table Playground: Basic RAG Workflow template