IronKernel Platform

CRM: Integrations & External CRM Adapters

Provider adapters (HubSpot/Salesforce and future systems) with mapping, retry, and state tracking.

Problem

Provider adapters (HubSpot/Salesforce and future systems) with mapping, retry, and state tracking.

Provider adapters (HubSpot/Salesforce and future systems) with mapping, retry, and state tracking.

1 Integration schema/runtime added for provider connections, sync state cursor tracking, and dead-letter replay controls (crm_integrations, crm_integration_sync_state,...
2 Adapter registry framework added with provider-specific adapters for HubSpot and Salesforce (hubspot, salesforce) using structured mapping...
3 Integration operator APIs added for listing connections, running sync cycles, listing DLQ records, and replaying DLQ...
4 Integration sync now records CRM activity entries for traceability and updates per-integration sync metadata (cursor, failures,...

Integration schema/runtime added for provider connections, sync state cursor tracking, and dead-letter replay controls (crm_integrations, crm_integration_sync_state,...
Adapter registry framework added with provider-specific adapters for HubSpot and Salesforce (hubspot, salesforce) using structured mapping...
Integration operator APIs added for listing connections, running sync cycles, listing DLQ records, and replaying DLQ...

Feature-level proof

Integrations & External CRM Adapters scope is defined in product module catalog.
verified
docs/products/crm/product.md · Module Catalog > Integrations & External CRM Adapters
CRM modules support intake processing, route projection, and qualification lifecycle evidence.
verified
docs/products/crm/product.md · Module Catalog > Intake & Qualification
Code: backend/services/crm/internal/modules/intake
Contract: proto/crm/intake/v1
CRM intake and qualification flows are implemented in dedicated modules and contracts.
verified
docs/products/crm/product.md · Module Catalog > Intake & Qualification
Code: backend/services/crm/internal/modules/intake
Contract: proto/crm/intake/v1

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).

Commercial to execution

Outcome: Converted commercial records move into execution with less re-entry and clearer ownership.

Commercial handoff friction drops when conversion and execution planning are connected by shared identifiers.

Route-level continuity checks where this feature appears in product-pair workflows.

Revenue-to-Execution

Formula: Execution-Aware Sales -> Load Lifecycle

Zero-to-Onboarded

Formula: CRM -> TMS

Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.