HTTP deliver

Posts each record to a URL you choose, with the body templated from the step's variables. The endpoint is yours.

Connector	`http/deliver`
Role	deliver
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:

steps:
  - id: deliver
    use: http/deliver
    with:
      url: URL

Replace the placeholder:

URL: target URL; may template {{record.<field>}} / {{config.*}}

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

Whatever fields the step's uses: line names. The runner checks them at plan time.

Provides

Nothing. A deliver step writes to the target and records a receipt.

Config

Key	Type	What it does
`url` required	string	Target URL; may template {{record.<field>}} / {{config.*}}
`method`	POST \| PUT \| PATCH	Default POST
`query`	object
`headers`	object
`body`		Body template; default is the resolved variables object
`auth`	object
`keep_payloads`	boolean
`entity_type`	string

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.