Skip to content
Nappai Documentation

Runnable Data Batch

Runnable Data Batch is a simple tool that lets you feed a list of data into a series of automated actions (called runnables) and get back the same data with the actions applied. Think of it as a “batch runner” that processes many items at once without you having to set up a separate workflow for each one.

How it Works

When you drop this component into your dashboard, you provide it with:

  1. Data – the list of items you want to process.
  2. Runnables – a set of actions that should be performed on each item.
  3. Optional settings that control how the data is split and how results are stored.

The component loops over every item in the data list, passes it to each runnable in the order you defined, and collects the results. After all items have been processed, it returns the updated data set, ready to be used by the next component in your workflow.

Inputs

  • Data: The data you want to process. It can be a single record or a list of records.
  • Runnables: A list of runnables that will be executed on each data item.
  • Check if value is array: If set to True, the component will check whether the value you provide is already an array. If it isn’t, it will split the value into an array using the separator you specify.
  • Separator for array: The character or string that separates items when the component splits a string into an array (e.g., a comma, semicolon, or newline).
  • Additional context: A string that will be appended to the context for each runnable. For example, if you set it to “Search for: {input}”, the runnable will receive a context that includes that phrase with the current input value inserted.
  • Input Key: The key name in the data that should be passed to the runnables. This tells the component which part of each data item to feed into the actions.
  • Data result Key: The key under which the processed result will be stored in the data. After the runnables finish, the output will be added to each data item under this key.
  • Output Key from runnables: The key that identifies the output produced by the runnables. This is used to pull the result from each runnable’s response.

Outputs

  • Data: The original data list, now enriched or modified by the runnables. The output is produced by the component’s process_data method and can be fed directly into the next component in your workflow.

Usage Example

Suppose you have a list of customer records and you want to:

  1. Look up each customer’s latest order.

  2. Calculate a loyalty score.

  3. Add a note if the customer has a pending issue.

  4. Add the Runnable Data Batch component to your dashboard.

  5. Configure the inputs:

    • Data: Connect the output of your “Customer List” component.
    • Runnables: Add three runnables – “Get Latest Order”, “Calculate Loyalty Score”, and “Check Pending Issues”.
    • Check if value is array: Leave as False (your data is already an array).
    • Separator for array: Leave blank.
    • Additional context: “Customer ID: {input}”.
    • Input Key: “customer_id”.
    • Data result Key: “processed_info”.
    • Output Key from runnables: “runnable_output”.

  6. Run the workflow. Each customer record will be processed by the three runnables, and the enriched data will appear under the processed_info key in the output.

You can then connect the output to a “Data Export” component to save the results or to a “Notification” component to alert staff about customers with pending issues.

  • Runnable – The individual action that can be added to the Runnables list.
  • Data Processor – A component that performs transformations on data without running external runnables.
  • Data Export – Sends processed data to a database, spreadsheet, or file.

Tips and Best Practices

  • Keep the Separator for array consistent with the format of your input data.
  • Use Check if value is array only when you’re unsure if the input is already a list.
  • Add descriptive Additional context strings to help runnables understand what they’re working on.
  • Store results in a clear Data result Key so downstream components can easily find the processed information.
  • Test the component with a small sample of data before running it on large batches to catch any errors early.

Security Considerations

  • Runnables can execute code or access external services. Only add runnables from trusted sources.
  • Review the permissions granted to each runnable to ensure they only access the data they need.
  • If your data contains sensitive information, consider encrypting it before passing it to runnables or limiting the runnables’ access to the minimum required fields.