HTTP enrich
Fetches a URL templated from the record's fields and stores the page as markdown, or extracts fields from a JSON response.
| Connector | http/enrich |
|---|---|
| Role | enrich |
| 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: enrich
use: http/enrich
with:
url: URL
freshness_days: FRESHNESS_DAYSReplace the following:
URL: request URL, templated from {{record.<field>}} placeholders — which are also the step's derived needsFRESHNESS_DAYS: rEQUIRED, no default: web content rots. Doubles as the step's cache window.
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
| Key | Type | What it does |
|---|---|---|
url required | string | Request URL, templated from {{record.<field>}} placeholders — which are also the step's derived needs |
freshness_days required | integer | REQUIRED, no default: web content rots. Doubles as the step's cache window. |
method | GET | POST | Default GET |
query | object | |
headers | object | |
markdown | boolean | Fetch a page and store it as markdown under field: |
field | string | The declared content field (markdown mode) — canonical or namespaced |
extract | object | Inline JSON mode: field → dotted response path |
max_bytes | integer | Response 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. |
auth | object | |
keep_payloads | boolean | per-step override of payload retention |
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.