Skip to content

Resources

Integration guide

Patterns for connecting ComeBk to CRM mirrors, identity, and outbound event consumers.

Category
Guides
Type
Guide
Version
v0.3
Published
Tags
integration

Integration surfaces

| Surface | Use | | --------- | ----------------------------------------- | | REST API | Synchronous create/read/advance | | Webhooks | Stage transitions and opportunity updates | | Admin API | Cycles and channels |

Details: API overview.

CRM mirrors

Treat CRM as a reader of ComeBk state. Mapping and failure rules: Integrating CRM mirrors.

Identity

Tokens are tenant-scoped. Map internal user ids to ComeBk ownerId fields in a controlled directory sync; do not invent ad-hoc owner strings in production.

Event consumers

Consumers must be idempotent. Prefer stageTransitionId as the dedupe key. Persist raw payloads for replay for at least the operational retention window agreed with your platform team.

Related

Document only — no binary attachment in this phase.

Version

Version
v0.3