#Which tools does CRM Middleware support natively?
CRM Middleware includes native connectors for the following tools. Native connectors are pre-configured, so authentication and field mapping work out of the box.
| Category | Integrations |
|---|---|
| CRM | Salesforce, HubSpot, Pipedrive, Microsoft Dynamics 365 (Business Central and Sales), Sellsy, ActiveCampaign, Loji by Neoteem |
| Helpdesk & IT service management | GLPI, Atera, ConnectWise |
| Any other tool with a REST API | Generic connector (Webhook) |
Setup instructions for each integration are in the Connect CRM Integration guide.
#What can each integration do?
| Integration | Contact lookup (screen pop) | Contact creation | Call logging | Chat logging |
|---|---|---|---|---|
| Salesforce | Yes | Yes | Yes (Task) | — |
| HubSpot | Yes | Yes | Yes (Call activity) | — |
| Microsoft Dynamics 365 | Yes | Yes (Sales: as a lead; Business Central: as a contact) | Yes | — |
| Sellsy | Yes | Yes | Yes (Phone call) | — |
| ActiveCampaign | Yes | Yes | Yes (Deal task) | — |
| Loji by Neoteem | Yes | — | Yes | — |
| GLPI | Yes | — | Yes (Task on an existing ticket) | — |
| ConnectWise | Yes | — | Yes (Activity) | — |
| Atera | Yes | — | — | — |
| Webhook (generic connector) | Yes | Yes | Yes | Yes |
#Can I connect a CRM that is not on the native list?
Yes. CRM Middleware includes a generic connector (Webhook) for any CRM or business tool that exposes a REST API. You configure the connection visually in the CX-Engine interface: no code, no SQL, and no API expertise required. This makes it possible to connect proprietary or industry-specific tools alongside the natively supported ones. The routes your API needs to expose are described in Requirements for the CX-Engine Middleware.
#Which PBX systems are compatible?
CRM Middleware currently supports 3CX (v18 and above) and Yeastar P-Series. Both are connected to CX-Engine via an OAuth 2.0 flow, using either the Authorization Code method (recommended for 3CX with the standard XML template) or the Client Credentials method for server-to-server or headless setups.
#Can I connect multiple CRM integrations at the same time?
Yes. CX-Engine supports connecting several CRM integrations simultaneously under the same account. Each integration gets its own API key and can be enabled or disabled independently for features such as contact lookup and call logging. You can also define a priority order so CX-Engine queries integrations in sequence until a matching contact record is found.
#How is the connection to a CRM authenticated?
The authentication method depends on the integration. You choose it in the API Key type field when adding the integration:
| Integration | Authentication method(s) | What you provide |
|---|---|---|
| Salesforce | OAuth 2.0 Authorization Code | Sign in to Salesforce and authorize CX-Engine |
| HubSpot | OAuth 2.0 Authorization Code, or API token | Sign in to HubSpot and authorize CX-Engine, or paste a private app access token |
| Microsoft Dynamics 365 | OAuth Azure, or OAuth 2.0 Client Credentials | Your Dynamics domain, then sign in with Microsoft; or API URL, client ID, client secret, tenant ID and scope |
| Sellsy | OAuth 2.0 Personal Access Token | Client ID and client secret |
| ActiveCampaign | API token | Account API URL and API key |
| Loji by Neoteem | Basic Auth | Instance URL, username and password |
| GLPI | App & User token | GLPI API URL, app token and user token |
| ConnectWise | ConnectWise API Keys | API base URL, company ID, client ID, public key and private key |
| Atera | API token | Atera API key |
| Webhook (generic connector) | None, Basic Auth, API token (header or request parameter), username and password, OAuth 2.0 Client Credentials, OAuth 2.0 Resource Owner Password | Depends on the method chosen |
All credentials are entered once in the Integrations menu and stored encrypted; no developer access is needed to set them up.