A claim form's lists come from the CRM without exposing its GraphQL

Goal Feed a form's lists from a GraphQL CRM without the browser depending on the CRM's schema.

The claim type and subtype live in a CRM that speaks GraphQL. lumnik ingests it page by page into a canonical entity.

a small BFF serves the form stable REST JSON
switching from Car to Home replaces the list
an unknown type answers 404

lumnik Open
Insurance
Forms
Connector
Entity

insurance-case-options.json

[
  {"id":"AUTO-COLLISION","typeCode":"AUTO","typeLabel":"Automobile","subtypeCode":"COLLISION","subtypeLabel":"Collision","typeOrder":10,"subtypeOrder":10,"active":true},
  {"id":"AUTO-GLASS","typeCode":"AUTO","typeLabel":"Automobile","subtypeCode":"GLASS_BREAKAGE","subtypeLabel":"Bris de glace","typeOrder":10,"subtypeOrder":20,"active":true},
  {"id":"AUTO-THEFT","typeCode":"AUTO","typeLabel":"Automobile","subtypeCode":"THEFT","subtypeLabel":"Vol du véhicule","typeOrder":10,"subtypeOrder":30,"active":true},
  {"id":"HOME-WATER","typeCode":"HOME","typeLabel":"Habitation","subtypeCode":"WATER_DAMAGE","subtypeLabel":"Dégât des eaux","typeOrder":20,"subtypeOrder":10,"active":true},
  {"id":"HOME-FIRE","typeCode":"HOME","typeLabel":"Habitation","subtypeCode":"FIRE","subtypeLabel":"Incendie","typeOrder":20,"subtypeOrder":20,"active":true},
  {"id":"HOME-BURGLARY","typeCode":"HOME","typeLabel":"Habitation","subtypeCode":"BURGLARY","subtypeLabel":"Cambriolage","typeOrder":20,"subtypeOrder":30,"active":true},
  {"id":"HEALTH-HOSPITAL","typeCode":"HEALTH","typeLabel":"Santé","subtypeCode":"HOSPITALISATION","subtypeLabel":"Hospitalisation","typeOrder":30,"subtypeOrder":10,"active":true},
  {"id":"HEALTH-DENTAL","typeCode":"HEALTH","typeLabel":"Santé","subtypeCode":"DENTAL_CARE","subtypeLabel":"Soins dentaires","typeOrder":30,"subtypeOrder":20,"active":true},
  {"id":"HOME-OLD-STORM","typeCode":"HOME","typeLabel":"Habitation","subtypeCode":"OLD_STORM_CODE","subtypeLabel":"Ancien code tempête","typeOrder":20,"subtypeOrder":90,"active":false}
]

manifests/10-insurance-crm.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-insurance-crm-b  connector_type: rest-generic  scopes: [insurance]spec:  base_url: http://host.docker.internal:18091  graphql_path: /graphql  endpoints:    - id: case-options      kind: graphql      query: |        query InsuranceCaseOptions($after: String) {          insuranceCaseOptions(first: 3, after: $after) {            edges {              node {                id                typeCode                typeLabel                subtypeCode                subtypeLabel                typeOrder                subtypeOrder                active              }            }            pageInfo { hasNextPage endCursor }          }        }      pagination:        kind: relay        cursor_binding: variable        cursor_var: after        cursor_path: $.data.insuranceCaseOptions.pageInfo.endCursor        has_more_path: $.data.insuranceCaseOptions.pageInfo.hasNextPage        response_path: $.data.insuranceCaseOptions.edges[*].node      incremental: { mode: full }      target:        kind: hybrid        table: connector.scenario_insurance_case_option_b        unique_key: $.id        promote:          - { name: option_id, path: $.id, type: text }          - { name: type_code, path: $.typeCode, type: text }          - { name: type_label, path: $.typeLabel, type: text }          - { name: subtype_code, path: $.subtypeCode, type: text }          - { name: subtype_label, path: $.subtypeLabel, type: text }          - { name: type_order, path: $.typeOrder, type: integer }          - { name: subtype_order, path: $.subtypeOrder, type: integer }          - { name: active, path: $.active, type: boolean }

$ lm validate -f manifests/10-insurance-crm.yaml
✓ 10-insurance-crm.yaml — valid

$ lm apply -f manifests/10-insurance-crm.yaml
Applied connector "scenario-insurance-crm-b" — 1 endpoint

$ lm source rest test scenario-insurance-crm-b
ENDPOINT      METHOD  STATUS  ITEMS  VERDICT
case-options  POST    200     3      ok

manifests/20-insurance-case-option.yaml

kind: Entityname: ScenarioInsuranceCaseOptionBdescription: "An insurance claim type and subtype pair curated by the CRM."match: [option_id]scopes: [insurance]columns:  type_code:    label: "Claim type code"  type_label:    label: "Claim type"  subtype_code:    label: "Claim subtype code"  subtype_label:    label: "Claim subtype"  active:    label: "Available"sources:  - table: scenario_insurance_case_option_b    map:      option_id: option_id      type_code: type_code      type_label: type_label      subtype_code: subtype_code      subtype_label: subtype_label      type_order: type_order      subtype_order: subtype_order      active: active

$ lm connector run scenario-insurance-crm-b
run scheduled: a1804432-d945-4e2e-8aa4-6da5b303e372

