NativeFlex CRM Settings — Setup Guide

This guide explains each field and how to configure them in CRM Settings for NativeFlex CRM integrations within the Further Dashboard.

💡 When fields are not used, be sure to insert a -. If the fields are left blank, you will not be able to save the CRM settings.

Basic Information

CRM Type
Dropdown to select the CRM integration type. Select NativeFlex CRM for this setup.

Name (required)
Internal label for this configuration. Useful when multiple CRM settings exist.

Default (required if there are no existing CRM settings)
Check this to make the configuration the default for the property or organization.

Enabled (required)
Activates the integration. Toggle off to pause without deleting the configuration.

Authentication

Choose one of the following authentication methods. Only one method can be active at a time.

OAuth

Enable if the CRM requires OAuth 2.0 authentication for API requests. Please include the OAuth endpoint in the OAuth URL field. Enter your grant_type within the OAuth Configurator — both client_credentials and password grant types are supported. Ensure that "OAuth Required" is toggled on.

Basic Auth

Enable if the CRM requires HTTP Basic Authentication (username + password sent with each request). Fill the URL field with the valid endpoint you will be sending lead information through.

Digest Auth Required

Enable if the CRM uses Digest Authentication, a more secure variant of Basic Auth.

Bearer Token

Enable if API requests must include a Bearer Token in the Authorization header. Provide the static token in the Bearer Token field.

URL Parameters

Enable if authentication credentials must be passed as URL query parameters instead of headers. Ensure URLs added to the integration include the URL parameters required for authentication.

Sync Settings

Move In Engine
Specifies the engine or method used to process and sync move-in events to the CRM.

Enable Move Ins Sync
When on, move-in events are automatically synced to the CRM in real time.

Max Field Length
Set character limits for fields sent to the CRM. Useful when the CRM enforces field-length restrictions.

Lead Requests

Post Lead Request URL
API endpoint where new lead data is sent when a lead is submitted through Further.

Post Lead Payload Configurator
Customize the field mapping and structure of the lead payload.
Map from = Client CRM field names | Map to = Further's internal API field names

Post Lead External ID JSON Path
JSON path used to extract the lead's external CRM ID from the response, linking future updates to the correct record.

Tour Requests

Post Tour Request URL
API endpoint where tour/visit data is sent when a tour is scheduled.

Post Tour Payload Configurator
Customize the field mapping and structure of the tour payload.
Map from = Client CRM field names | Map to = Further's internal API field names

Post Tour Validation JSON Path
JSON path used to parse the CRM's response after a tour is posted, confirming it was received successfully.

Messaging

Post Message Request URL
API endpoint where lead messages are posted to the CRM.

Post Message Payload Configurator
Customize the payload structure for message posts.

Post Message Validation JSON Path
JSON path used to validate the CRM's response after a message is posted, confirming it was received successfully.

Insurance

Patch Insurance Request URL
Endpoint used to update (PATCH) insurance information on an existing CRM record.

Patch Insurance Payload Config
Customize the payload sent when patching insurance data.

Post Insurance Image Request URL
Endpoint used to upload insurance images or documents to the CRM.

Post Insurance Image Payload Config
Customize the payload structure for insurance image uploads.

Other Settings

Allow Activity Without External CRM Lead ID
When enabled, activity (tours, messages, etc.) can be sent to the CRM even if no external CRM Lead ID has been stored in the Further system.