Connectors › HTTP

HTTP enrich

Fetches a URL templated from the record's fields and stores the page as markdown, or extracts fields from a JSON response.

Connectorhttp/enrich
Roleenrich
Recordsperson
Tierbuilt in
Credentialnone
Costunset in the manifest; gtme plan prints what the step declares at run time
Sourceinternal/adapters

Use it

It ships inside the binary. In a pipeline file:

steps:
  - id: enrich
    use: http/enrich
    with:
      url: URL
      freshness_days: FRESHNESS_DAYS

Replace the following:

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

The fields the step's provides: line declares.

Config

KeyTypeWhat it does
url requiredstringRequest URL, templated from {{record.<field>}} placeholders — which are also the step's derived needs
freshness_days requiredintegerREQUIRED, no default: web content rots. Doubles as the step's cache window.
methodGET | POSTDefault GET
queryobject
headersobject
markdownbooleanFetch a page and store it as markdown under field:
fieldstringThe declared content field (markdown mode) — canonical or namespaced
extractobjectInline JSON mode: field → dotted response path
max_bytesintegerResponse size cap (default 262144). An oversized response stores no field — the record advances counted empty, never truncated silently — and is still retained as a payload for the retention window.
authobject
keep_payloadsbooleanper-step override of payload retention
entity_typestring

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.