$ lm run get a1804432-d945-4e2e-8aa4-6da5b303e372
ID        CONNECTOR                 ENDPOINT      STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
a1804432  scenario-insurance-crm-b  case-options  Completed  9   9    0        0             2026-11-03 19:17  2026-11-03 19:17  yes

$ lm entity apply -f manifests/20-insurance-case-option.yaml
Applied entity "ScenarioInsuranceCaseOptionB" → connector."v_scenarioinsurancecaseoptionb"

$ lm entity get ScenarioInsuranceCaseOptionB --limit 1000 -o json
[
  {
    "option_id": "AUTO-COLLISION",
    "type_code": "AUTO",
    "type_label": "Automobile",
    "subtype_code": "COLLISION",
    "subtype_label": "Collision",
    "type_order": "10",
    "subtype_order": "10",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "AUTO-GLASS",
    "type_code": "AUTO",
    "type_label": "Automobile",
    "subtype_code": "GLASS_BREAKAGE",
    "subtype_label": "Bris de glace",
    "type_order": "10",
    "subtype_order": "20",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "AUTO-THEFT",
    "type_code": "AUTO",
    "type_label": "Automobile",
    "subtype_code": "THEFT",
    "subtype_label": "Vol du véhicule",
    "type_order": "10",
    "subtype_order": "30",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "HEALTH-DENTAL",
    "type_code": "HEALTH",
    "type_label": "Santé",
    "subtype_code": "DENTAL_CARE",
    "subtype_label": "Soins dentaires",
    "type_order": "30",
    "subtype_order": "20",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "HEALTH-HOSPITAL",
    "type_code": "HEALTH",
    "type_label": "Santé",
    "subtype_code": "HOSPITALISATION",
    "subtype_label": "Hospitalisation",
    "type_order": "30",
    "subtype_order": "10",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "HOME-BURGLARY",
    "type_code": "HOME",
    "type_label": "Habitation",
    "subtype_code": "BURGLARY",
    "subtype_label": "Cambriolage",
    "type_order": "20",
    "subtype_order": "30",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "HOME-FIRE",
    "type_code": "HOME",
    "type_label": "Habitation",
    "subtype_code": "FIRE",
    "subtype_label": "Incendie",
    "type_order": "20",
    "subtype_order": "20",
    "active": "true",
    "_conflicts": "{}"
  },
  {
    "option_id": "HOME-OLD-STORM",
    "type_code": "HOME",
    "type_label": "Habitation",
    "subtype_code": "OLD_STORM_CODE",
    "subtype_label": "Ancien code tempête",
    "type_order": "20",
    "subtype_order": "90",
    "active": "false",
    "_conflicts": "{}"
  },
  {
    "option_id": "HOME-WATER",
    "type_code": "HOME",
    "type_label": "Habitation",
    "subtype_code": "WATER_DAMAGE",
    "subtype_label": "Dégât des eaux",
    "type_order": "20",
    "subtype_order": "10",
    "active": "true",
    "_conflicts": "{}"
  }
]

GET /form-options/claim-types: AUTO Automobile · HOME Habitation · HEALTH Santé
… /AUTO/sub-types: COLLISION Collision · GLASS_BREAKAGE Bris de glace · THEFT Vol du véhicule
… /HOME/sub-types: WATER_DAMAGE Dégât des eaux · FIRE Incendie · BURGLARY Cambriolage

evidence: replay.log, 50-claim-types.json, 51-auto-subtypes.json, 52-home-subtypes.json, 53-unknown-type.json · transform v1

… /UNKNOWN/sub-types: 404 · claim type not found

evidence: replay.log, 50-claim-types.json, 51-auto-subtypes.json, 52-home-subtypes.json, 53-unknown-type.json · transform v1

Limits

The CRM is synthetic but speaks the real request and Relay response shapes of lumnik's GraphQL connector.
The BFF is demonstration-sized: it calls lm on every request. A production BFF would call the hub API with its own identity and cache these lists.
The BFF only reads; creating the claim in the CRM is outside the scenario.
The rule is active == true; effective dates, per-language labels and per-product eligibility would be further business rules.
Synthetic data.

Insurance · form

A claim form has two lists.

The type, then the subtype.

Both live in a CRM that speaks GraphQL.

Synthetic CRM

The problem

The CRM's schema becomes the browser's contract.

The front end calls the CRM's GraphQL.
Every CRM change breaks the form.
A retired code can stay on offer.

Nothing is changed

The CRM keeps its GraphQL.

lumnik reads it page by page.
An entity carries stable names.
The form reads REST JSON.

What had to be written

kind: graphql
query: |
  query InsuranceCaseOptions($after: String) {

GraphQL is a request shape, not a connector.

A 78-line scenario, two declaration files.

What the policyholder sees

Car: three subtypes.

Collision.
Glass breakage.
Vehicle theft.

Real BFF answer, replay of 3 November 2026.

A list replaced

Home replaces the list.

Water damage, fire, burglary.
Collision never stays.
The retired code is not offered.

The limit

The BFF is demo-sized.

It calls lm on every request.
In production: the hub's API and a cache.
Creating the claim in the CRM is out of scope.

Try it

The scenario replays end to end.

GraphQL CRM, entity, BFF: every step is published with its output.

This scenario runs on lumnik Open, free and open source.

Try lumnik Open →