What format is the output?

A `data` file of rows. Serialization is unspecified. Do not assume JSON or CSV.

Can this join or aggregate datasets?

No. One dataset in, one file out. Joins and aggregation are not in the contract.

`solution` and `dataset`. `query`, `columns`, `order-by`, and `workspace` are optional. `workspace` defaults to the workspace that contains the workflow.

What does the `workspace` input do?

It scopes where the module looks for the solution. By default it reads the workspace that contains the workflow using this module. Set it when the solution lives in a different workspace you can reach; a workspace you cannot reach produces no rows.

2026-08-13

Utilities

Get Data from Dataset

Pull rows from a Solution dataset into a file for downstream Library nodes. Required: solution and dataset. Query, columns, order-by, and workspace are optional.

What Get Data from Dataset does

Workflows often need rows that already live in a Solution dataset, not on disk. This module reads those rows into a data file the rest of the workflow can consume, so a hostname list, a target list, or any other dataset becomes a wired input without a manual export. The query language is unnamed in the source of truth; syntax lives on the node, not on this page. It is not a warehouse and not a scanner; it reads and writes, and it does not join, aggregate, or transform.

You read rows from a Solution dataset you already have and write them to a data file for later Library nodes. The query language is unnamed. Syntax lives on the node. It is not a warehouse and not a scanner.

Where it fits in the pipeline

Illustrative excerpt. Each node is a Trickest module.

Upstream

A Solution dataset you can reach. That dataset is not a Library module.

Downstream

Any Library node that takes a generic list file: hostname enumerators, Probe for Web Servers, Scan for Open Ports.

Parallel

Get Cookies via Puppeteer Recording is the other thin Utilities leaf. Different job. This does not sit on the network or web tail. It feeds a file into either.

When to use this

Nest this when a downstream node needs rows that live in a Solution dataset and are not already a workflow file. Skip it when the list is already on disk, or when you wanted a query console rather than an in-workflow read.

Inputs and outputs

Required: solution (STRING): the solution to retrieve data from.
dataset (STRING): the dataset to retrieve data from.
Optional: query (STRING): query to filter the data by. Syntax lives on the node.
columns (STRING): columns to include in the output.
order-by (STRING): columns to sort the data by.
workspace (STRING): the solution's workspace name. Default: the workspace
data: a file of rows from that dataset. Row serialization is unspecified.

Data

The tables this module produces. Sample rows are illustrative.

dataset-rows3 columns · 3 sample rows

Rows read from the source Solution dataset and written to the data file.

	idtext	valuetext	metadatajson
1	host-001	app.example.com	{2}
2	host-002	staging.example.com	{2}
3	host-003	api.example.com	{2}

How it differs from similar modules

Warehouse / SQL export

Why this is not it

You read one Solution dataset into a workflow file. Not a warehouse. The query language is unnamed.

Live Tables

Why this is not it

A different platform surface. This module writes a file for downstream nodes. It does not replace that console.

questions