> ## 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.

# Octolane

> Connect Octolane and configure the customer records and fields to import.

Octolane brings accounts, contacts, and opportunities into Quivly's customer profiles and AI workflows. Admins choose the objects to sync; saved mappings and account import scope determine which records become available.

## Connect Octolane

1. Have an API key for the intended Octolane workspace ready, then open **Data → Integrations → Octolane → Configure**.
2. Choose **Connect**, enter the API key, and select the objects to import. Required related objects are selected automatically.
3. Complete verification and check the workspace identity before confirming the connection.
4. Review sync progress and **Logs**. After the historical import, updates sync every **30 minutes**. **Sync now** requests an earlier update.

## Complete mappings and import scope

Before the first account import, have your Quivly onboarding team review and save which accounts should enter the workspace. This requires an explicit choice, including when you want **all accounts**. Connecting Octolane alone does not start a fully configured customer import.

Under **Data → Objects**, review the mappings for each selected object:

| Octolane object | Quivly object |
| - | - |
| Accounts | Customers |
| Contacts | Contacts |
| Opportunities | Opportunities |

Quivly provides native defaults for all three objects. Core identity and relationship mappings remain locked; add custom mappings for additional fields, including the custom fields shown in the raw data preview. Each object's processing requires its saved mapping. Configure accounts before dependent records.

Account import filters are managed through Quivly-assisted onboarding. The field editor does not expose filter controls, and saving field changes preserves the existing scope. See [CRM import scope](https://docs.quivly.ai/field-mappings/introduction.md#which-crm-accounts-are-imported).

## Verify and maintain

Open **Customers** and check a known account's name, domain, contacts, and opportunities. Compare important opportunity values with the source record.

You can change which objects sync. Stopping an object's sync or tightening account import conditions retains records already imported; these changes do not clean up existing customers.

If expected records are missing, review account eligibility, the saved mappings, source logs, and [customer linking](https://docs.quivly.ai/troubleshooting/customer-information-not-linking.md). Connecting Octolane does not automatically configure health scoring or publish a Play.


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