csv/deliver

Built-in deliver adapter for person records: its manifest, needs, provides, config keys, cost, and an example step

What you'll learn

You're about to put csv/deliver in a step and want its keys, fields, credentials, and cost before plan tells you.

what the adapter needs and provides
every with: key it accepts
what it costs and which credential it demands

A built-in deliver adapter for person records: it needs the step's uses: fields and declares no fields of its own. Plan prices it at $0 per record, and it demands no credential.

Manifest

Key	Value
id	`csv/deliver`
version	1
role	deliver
entity type	person
credentials	none
cost estimate per record	$0

Needs

The fields the step's uses: line names, and nothing else.

Provides

Nothing; a delivery row is what it writes.

Config keys

The keys with: accepts. Plan rejects any other key.

Key	Type	Required	What it sets
`entity_type`	string
`path`	string	yes	CSV file to write; created with a header, appended across runs
`variables`	object		Egress mapping, injected by the runner from the step-level variables: key. Its targets are the columns.

Example

From Your CSV:

  - id: out
    use: csv/deliver
    with:
      path: out.csv
    variables:
      first_line: first_line
      ps_line: ps_line
    idempotency: email

Used in

The persona-file-and-text-compose example in gtme help --agent