Purpose. Connectors turn existing systems into event sources for the
capture gateway so evidence sealing is automatic — not a manual export every time.
Available connector families (monorepo)
- generic-webhook — signed HTTP webhooks into
/v1/webhooks/{connector_id}
- file-watch — watched folder (e.g. job photos landing on disk)
- github — repository / workflow style events
- otlp — OpenTelemetry-style intake path
- certification — tooling around trust issuance (pilot)
Source: github.com/…/connectors
How to use
- Run a gateway (pilot or self-hosted).
- Enable the connector in gateway settings / env for that instance.
- Point the external system at the webhook URL or drop files in the watch dir.
- Confirm events appear (cases / receipts), then seal the case.
What connectors are not
They do not make “the whole company QEV certified.” They feed one workflow’s evidence plane. Trust marks stay scoped — see Trust program.
Gateway docs · JS SDK · Pilot help