Connectors
A connector links an external system to VB-OS so that evidence can be pulled from it automatically. Instead of manually including evidence values in every workload, a connector fetches data from the source system at evaluation time, with full provenance tracking.
Managing Connectors
Section titled “Managing Connectors”Connectors are managed in the Integrate tab of a project, under the Connectors sub-tab. You can search by name, filter by provider or status, and create new connectors.
Creating a Connector
Section titled “Creating a Connector”Click New Connector and provide:
- Provider: the external system type (e.g., a database, API, or SaaS platform)
- Name: a descriptive name for this connector instance
- Credentials: authentication details for the external system (stored securely, never exposed in logs or API responses)
- Evidence mapping: which fields from the external system map to which evidence fields in your boundary
Evidence Mapping
Section titled “Evidence Mapping”Each connector defines a mapping between external data and VB-OS evidence fields. For example, a connector to a KYC provider might map the provider’s identity_verified response field to the kyc_verified evidence field your boundary requires.
The mapping also establishes provenance: VB-OS records that a specific evidence field came from a specific external source, which is used by require_provenance declarations in boundaries.
Connector Status
Section titled “Connector Status”Each connector has a status:
- Active: connected and available for evidence gathering
- Error: the most recent attempt to reach the external system failed (check credentials and network)
- Disabled: manually paused by a team member
Testing a Connector
Section titled “Testing a Connector”After creating a connector, use the Test action to verify that VB-OS can reach the external system and that the evidence mapping produces the expected fields. The test result shows the raw response from the provider and the mapped evidence fields.
What’s Next
Section titled “What’s Next”- Boundaries : add
require_provenancedeclarations that reference your connectors - Evaluations : submit evaluations that use connector-gathered evidence
- For developer integration details, see Connectors (Build)