> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/hubspot/troubleshooting.md). # Fixing HubSpot sync errors When a lead can't sync to HubSpot, it shows up in **Integrations → HubSpot → Reconciliation**, grouped by error type. This article covers each error category — what it means and how to fix it. If you got here by clicking the **?** icon next to a Reconciliation error, the section below matches your error type. Jump straight to it. > **New to Reconciliation?** Read the [Reconciliation overview](/help-center/integrations/crm/reconciliation.md) first — it explains the tab, the icons, the fix-it drawer, and how retry works. The article below assumes you know that vocabulary. *** ## Authentication errors **What you'll see:** "Connection authentication credentials were incorrect at sync." **What it means:** Mobly's HubSpot connection isn't authorized anymore. This usually happens when the user who connected HubSpot changed their password, lost access, or had MFA enforced — or when HubSpot expired the OAuth token. **Fix it:** 1. Go to **Integrations → HubSpot → Connect** 2. Re-authorize the connection through HubSpot's OAuth flow, ideally with a HubSpot admin Then click refresh on the Reconciliation error to retry the failed leads. *** ## Connection errors **What you'll see:** "We can auth with the connection, but we cannot interact with the mapped objects as desired." **What it means:** Mobly can sign in, but doesn't have permission to read or write the HubSpot objects your mappings expect — usually Contacts, Companies, or a custom object. The connecting user may have lost access to one of these in HubSpot, or HubSpot may have revoked specific scopes. **Fix it:** 1. In HubSpot, confirm the user who authorized Mobly still has read + write access to Contacts, Companies, and any custom objects in your mappings 2. If access has changed, re-authorize the connection under **Integrations → HubSpot → Connect**, ideally with a HubSpot admin 3. Retry from Reconciliation *** ## Qualifier mapping is missing or out of date **What you'll see:** "X needs their mapped connections updated." **What it means:** A Mobly qualifier value can't be sent to HubSpot because it isn't mapped to anything on the HubSpot side. This often happens when a new qualifier value is added in Mobly but never mapped, or when the HubSpot property option it was mapped to was deleted. **Fix it:** 1. Click the **wrench icon** on the error row in Reconciliation — it opens a "Fix Value Mapping" drawer with the affected qualifier ready to edit 2. Map the unmapped value(s) to the right HubSpot property option 3. Save Or do it manually under **Integrations → HubSpot → Qualifiers**: find the qualifier, open its **Action** menu, and review every value's mapping. Then retry from Reconciliation. *** ## Object mapping is missing **What you'll see:** "Mapping is missing for X object." **What it means:** Mobly is trying to push a lead into a HubSpot object (Contact, Company, etc.) but you haven't mapped any fields on that object yet. **Fix it:** 1. Go to **Integrations → HubSpot → Mapping** 2. Find the object section flagged in the error 3. Click **Set Defaults** to auto-populate Mobly's recommended mappings, or map fields manually 4. Save Then retry from Reconciliation. *** ## Required HubSpot field is missing **What you'll see:** "Required field X is missing in the CRM" — or — "Were previously mapped but the field is now missing." **What it means:** A HubSpot property your mapping points to doesn't exist in HubSpot anymore. Usually someone deleted or renamed the property on the HubSpot side. **Fix it:** Click the **wrench icon** on the error row to open the "Fix Missing Field Mapping" drawer — pick a new HubSpot field to map to, or clear the mapping if you no longer need it. If the field was deleted in HubSpot by mistake, you can also recreate it: in HubSpot, go to **Settings → Properties** and add the property back with the original internal name. Then retry from Reconciliation. *** ## Data is too long for the field **What you'll see:** "Exceeded the X field limit." **What it means:** A value Mobly is sending (job title, company name, notes, etc.) is longer than the character limit set on that HubSpot property. **Fix it:** Click the **wrench icon** on the error row to open the "Fix Field Length" drawer — pick a different Mobly field to map (one whose values fit), or clear the mapping if you don't need this field synced. If you'd rather keep the mapping as-is, change the HubSpot property's character limit instead: in HubSpot, **Settings → Properties → find the property → raise the limit** or change the property type to Multi-line text (up to 65,536 characters). Then retry from Reconciliation. *** ## Data format conflict **What you'll see:** "Data format conflict with the X." **What it means:** A value Mobly sent doesn't match the format HubSpot expects for that property — most common with URL fields, phone numbers, and dates. **Common example:** A LinkedIn URL field gets just a username (`jdoe123`) instead of a full URL (`https://linkedin.com/in/jdoe123`). HubSpot rejects it. **Fix it:** Two paths. * **Click the wrench icon** on the error row to open the "Fix Data Format Mapping" drawer — useful when the right answer is to remap to a different HubSpot field that accepts the format you're sending. * **Click the Log button** on the affected lead to see the exact value Mobly tried to send. If the data itself is wrong (typo'd URL, malformed phone), correct it on the lead in **My Leads**. Then retry from Reconciliation. *** ## Value isn't valid in HubSpot **What you'll see:** "Value sent for X is not valid in the CRM." **What it means:** The value Mobly sent isn't one of the allowed options for that HubSpot property. Most common with picklist (dropdown) properties — Mobly sent a value that doesn't exist as an option in HubSpot. **Fix it:** 1. In HubSpot, go to **Settings → Properties** and find the property 2. Either add the missing option in HubSpot, or update Mobly's qualifier mapping so it sends one of the existing options under **Integrations → HubSpot → Qualifiers** Then retry from Reconciliation. *** ## Not enough data to sync **What you'll see:** "Not enough data to meet X requirement." **What it means:** A field required for the sync (usually email) is missing or hasn't been enriched yet. HubSpot needs this to create or update the contact. **Fix it:** Depends on enrichment state. **If enrichment is still in progress:** Most leads enrich within minutes. Wait, then click refresh on the Reconciliation error to retry. If the field is populated, the lead clears. **If enrichment finished and the data is still missing:** 1. Open the lead in Mobly (**My Leads**) 2. Manually fill in the required field 3. Retry from Reconciliation If a high percentage of leads are hitting this for the same field, the requirement may be too strict for the data you're capturing. Talk to your CSM about adjusting Mobly's enrichment requirements or making the HubSpot field optional. *** ## Legacy integration errors **What you'll see:** "Legacy integration error." **What it means:** The error came from the older (legacy) HubSpot integration that Mobly is deprecating. **Fix it:** Move to the new HubSpot integration — see [Migrating from the legacy integration](/help-center/integrations/crm/migrating-from-legacy.md). After migrating, click refresh on the Reconciliation error — successful resyncs land in Cleared. *** ## Unexpected errors **What you'll see:** "Unable to sync due to an unexpected error not yet categorized." The category label may show as either **UNHANDLED\_ERROR** or **UNCATEGORIZED** — both mean the same thing for you. **What it means:** HubSpot returned an error pattern Mobly hasn't seen before, so it can't suggest a self-serve fix. These errors get grouped here so the Mobly team can categorize them and add specific fixes in future releases. **Fix it:** 1. Click the **Log** button on the affected lead and copy the error response 2. Send it to your CSM with the Lead ID The Mobly engineering team uses these reports to add new error categories with specific fixes — so the next person hitting the same issue gets a self-serve answer. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/hubspot/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.