This guide is intended for implementation consultants setting up a NativeFlex CRM integration on behalf of a client. It covers the prerequisites and configuration steps for each supported CRM, an introduction to NativeFlex, and a field mapping reference.

Supported CRMs

Salesforce

To connect Further with your Salesforce org, your Salesforce admin will need to configure three things: a dedicated integration user, a permission set, and a Connected App. The specifics of how to create each may vary depending on your Salesforce edition — refer to Salesforce documentation for setup steps.

Note: Salesforce System Administrator access is recommended for the person completing this setup.

Integration User

Further requires a dedicated, non-human Salesforce user that the integration runs as. This should not be an existing employee or admin account.

The user must have:

• A Salesforce user license

• API access enabled

• The Further permission set assigned (see below)

• No broader profile-level permissions than necessary

Permission Set

Create a permission set and assign it to the integration user. Access should be limited to only what the integration needs.

Required object permissions:

Required system permissions:

• API Enabled

Field-level access should be limited to only the fields in the payload mapping (see Field Mapping Reference below).

⚠ The integration user should never have Delete access on any object.

External Connected App

Further currently authenticates using the OAuth Username-Password flow. JWT Bearer Token support is on the roadmap.

The Connected App must be configured with:

• OAuth enabled

• client_credentials flow enabled in Settings and Policies

• OAuth scopes: Manage user data via APIs (api), Perform requests at any time (refresh_token), Access the Salesforce API Platform

• Grant type: client_credentials

Further will need the following credentials from you:

If using client_credentials:

• Consumer Key (Client ID)

• Consumer Secret (Client Secret)

If using password:

• Consumer Key (Client ID)

• Consumer Secret (Client Secret)

• Integration user's username

• Integration user's password

⚠ Credentials should not be shared over email. Further will provide a secure method for credential handoff during onboarding.

Go High Level

🚧 Coming Soon — Go High Level CRM integration support documentation is currently in development. This section will be updated when available.

Kipu

🚧 Coming Soon — Kipu CRM integration support documentation is currently in development. This section will be updated when available.

Lightning Step

🚧 Coming Soon — Lightning Step CRM integration support documentation is currently in development. This section will be updated when available.

NativeFlex Overview

NativeFlex is Further's generalized CRM integration engine that sits between our products (VSA, CW, phone, etc.) and external CRMs like Salesforce, Kipu, Lightning Step, and others. It standardizes payload mapping, auth, and extras — such as insurance card image push and admit/move-in fetchers — so CRM behavior is configurable in the dashboard instead of hard-coded per client.

For full setup and configuration instructions, refer to the NativeFlex CRM Settings — Setup Guide.

Field Mapping Reference

NativeFlex uses a standardized field library that applies across all supported CRM integrations. The mapping reference below documents every available field, its data type, and syntax — use it to map Further fields to the corresponding fields in your CRM.

Refer to the full reference here: NativeFlex Field Library & Syntax Reference.