Skip to content
PRESHaiPRESHaiPRESHos Platform

Connector binding

Binding is the step that makes a connector real for one org: one install, one connection, one set of object mappings. The bind surface hangs off the package at /automations/connectors/[packageKey], reached from Integrations / Connectors. Packages own auth, install, config, and scheduling; binding owns the last mile to org scope.

Reading the bind surface

Section titled “Reading the bind surface”

The Ziflow install at /automations/connectors/ziflow carries badge Active. The tagline states the boundary plainly: client proof review happens in Ziflow; approvals stay canonical in PRESHos. That split is the whole page: the connector is the external channel, never the system of record.

  • Tabs across the top: Overview, Connection, Settings, Webhooks, Linked records, Sync activity, Reconciliation, Danger zone. Overview is health; Connection is credentials; Linked records and Sync activity are where a binding proves itself.
  • Install status block: version (1.0.0), installed and activated timestamps, Connection: active, Credentials: Present in Vault. Credential values never appear here; presence is the signal.
  • Quick actions: Test connection and Pause. Docs and Refresh sit top-right. A binding that stops behaving gets paused here first, diagnosed in Sync activity second.
Connector install at /automations/connectors/ziflow: Ziflow Active, Overview tab, install status, quick actions
Example install (Ziflow). Your package key replaces ziflow in the URL.

The binding contract

Section titled “The binding contract”
  • Bindings live in the install’s settings.object_mappings, scoped to org, package, and connection. A mapping without all three coordinates is meaningless.
  • Identity is binding:<uuid> in ai.connector_object_map. Substitute your install’s values for the bracketed placeholders (coordinates, never secrets).
  • Destinations come from the destination catalog (target-catalog.ts). Example shape: targetObject: 'work-items' with workItemTypeId. Never the retired tasks/deliverables destinations.
  • Imports run from an authorized runner: a new Inngest function registered via function-catalog. connector-sync-runner stays dead; never revive it, never expose applyConnectorMappedRecord unauthenticated.

Worked binding end to end: E2E: HubSpot inbound import. Contract reference: SDK concepts. Non-HubSpot systems follow the same contract; only the HubSpot walkthrough exists so far.