Guides
Integrating CRM mirrors
Keep an external CRM as a mirror of ComeBk opportunity state without inventing a second source of truth.
- Guides
- 1 min read
Principle
ComeBk owns marketing and sales workflow state for commercial lending. External CRMs may mirror opportunities for reporting or enterprise IT standards. Do not treat the CRM as the system of record for stage, channel, or explainability.
Recommended sync direction
| Direction | Use when | | ------------ | -------------------------------------------------------------------------------- | | ComeBk → CRM | Default. Push stage, owner, and summary fields after successful ComeBk writes. | | CRM → ComeBk | Only for bootstrap or rare fields that ComeBk does not yet model. Map carefully. |
Avoid bidirectional sync on the same fields. Conflict rules become unmaintainable.
Mapping checklist
- Map CRM “deal” or “opportunity” ids to ComeBk opportunity ids in a dedicated join table.
- Preserve ComeBk stage and channel vocabularies; do not collapse them into CRM picklists that lose meaning.
- Store explanations in ComeBk; put only a short summary or link in the CRM.
- Idempotent webhooks: key by
opportunityId+stageTransitionId.
Failure modes
- CRM downtime must not block ComeBk stage advancement.
- Retry with backoff; log dead letters for operator review.
- On mapping drift, prefer ComeBk state and emit a reconciliation report.
Related
For commercial or access questions: Contact.