http/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 http/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. It publishes no per-record estimate, so plan prints ?, and it demands no credential.

Manifest

Key	Value
id	`http/deliver`
version	1
role	deliver
entity type	person
credentials	none
cost estimate per record	not published

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
`auth`	object
`auth.env`	string	yes
`auth.name`	string
`auth.prefix`	string
`auth.type`	one of header, query, bearer, basic	yes
`body`	any		Body template; default is the resolved variables object
`entity_type`	string
`headers`	object
`keep_payloads`	boolean
`method`	one of POST, PUT, PATCH		Default POST
`query`	object
`url`	string	yes	Target URL; may template {{record.<field>}} / {{config.*}}
`variables`	object		Egress mapping, injected by the runner from the step-level variables: key.

Example

From Recover:

  - id: crm
    use: http/deliver
    with:
      url: http://127.0.0.1:8765/leads
    variables:
      email: email
      full_name: full_name
      score: demo.score
    idempotency: email