> ## Documentation Index > Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshoot CRM sync and lead intake > Why leads do not arrive or do not sync: connection vs configuration vs execution, expired token, paused input door, routing rules, agent paused, webhook URL or token, field mapping to Variables, output stage trigger for HubSpot, Zoho, GoHighLevel, Odoo, Google Sheets and custom webhooks. How to find out why leads from a CRM, a form or the API don't arrive, arrive in the wrong place, or don't update the CRM. Last verified: 2026-09-25. ## Three separate checks A CRM can fail at three different levels. Check them in this order and don't treat one as proof of the next: | Check | The question | Where to look | | ----------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | **Connection** | Can Nexor sign in to the CRM account? | **Integrations** → the CRM. The agent's **Lead source** also shows a status per source. | | **Configuration** | Are routing, field mapping and outputs set for the right agent and task? | The agent's **Lead source** → the CRM row, which opens its configuration for that agent. | | **Execution** | Did a specific import or sync actually run and produce the result? | The import history or last run of the input door or route, and the lead's timeline. | A connected account doesn't prove that leads sync. A queued job or a preview is not a finished import. Connect and authorize a CRM only from its connection screen. Never paste API keys, passwords, tokens or private receiving URLs into a support conversation. ## By symptom | Symptom | Check first | What to do | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | | Leads don't arrive | The input door or route is on and not paused; it points to a task; that task is live; the last run matches the schedule. | Turn the door or route back on, pick the task, and **Set live** the task. A lead in a paused task waits until the task is live. | | Leads arrive in the wrong task | The route or door's target task, and the fallback route used when nothing else matches. | Change the target task in the source's configuration. | | Fields stay empty | The CRM field is mapped to lead data, and that data is mapped to the task's **Variables**. | Map the field. A value the lead gives in the conversation takes priority over data from the CRM. | | The CRM isn't updated when a lead reaches a stage | The output is configured for that task and that stage. For Zoho, the stage condition. | Configure the output for the stage. See the CRM's guide. | | The source shows **Needs attention** or the connection expired | The credential was revoked or expired in the CRM. | Reconnect from **Integrations**. | | Leads from your own form or system don't arrive | The request reaches the right URL or API key, with the right token and fields. | Check the input door in **Custom connection**, or the request to the API. | ## By CRM | CRM | How leads come in | How often | What Nexor sends back | | --------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | | **HubSpot** | Input doors: lists, real-time contacts, or a one-time import of the portal or specific contacts. | Each list door checks every 30 minutes to 2 days (default 1 hour). New contacts in a connected list can arrive in seconds. | The results you configure as outputs for each task. | | **GoHighLevel** | Routes by pipeline or by GoHighLevel workflow, with a fallback route. Real-time webhook, and optional **Auto-sync**. | **Auto-sync** checks open opportunities every 10 minutes. | Final outcomes mapped to a GoHighLevel status or stage. | | **Zoho CRM** | Zoho is mainly an output. | When the lead reaches the configured point. | Leads and, per task, existing organizations (Accounts). | | **Kommo** | Routes from the pipelines and stages you choose to a task. | As Kommo sends them. | See the Kommo guide. | | **Odoo** | Imports of the teams, stages and record types you choose. | Manual or periodic imports, with history. | Nothing: the connection is read-only. | | **Google Sheets** | **Import** automations read a tab of a spreadsheet. | Checked about every 5 minutes. | See the Google Sheets guide. | | **Custom connection** | Input doors: an incoming webhook (one fixed task) or an API key. | As your system sends them. | Outgoing webhooks, Cloud Functions and tools. | | **API** | `POST` a lead with the task's id. | Right away. | Webhooks for the events you subscribe to. | ## HubSpot details * Each list door can be turned off without deleting its configuration. **Pause when contact leaves list** is a separate option. * Map HubSpot properties in **How your data lands** before importing, and again when properties change in HubSpot. * A connection can't be switched to a different HubSpot portal: disconnect first. * HubSpot workflows that call Nexor must send the token in the `x-nexor-hubspot-token` header. A token in the URL is no longer accepted. ## Zoho: create leads only from certain stages Yes, it's possible. In the task's Zoho output, turn on **Create the lead in Zoho only when it reaches certain stages** and choose the stages. Without that option, the output follows its default trigger. ## GoHighLevel details * **Auto-sync** covers the pipelines you select that already route to a live task. * A route can be paused and resumed without deleting it. Each import keeps a run history. ## Ask Nexor AI to check it for you In the agent's chat, you can ask for a read-only check before changing anything: * "Show the HubSpot connection and incoming routing for this task. Don't change anything." * "Which CRM fields fill this task's Variables?" * "Check the latest import and explain why this lead didn't sync." ## Related guides * [Integrations overview](/docs/en/guides/integrations/overview) * [HubSpot](/docs/en/guides/agents/leads/hubspot), [Kommo](/docs/en/guides/agents/leads/kommo), [GoHighLevel](/docs/en/guides/integrations/gohighlevel), [Zoho](/docs/en/guides/integrations/zoho), [Odoo](/docs/en/guides/integrations/odoo), [Google Sheets](/docs/en/guides/integrations/google-sheets), [Custom connection](/docs/en/guides/integrations/custom-connection) * [Add leads by API](/docs/en/guides/agents/leads/api) * [Settings scope: account, agent and task](/docs/en/support/settings-scope)