A Connectify-owned Salesforce adapter, not a packaged connector
We collapse that workflow by keeping the Salesforce adapter inside our own runtime, monitored by our SRE rotation and updated as Salesforce, Inc. ships breaking changes. That means the field maps, sync cadences, and replay rules are shaped to your exact data model — including Permission-set aware writes — no governor-limit surprises and Custom + standard object discovery on first run. For teams in Mesa, the difference shows up the first time the upstream API throws a 500 — the adapter retries, journals the failure, and never silently swallows a transaction.
