Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thesozocrm.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Integrations

Connect only what your team uses daily, then scale in phases.

​
Integration priorities

Phase 1: Must-have

Proposal/design, notifications, and payout visibility tools.

Phase 2: Operational depth

Installer coordination, accounting sync, and analytics exports.
1

Map system owners

Assign an owner for each integration before enabling it.
2

Define source of truth

Decide which platform owns each field to avoid sync conflicts.
3

Dry run with test records

Validate create/update paths before production traffic.
4

Launch with monitoring

Watch first-week sync health and exception counts daily.

​
Data reliability checklist

Use stable IDs, not names, as your cross-system join key.
Make retry-safe writes (idempotent updates).
Log failures with enough context to replay safely.

​
Technical implementation notes

Use authenticated requests tied to a real Sozo user context. Enforce access by role and team scope.
Assume duplicate delivery can happen. Design create/update handlers so replaying the same event is safe.
Define one source of truth per field before go-live to prevent bidirectional overwrite conflicts.
Track success rate, retry counts, and dead-letter failures for every critical sync workflow.

​
Need API-level details?

Use API Reference for auth patterns and integration implementation guidance.