Current

09 — Connector Marketplace and Integration Registry UI

Status: Active frontend handoff

Boundary

The Connector Marketplace is the tenant selection tray. Integration Manager is
the operational view of installed bindings, sync, webhooks and schemas. Neither
surface owns OAuth credentials or connector execution.

This in-product tray is distinct from the IW-Spine-Network Plugin published
in plugin marketplaces and IW-Spine-Network MCP published in MCP
marketplaces. Those packages activate IntegrateWise; this tray adds provider
connections after activation.

Catalog view

Each catalog item displays:

  • connector/package ID, name, publisher, category and verified version;
  • supported entities, read/write/webhook capabilities and required scopes;
  • supported environments and authorization method;
  • availability for the current role/industry/department projection;
  • install, configured, syncing, operational, degraded or revoked state.

No connector is hardcoded as mandatory infrastructure for customer tenants.
Configuration Manager and Activation Hub determine recommendations and
readiness.

Gateway interactions

The typed client uses the Gateway routes defined by the live contract, including
workspace discovery and marketplace package/installation endpoints. Authorization
starts through a Gateway-generated state/PKCE transaction. The browser never
receives provider refresh tokens.

Every installation is bound to:

tenant_id + account_id + user_id + spine_network_id
+ marketplace_package_id + provider_connection_id + environment

Duplicate-source handling

When the same provider/account is discovered through multiple hosts, show one
logical source with multiple bindings. The UI exposes provenance and lets an
authorized user choose precedence, merge policy or isolation. It must not merge
records solely because provider names match.

Acceptance

  • Cross-tenant installations never appear.
  • Consent state survives redirect and is idempotent.
  • Revocation removes usable authority without deleting canonical history.
  • Partial discovery shows which hosts were searched and which failed.
  • A successful install does not display “operational” until activation and
    initial synchronization evidence are complete.