Connect Octolane
- Have an API key for the intended Octolane workspace ready, then open Data → Integrations → Octolane → Configure.
- Choose Connect, enter the API key, and select the objects to import. Required related objects are selected automatically.
- Complete verification and check the workspace identity before confirming the connection.
- 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:
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.
