EchoLoop
TS

Luma sync

Thinkspace calendar · humans export CSVs from Luma Manage → Guests → Export · the existing CLI pipeline loads them idempotently. This page does not upload or apply data yet.

Upload guest CSVs
One file per event, tagged with event_api_id. No paid Luma API.

CSV drop zone is disabled in v0

Export from Luma, then run the documented CLI path.

event_api_idrequired on each file when this ships
Sync runs
Fields match the sketched luma_sync_runs contract. No table is applied yet.
RunStatusNewSkippedFailed
No live sync-run rows. CLI dry-runs write private _sync_run.json / _summary.json artifacts outside Git.
Pipeline (last run)
Existing path: inventory → classify → raw append → register/attend.
  1. Inventory

    Past hosted events for the Thinkspace Luma calendar.

  2. Classify (hash)

    Skip when calendar + event + csv_sha256 already loaded.

  3. Raw append

    New files only. Never mutate historical raw_import_rows.

  4. Register / attend

    Project guest rows into evidence — not marketing consent.

Attendance ≠ marketing consent · Luma is source evidence, not CRM SoT.