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

# Monaco

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

Monaco can bring accounts, contacts, opportunities, users, and recorded meetings into Quivly. Admins choose the objects to sync; saved mappings and account import scope determine which records become available.

## Connect Monaco

1. Have an API key for the intended Monaco workspace ready, then open **Data → Integrations → Monaco → 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**. A connected CRM can have received source records while customer processing is still waiting for setup.

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

| Monaco object | Quivly object |
| - | - |
| Accounts | Customers |
| Contacts | Contacts |
| Opportunities | Opportunities |
| Users | External Users |
| Meetings | Call Recordings |

Quivly provides native defaults for all five objects. Core identity and relationship mappings remain locked; add custom mappings for additional fields. Each object's processing requires its saved mapping. Configure accounts before dependent records.

Account import filters are managed through Quivly-assisted onboarding, separately from the field editor. The Objects editor does not offer import-filter controls. Ask your Quivly team to complete or change that scope. Ordinary field-mapping saves preserve the existing rule. See [CRM import scope](https://docs.quivly.ai/field-mappings/introduction.md#which-crm-accounts-are-imported).

## Verify and maintain

Check a known customer, its linked contacts and opportunities, and available meetings in [Communications](https://docs.quivly.ai/customer-views/communications-tab.md). Meeting enrichment can wait for a transcript to become available.

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 the saved mappings, account eligibility, source logs, and [customer linking](https://docs.quivly.ai/troubleshooting/customer-information-not-linking.md). Connecting Monaco 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.