WhoDB PlatformDocs

Transform node reference

Where: Transforms → open a graph → Library. Choose a node for the operation it performs, then click the added node to configure it.

The node library is the starting point for extending a transform.The node library is the starting point for extending a transform.

The node library is the starting point for extending a transform.The node library is the starting point for extending a transform.

The node library is the starting point for extending a transform.

NodeWhat it doesDetailed instructions
SourceReads a connected database/service objectInput nodes
SeedEmits inline rows or pasted CSVInput nodes
FileReads one project file or a folder selectionInput nodes
DatasetReads a project datasetInput nodes
Ontology (entity)Reads managed entity recordsInput nodes
SelectKeeps or drops columnsColumns and filters
FilterKeeps matching rowsColumns and filters
ConditionSplits matching and nonmatching rows into branchesColumns and filters
RenameChanges output column namesColumns and filters
FormulaAdds or replaces computed columnsColumns and filters
AggregateGroups rows and computes measuresCombine and summarize
SortOrders rows by one or more keysCombine and summarize
LimitKeeps first N rows or a random sampleCombine and summarize
DeduplicateRemoves duplicate rows by selected keysCombine and summarize
JoinCombines two streams on matching keysCombine and summarize
UnionStacks compatible input streamsCombine and summarize
OCRExtracts text from document/image inputsAI and OCR
AIProduces structured fields using a configured modelAI and OCR
ScriptRuns custom row-processing codeScripts and functions
FunctionInvokes a configured ontology functionScripts and functions
OutputWrites to a dataset or entityOutput mapping

Read a configuration panel#

The selected node shows its input and output summary. Finish required selections before interpreting a downstream error. Changing an upstream selection can change the columns available downstream. Recheck formulas, join keys, and output mappings after a source schema change.

Ready describes the node's current configuration state, not a guarantee that an external runtime, provider, or destination will succeed. Use Preview, then a controlled run, and inspect the destination independently.

Was this page helpful?