Merge data

​

Purpose

• Create a final, clean data structure at the end of a workflow.
• Merge data from an initial input (e.g., an id from an Open datasets block) with data extracted from a webpage (e.g., a title from an Extract Data block).
• Combine results from multiple, separate Extract Data blocks into a single, cohesive output.
• Select only the necessary fields from a larger set of available variables for the final result.

​

Configuration

1. What information should we combine?
   • This choice determines the structure of your final output.
   • A list of items: Use this if you are processing a list and want each merged item to be a separate row in the final results.
   • A single item: Use this if you are combining data for a single entity into one result row.
2. Defining Attributes (The Data Table):
   • You will define the structure of your final output in a table-like interface.
   • NAME (Column 1): This is the name of the variable you want to include in the final output. The agent will look for an existing variable with this exact, case-sensitive name in the data available from all preceding steps.
   • EXAMPLE VALUE (Column 2): This field is typically left empty, as the block uses existing data. However, you can use it to provide notes or examples for clarity if needed. The primary mechanism is matching the NAME to an existing variable.

Screenshot: Merge data block configuration panel showing the item type selection and attributes table with 'title' and 'id'

​

How It Works

1. Place the Merge data block at a point in your workflow where all the data you want to merge is available. This is often at the end of an iteration loop or as the final step of the entire workflow.
2. Define the desired output schema by listing the NAME of each variable you want to include.
3. When the workflow runs, this block gathers the values of the variables from the preceding steps that match the names you’ve listed.
4. It then creates a new, single result (or a list of results) containing only the fields you specified, effectively merging them into one clean structure.

​

Example: Merging Input Data with Extracted Data

1. Open datasets Block:
   • Contains two columns: URL (e.g., https://example.com/product/123) and id (e.g., 123).
2. Extract Data Block (added next):
   • This block runs on each URL from the dataset.
   • It is configured to extract one attribute:
     • NAME: title, DESCRIPTION: The main title of the product.
3. Merge data Block (added next):
   • What information…?: A single item (since we are creating one final row per product).
   • Attributes:

     NAME	EXAMPLE VALUE
     title
     id

• Result: The final output will be a table with two columns, “title” and “id”. For each product, the title will be taken from the Extract Data step, and the id will be taken from the initial Open datasets step, perfectly merging them into a single, clean result row.

​

Key Considerations

• Data Reorganization, Not Extraction: This block’s purpose is to structure and combine existing data, not to extract new data from a source.
• Variable Name Matching: The block relies on exact, case-sensitive matching between the NAME you provide in its table and the names of variables available from previous steps.
• Workflow Placement: This block is most effective when placed at the end of a processing sequence to consolidate all gathered information into a final, desired format.