CSV source

Reads people or companies from a CSV file. The header row names the fields; columns maps the rest onto canonical names.

Connector	`csv/source`
Role	source
Records	person
Tier	built in
Credential	none
Cost	unset in the manifest; `gtme plan` prints what the step declares at run time
Source	internal/adapters

Use it

It ships inside the binary. In a pipeline file:

source:
  use: csv/source
  with:
    path: PATH

Replace the placeholder:

PATH: cSV file to read; header row names the fields

gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.

Needs

Nothing. A source starts the pipeline.

Provides

Whatever the input names. Fields that match canonical names map onto them.

Config

Key	Type	What it does
`path` required	string	CSV file to read; header row names the fields
`entity_type`	person \| company
`limit`	integer
`columns`	object	Ingress mapping (ADR-018): canonical field name → CSV header as written. Headers already matching canonical names auto-map; unmapped non-canonical headers become csv.<normalized_header>.

On this page, connector means what gtme calls an adapter. This one is a process adapter compiled into the binary. Two adapter tiers explains the difference.