8. Integrations — CRM Integrations

8.3 HubSpot Integration

HubSpot is a versatile CRM used for contact management, sales pipeline, and marketing campaigns.

Connection

1. Go to Integrations → HubSpot → Configure
2. Enter your HubSpot API key (Private App Token)
3. Click on "Test connection" to validate
4. Set synchronization options (see below)
5. Click on "Save"

💡 To get your API key: in HubSpot, go to Settings → Integrations → Private Apps → create an app with the scopes crm.objects.contacts.read and crm.objects.contacts.write (prospects), crm.objects.deals.read (properties) and crm.objects.owners.read (agents).

Synchronized entities

💡 A prospect created in NoviaMind (for example from a call) is created in HubSpot once. A contact HubSpot already has is never changed from NoviaMind: HubSpot stays the reference and its changes come back at each sync. If the email already exists in HubSpot, no contact is created. The call summary is not sent to HubSpot.

Synchronization options

Field mapping

NoviaMind allows you to map HubSpot fields with NoviaMind fields. For example:

⚠️ Unmapped fields are not synced. Configure mapping in Integrations → HubSpot → Field Mapping.

8.4 Netty Integration

Netty is a specialized real estate transaction software designed for agencies. It centralizes mandate management, contacts, and viewings.

Connection

1. Go to Integrations → Netty → Configure
2. Enter your Netty API key (the Agency ID field is optional and not used yet)
3. Click on "Test connection" to validate
4. Set synchronization options
5. Click on "Save"

💡 If you do not have a Netty API key, ask Netty (Modelo Office) for one.

Synchronized entities

💡 Netty's API is read-only for properties and agents: they are imported into NoviaMind, never sent back.

What the sync keeps and removes

• Your changes in NoviaMind are kept across syncs: the AI access level, the tags you add, the status, notes and agent you set on a prospect.
• A property Netty marks sold, let, withdrawn or archived stays in NoviaMind but is no longer offered by your AI agents; it is offered again if it comes back on the market.
• A property deleted in Netty is deleted in NoviaMind. A contact deleted or archived in Netty becomes lost.
• A prospect created in NoviaMind (for example from a call) is created in Netty once and is then the Netty contact: new calls update it in Netty, other changes made in NoviaMind are not sent.

Typical use case with Netty

1. A prospect calls about a real estate property
2. The AI agent identifies the property via the synced Netty database and presents the details
3. The prospect is interested → appointment booked automatically
4. A contact is created in Netty with the prospect's details, the call summary in its notes

8.5 Apimo Integration

Apimo is a real estate CRM widely used in France and internationally, providing property management, owner and contact tracking, and publication tools.

Connection

1. Go to Integrations → Apimo → Configure
2. Enter your Agency Name (provider ID) and API Key
3. Click on "Test connection" to validate
4. Set synchronization options
5. Click on "Save"

💡 Your API credentials are available in your Apimo administration panel. Authentication uses HTTP Basic with your agency name and API key.

Synchronized entities

💡 Apimo properties and realtors are read-only — they can be imported into NoviaMind but not pushed back. Leads support full create operations.

Pre-configured field mapping

NoviaMind includes 13 pre-configured property field hints for Apimo, automatically mapping fields like area.value → areaSqm, price.value → price.amount, city.name → address.city, etc.

8.6 Bitrix24 Integration

Bitrix24 is a comprehensive business platform with CRM, project management, and communication tools, popular among real estate agencies.

Connection

1. Go to Integrations → Bitrix24 → Configure
2. Enter your Webhook URL
3. Click on "Test connection" to validate
4. Set synchronization options
5. Click on "Save"

💡 To create a webhook: in Bitrix24, go to Developer resources → Other → Inbound webhook → create a webhook with CRM permissions (crm, crm.item.add, crm.item.update, crm.item.list).

Synchronized entities

Dynamic CRM schema

Bitrix24 has a dynamic CRM schema — deal and contact field definitions are fetched from the Bitrix24 API automatically. This means the field mapping adapts to custom fields configured in each Bitrix24 instance.

8.7 Advanced Synchronization Configuration

Synchronization methods

💡 Whatever the method, when sending to the CRM is enabled, each prospect created by a call is sent right after the call. With Netty, prospects created or changed in NoviaMind are also sent at each sync. A sync already running for the integration cannot be started twice.

Synchronization statuses

In case of failure, the error is displayed on the integration card. Click on "Sync now" to retry manually.

Updates from the CRM

NoviaMind does not receive events from CRMs yet: changes made in the CRM reach NoviaMind at the next sync (scheduled or "Sync now"). To notify your own tools of NoviaMind events, see Outbound Webhooks.

8.8 Testing and Managing an Integration

Testing the connection

From a configured integration card, click on "Test connection". NoviaMind verifies:

• The validity of API credentials
• The CRM endpoint accessibility
• The available permissions

Manual synchronization

Click on "Sync now" to trigger an immediate full synchronization, regardless of the configured mode.

Enable / Disable

Each integration can be enabled or disabled without losing its configuration. Useful for temporarily switching without deleting settings.

Deleting an integration

Click on "Delete" in the integration settings. This action is irreversible and erases the configuration and stored credentials.

⚠️ Deleting an integration does not erase data already synced to your CRM.

Summary