Semogram Docs
PluginsTransforms reference

pivot

Configure pivot parameters, input/output bindings and lineage.

Turn row values into columns within grouped outputs.

Install

Install the Transforms bundle, then select the pivot capability on a pipeline transform node. Runtime entrypoint: transforms/pivot.ts. The installed capability must be enabled and pass preflight.

Configure

Execution: deterministic. Declared runtime support: supported.

Parameters

FieldTypeRequiredDetails
groupByarrayNoFields that stay fixed while values pivot into columns. Items: string.
keyFieldstringNoField whose values become output column names.
valueFieldstringNoField whose values populate the pivoted columns.
fillValuenumberNoOptional numeric value used when a pivoted cell is missing.

View the complete contract for nested parameter shapes, defaults, named bindings and lineage.

Bindings

  • Input in: Input (required)
  • Output out: Output

Verify the result

Create a small input with known values that exercise pivot and supply the required parameters above. Validate, save and run the pipeline. Inspect the output records and compare row counts and changed fields with the input. Check the run’s errors and evidence before accepting a conversational summary.

Include empty inputs, missing values and relevant duplicate or multi-match cases so the intended behavior is clear.

Lineage and changes

Lineage mode: explicit. This operation can change row membership or combine records. Its explicit lineage must map output records to their contributing inputs; check those links after the run.

Changing parameters changes the computation. Review the saved pipeline revision before rerunning it. Publishing a new plugin version and editing node parameters are different changes.

FAQ

Why does validation fail?

Check required parameters, the installed capability version, runtime support and the named input/output bindings. A missing nested field may be visible only in the full contract.

Is this a standalone MCP tool?

It is a plugin capability used by a pipeline, not a new top-level MCP tool with this operation name. An assistant can inspect, validate and execute the pipeline through the MCP reference.