CRM Sync

Keva contains local Salesforce and HubSpot sync, mapping, webhook, and batch-dispatch paths. No customer-facing CRM setup or Settings → CRM Sync journey is offered in this release. Provider activation is unavailable in this release.

Source boundary

The local paths are source inventory only. Provider-valid delivery, configured concurrency, workspace and privacy policy, deployment, and end-to-end bidirectional product behavior have not been verified.

Provider	Local source areas	Proof status
Salesforce	Contacts, Accounts, profile, webhook, and batch paths	Local source paths; product proof open
HubSpot	Contacts, Companies, profile, webhook, and batch paths	Local source paths; product proof open

Current trigger boundary

• Dashboard customer-profile creation and update are suspended.
• No new-ticket producer currently creates a durable profile or dispatches customer sync.
• Inbound Salesforce can create or update a tenant-wide profile; HubSpot updates an already-linked profile. Their workspace, strict PII schema, audit/privacy, configured provider, deployment, and product behavior remain open.
• There is no current customer-profile page or Sync Now customer journey.
• Platform-specific batch-sync API routes exist locally and require connector-edit authority. Their execution remains unverified.

Open Operational Proof

• No timestamp-based conflict-arbitration contract is proven.
• Sync-log rows exist in source, but complete logging, history presentation, and operator recovery are not product-verified.
• A batch worker selects at most 100 profiles per invocation. Complete-customer coverage, provider rate limiting, retries, and delivery remain unverified.
• Connector tokens are encrypted locally; refresh behavior is not claimed.
• HubSpot signature verification has local source coverage. Salesforce webhook authentication must not be described as HMAC without a matching source contract.
• The CRM routes are dashboard routes authenticated by the interactive Clerk session, not keva_live_ public API-key endpoints.

The local source inventory is not a customer procedure. Connection, mapping, provider, webhook, and batch behavior require a supervised Keva-owned fixture and independent read-back before they can be documented as an offered product journey.