CRAIM already includes a broad integrations layer. It is not limited to one CRM or one messaging provider.
CRM integrations
The backend supports universal CRM integration flows with provider adapters and sync services.
Currently supported CRM providers in the codebase include:
- AmoCRM
- Bitrix24
- HubSpot
Communication channels
Communication channels and lead sources are intentionally different concepts.
Channels
Channels are for direct communication surfaces such as:
- Telegram
- phone
These are operational execution paths for conversations and calls.
Why channels matter
Connected channels let CRAIM keep message and call activity tied to the company workspace and CRM records.
Telephony
Telephony is modeled separately so the system can support provider-specific routing and AI calling paths.
Providers present in the codebase include:
- OnlinePBX
- Mango Office
- Zadarma
- Twilio-based phone integrations
Calendar
Calendar integration exists as a separate module so scheduling and event operations can remain explicit rather than being buried in generic notes.
Recommended implementation rule
Use integrations as infrastructure and routing. Do not let provider-specific details leak into daily sales operation more than necessary.