# Connect ELMA365

Connect an ELMA365 company to ChatRex with OAuth and configurable CRM application mapping.

The integration lets your bot find and save contacts, create deals and tasks, change permitted stages, add notes and return links to ELMA365 records.

You need ELMA365 administrator access, the ChatRex AI Connector module, API access and permissions for the selected applications, plus a ChatRex integration subscription. The ChatRex subscription is purchased separately in ChatRex. Built-in CRM applications may require an additional ELMA365 license. Custom company applications with compatible fields and relationships can also be mapped.

This version works with CRM data. It does not connect the Lines messaging channel or launch bots from ELMA365 events.

# Install the module and create an OAuth client

Install ChatRex AI Connector in the required ELMA365 company. To use a .e365 file supplied by ChatRex, open Administration → Modules, add a module and choose the file upload option. Select the archive, continue, check the module name and wait for the dependency checks to finish. Complete installation and open the installed module. Back up the company configuration before updating an existing module.
In ChatRex, open Integrations → Connect integration → Data sources → ELMA365 and copy the callback URL shown in the connection form.
In ELMA365, open the module settings using its gear icon, then the External application tab. Enable the external application and use the ChatRex CRM API template with the api permission.
Expand the module’s token section and create an OAuth2/OIDC client. Select the ChatRex CRM API external application. Set its redirect URI to the copied callback URL, then save its client ID and client secret.
Authorize using a dedicated ELMA365 user with access only to the required applications and records. Write actions need permission to create and update records, change the permitted stages and add comments to object feeds.

In the installed module, select the same user in Connection user, enable Allow ChatRex actions, and save. The bot cannot use the module until a user is selected and actions are enabled.

ChatRex does not need your ELMA365 user password. Enter the OAuth client secret only in the connection settings, never in a bot prompt or a customer's message.

# Connect the company

Enter the HTTPS company URL, OAuth client ID and client secret in the ELMA365 connection form in ChatRex.
Prepare the connection, then open ELMA365 authorization.
Sign in to the required company and grant access. Return to ChatRex.
Check the connection. Application mapping becomes available after successful authorization.
If the subscription selection opens, purchase a suitable subscription through the normal ChatRex flow.

The authorization link expires after 10 minutes. Prepare a new connection if the link expires or access is denied. Contact ChatRex support if no callback URL is shown.

# Map your CRM applications

Choose the applications used by your company; their names may differ from the standard Contacts, Deals and Tasks.

Section	What to select
Contacts	Record title, full name, phone or email, and a searchable request ID field; optionally a company relationship
Deals or leads	Title, a relationship to the selected contacts application, status and request ID; optional fields shown in the form
Tasks	Title, deadline, assignee, request ID and a relationship to a deal or contact
Companies	An optional company directory and its title field

The request ID field is a separate searchable field used to prevent duplicate records. Do not manually change its values on records created by the bot. Exact contact search needs a phone number or email; name-only search is not supported.

Choose the pipeline, initial stage, allowed stages and assignees. Add each permitted From stage → To stage transition. The selected ELMA365 status group must allow manual status changes. The bot cannot change stages without configured transitions.

Validate and save the mapping. ChatRex checks fields, relationships, available stages, users and read access. A successful save also synchronizes the mapping with the ELMA365 module.

Validate and save again after changing fields, permissions or stages, saving module settings, upgrading the module or re-enabling it. Then update the setup of any bot created from the template so that it uses the validated mapping.

# Configure and test a bot

Create a bot from the ELMA365 template or add actions in Integrations and actions. Select the connected company and the parameters allowed for this bot. See ELMA365 actions.

First run previews using IDs of existing test records. Then ask the test bot to find a contact, obtain consent to save data, create a deal, add a note and create a related task. Open the returned links and verify the data, stage, deadline and assignee in ELMA365.

Multiple matching contacts or active deals require clarification; the bot must not choose a record arbitrarily. If a write outcome is unconfirmed, inspect ELMA365 and contact support before submitting a new request to create the same record.

# Connection diagnostics

In the integration settings, click Check connection and module. ChatRex checks CRM access, the installed module API and version, and the current validity of the saved mapping separately. Unsaved form changes are not included.

If CRM access passes but the module needs attention, check that ChatRex AI Connector is installed and its API methods use external authorization in ELMA365. A module-only access failure does not disconnect a working CRM connection. Save the mapping again if its schema or permissions have changed.

In the ELMA365 module, Connection check shows whether actions are enabled, a user is selected and the mapping is synchronized. This is a snapshot from when the form opened; reload after changes. If it requests mapping validation, validate and save in ChatRex.

Diagnostics do not create CRM records or test write actions. Run a separate bot test and verify the resulting records in ELMA365.

# Errors and disconnection

Module disabled or unavailable: enable ChatRex AI Connector, allow actions, select the OAuth connection user and save. Then validate the mapping in ChatRex.
Module linked to another connection: disconnect the previous ChatRex connection first. If it is already disconnected, save the module settings in ELMA365 to clear the remaining binding, then validate the new mapping.
Application unavailable: check the connected user's permissions and the ELMA365 license.
Outdated mapping: select any changed fields or stages, then validate and save again.
Authorization invalid: check the OAuth client and reconnect.
Transition unavailable: check the current stage, allowed transitions and manual status changes in ELMA365.

To disconnect, click Disconnect in the ChatRex integration card to stop bots from using the connection. In ELMA365, open your user menu, settings and external applications, then revoke the ChatRex authorization if it appears in the list. If the OAuth client is no longer needed, delete it from the module’s token section.

Deleting an OAuth client does not guarantee that an existing access token stops working immediately. ELMA365 access tokens last 10 minutes, so disconnect the integration in ChatRex first. Reconnection requires mapping validation again.