Custom Builds · Integrations
A connection is not an integration until the operating rules are clear.
CSS does not publish named third-party integrations for Custom Builds. A feasible integration needs technical discovery first.
What discovery verifies
API or export method, authentication, rate limits, field mapping, record matching, data quality, vendor terms, permissions, and ongoing costs.
The failure path is part of the scope
Error handling and a manual fallback with a named owner are designed in — see the integration-failure workflow story for how that looks in practice.
System of record
Every in-scope field gets one authoritative system, decided and written down, so a sync conflict has an answer before it happens.
Boundary. No named integration, real-time sync, universal compatibility, uptime, or vendor-support promise before technical discovery.