> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Lightfield, Monaco & Octolane

> Connect additional CRMs and bring accounts, contacts, and opportunities into Quivly.

Admins can connect these CRMs under **Data → Integrations**. They feed the same customer profiles, field mappings, and AI workflows as Quivly's other CRM integrations.

| CRM | Connection | Data imported |
| - | - | - |
| **Lightfield** | Guided workspace connection | Accounts, contacts, and opportunities |
| **Monaco** | API key | Accounts, contacts, opportunities, users, and recorded meetings |
| **Octolane** | API key | Accounts, contacts, and opportunities |

## Connect Lightfield

1. Open **Lightfield → Configure** and choose **Set up integration**.
2. Connect your workspace, select the objects and fields to sync, and complete setup.
3. Review the corresponding mappings under **Data → Objects**. Available opportunity fields depend on your Lightfield workspace.
4. Open **Logs** to monitor the import. Records sync every 15 minutes.

## Connect Monaco or Octolane

1. Have an API key for the intended CRM workspace ready, then open its **Configure** tab in Quivly.
2. Choose **Connect**, enter the API key, and select the data to import. Required related objects are selected automatically.
3. Complete the verification and connection flow. Check the workspace identity shown before starting the import.
4. Review sync progress and **Logs**. After the historical import, updates sync every 30 minutes. Use **Sync now** when you need to request an update sooner.

You can change the selected objects later. Stopping an object's sync retains records already imported. Monaco meeting enrichment may wait for the recording's transcript to become available.

## Verify the customer data

Open **Customers**, select a sample account, and check its name, domain, contacts, and opportunities. Monaco meetings appear in [Communications](/customer-views/communications-tab.md) when available and linked.

Customer matching and [field mappings](/field-mappings/introduction.md) determine where records land. Check the [customer linking guide](/troubleshooting/customer-information-not-linking.md) if imported records do not appear on the expected profile. Connecting a CRM does not by itself configure health scoring or publish a Play.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.