The Sales Navigator card does not appear on the contact record
WhyEither the seat is on Sales Navigator Core, or the per-user app install never happened. Embedded Profiles needs Advanced or Advanced Plus and an install by each user, not just by the admin.
Check the edition on the seat, then have that user install the LinkedIn Sales Navigator app from the HubSpot App Marketplace themselves.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
InMails and messages are not reaching the timeline
WhyLinkedIn is not selected in the activity filter. The writeback arrives on the record and the timeline hides it.
On the contact record, open Filter activity and tick LinkedIn. Check one rep who has definitely sent an InMail since go-live.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
Writeback works for some reps and not others
WhyActivity writeback and contact creation need each user to authenticate with the CRM individually. Admin authentication does not cover them.
Send the reps who are missing to Sales Navigator, Settings, CRM Settings, Connect to CRM. Confirm the admin has enabled writeback for the contract, because user authentication only appears once that is on.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
A rep cannot update a HubSpot contact from Sales Navigator
WhySales Navigator respects HubSpot permissions. Without read and write access to that record in the CRM, the update is refused on the LinkedIn side.
Fix the permission in HubSpot rather than in Sales Navigator. This is also the first thing to check when a correctly licensed Advanced Plus install appears to do nothing.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
The pairing will not complete
WhyA LinkedIn Business Manager connection is already in place, or the HubSpot account is paired to a different Sales Navigator environment. Only one pairing exists at a time.
Disconnect Business Manager, complete the Sales Navigator sync, then reconnect it. If a sandbox was paired for testing, release it before pairing production.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
The CRM filled up with duplicate contacts
WhyContact creation from Sales Navigator writes a new record whenever no match is found, and a rep working a list will not stop to look for the match.
Require an email address and an account association on creation, keep HubSpot duplicate management running, and train reps to use Find CRM record before Create new CRM record. This is the failure mode practitioners raise most often.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
Two years of LinkedIn history is missing
WhyThere is no backfill. Only new and updated data syncs after go-live.
Uninstalling and reinstalling the app resets the sync and sends every record again, which is documented rather than a support trick. Decide this before the first report, not after.
On HubSpot and LinkedIn, which needs a plan upgrade on one side
Contact fields populate and company fields do not
WhyCompany mapping is configured in the same place and behaves independently, and practitioners report exactly this asymmetry with mappings that look correct in the Admin Portal.
Check the connecting account's permissions on companies specifically, not just on contacts, then re-test with a single company export.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
Exports reach fewer records than expected
WhyThe connecting account is on the minimum permission of records they own rather than all records.
Raise the permission to the recommended level on both contacts and companies. ZoomInfo documents both the minimum and the recommendation, and the gap between them is silent.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
Duplicates are piling up after exports
WhyThe admin left the create-a-duplicate option available, and reps in a hurry take it.
Restrict the duplicate options in the Admin Portal so updating the existing record is the path of least resistance.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
The integration broke when somebody left the company
WhyIndividual user account connections tie the integration to people.
Move to the service account connection, which ZoomInfo describes as the default and preferred option for exactly this reason.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
Nobody authorised ZoomInfo to read the CRM
WhyHubSpot Import is enabled by default and allows ZoomInfo to import and analyse information from HubSpot about your team and your prospects and customers.
Decide it deliberately and record who decided. This is a data-sharing setting rather than a performance one, so the person to ask is not the CRM admin.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
Reps complain the data overwrote their notes
WhyExport behaviour on those field mappings.
Change the behaviour per field. The mapping screen allows it and the default is not always what a rep would choose.
On HubSpot and ZoomInfo, which needs a plan upgrade on one side
There is no webhook action in the workflow editor
WhyBoth the webhook action and the custom code action require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. Workflows themselves are a Sales Hub feature and reaching outside them is not.
Price the hub against Clay and n8n before buying it. Full CRM API access is on every tier including the free one, so an external route reads and writes the same records without the upgrade.
On HubSpot and Reverse Contact
The custom code action timed out
WhyAn action must finish within 20 seconds and inside 128 MB of memory, and HubSpot returns an error on exceeding either.
Use the cached endpoints, which publish a 500ms P95. Arriving near 20 seconds means you are either calling a live endpoint, which answers with a task rather than a record, or looping over records inside one action.
On HubSpot and Reverse Contact
One contact was written another contact's job title
WhyHubSpot documents that variables declared outside exports.main may be re-used by future executions of the action, to save memory, and many objects can be enrolled at the same moment.
Move every variable holding anything about a person inside exports.main. Only a connection you intend to re-use belongs outside it, which is the case the caveat was actually written for.
On HubSpot and Reverse Contact
Some contacts were quietly left un-enriched
WhyA rate-limited call is only retried if the error is thrown. HubSpot documents that in Node.js you must throw it in the catch block, and in Python raise it in the except block.
Re-throw on a 429 instead of returning a no_match. A swallowed rate limit looks exactly like a real miss in the workflow history, which is what makes this one expensive to find later.
On HubSpot and Reverse Contact
A property a rep maintained has been overwritten
WhyNothing in this build decides that for you. The API returns a record and the property it lands in is whichever one your action names.
Write to prefixed properties only, then promote a value into a human-maintained property with a separate workflow that fires only where the human property is empty.
On HubSpot and Reverse Contact
The workflow reports success and the property is empty
WhyReverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody completes normally rather than failing.
Return a match status from callback() as its own output field and branch the workflow on it. The call itself cost nothing, because every 4xx and 5xx is free.
On HubSpot and Reverse Contact
Everything stopped at once, including the calls that were free
WhyBelow 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Read quotas.workspace.credits.left from any response and alert on it. GET /v2/usage keeps answering when the checks do not, so a balance check never fails for the reason the lookup did.
On HubSpot and Reverse Contact
An endpoint that worked last week returns nothing
Why/v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026.
Open the custom code action and change the path. A workflow action is not version-controlled by default, so the only copy of that string is the one inside it, and nothing will warn you.
On HubSpot and Reverse Contact
The workflow created the task but every field is empty
WhyCustom field mapping is not supported in HubSpot workflows. Only Deal tokens in the name and description carry anything across.
Put the values you need into the description as tokens, and build real field mapping as a ClickUp Automation instead.
On HubSpot and ClickUp, which needs a plan upgrade on one side
A field will not map even inside an Automation
WhyMapping is type to type. A HubSpot email field maps only to a ClickUp Email custom field, and there is no conversion.
Create the matching custom field type in ClickUp first, then map. Renaming does not help, the type does.
On HubSpot and ClickUp, which needs a plan upgrade on one side
The second automation in a chain never fires
WhyAn object created by a HubSpot Automation does not trigger another HubSpot Automation.
Collapse the chain into one automation, or trigger the second step from something a person does rather than from something an automation made.
On HubSpot and ClickUp, which needs a plan upgrade on one side
Nobody can authenticate the integration
WhyClickUp requires a Workspace owner or admin to connect HubSpot.
Get the Workspace owner to do the App Center step. It takes a minute and cannot be delegated by permission alone.
On HubSpot and ClickUp, which needs a plan upgrade on one side
ClickUp is full of Spaces nobody meant to create
WhyThe workflow action offers to create a Space, Folder or List as well as to pick one, and a trigger that fires on every deal will keep taking it.
Point actions at existing Lists, and decide the naming pattern before the workflow goes live rather than after a quarter of deals have run through it.
On HubSpot and ClickUp, which needs a plan upgrade on one side
The HubSpot source and the object actions are not there
WhyThe workspace is on Free or Launch. Clay's plan comparison marks CRM integrations as included from Growth, and nothing in the HubSpot integration documentation repeats it.
Check the plan before debugging the connection. There is no partial version of this on a lower tier, so the decision is a purchase rather than a setting.
On HubSpot and Clay, which needs a plan upgrade on one side
Connecting fails with an unexpected error during the app authorization process
WhyOne of the three custom object scopes was switched on against a portal below Enterprise. HubSpot cannot grant them there, and the authorisation stops rather than proceeding without them.
Reconnect with all three off, which is how they arrive. Reconnecting keeps whatever was enabled last time, so an Enterprise portal that already has them on holds onto them.
On HubSpot and Clay, which needs a plan upgrade on one side
The List dropdown shows an error asking you to reconnect
WhyThe connection does not carry the create and edit lists permission. HubSpot asks for it by default, so this is a connection somebody made with it unticked.
Reconnect the account and select that scope. It is the same flow and the rest of the permissions are unaffected.
On HubSpot and Clay, which needs a plan upgrade on one side
A row ran, HubSpot accepted it, and the record is not in the list
WhyAdded to list came back false. Clay documents that as HubSpot taking the request and declining the record, because it is already a member or is not eligible for that list.
Read the output rather than the row status. A record ID that does not exist in the portal fails the row instead, which is a different signal and a different fix.
On HubSpot and Clay, which needs a plan upgrade on one side
The write created a second copy of a record that already existed
WhyCreate was used where Update was meant. Create has no record ID input and no matching step, so it writes a new object every time it runs.
Use Update keyed on the HubSpot Object ID for anything that came out of an import. Clay puts that ID at the top of the Look up filter list for the same reason: it is the only precise match on offer.
On HubSpot and Clay, which needs a plan upgrade on one side
A populated HubSpot property came back blank after a run
WhyIgnore blank values was turned off on the Update action. With it off, a blank Clay cell is sent through and overwrites what HubSpot had.
Turn it back on, and keep the properties your reps maintain out of the write entirely. It is on by default, so this is a setting somebody changed on purpose.
On HubSpot and Clay, which needs a plan upgrade on one side
A company domain lost its subdomain on the way in
WhyKeep subdomains in Company domain is off by default, so shop.example.com is reduced to example.com before the write lands.
Switch it on in the Create or Update action, and separately in Look up if you are filtering on a subdomain. The two switches do not follow each other.
On HubSpot and Clay, which needs a plan upgrade on one side
Credits went roughly twice as far as the row count suggested
WhyDuplicate records in HubSpot arrived as separate rows and every provider ran against both. Actions bill on the attempt, so a duplicate costs exactly what a match costs.
Measure the portal's duplicate rate before the first run and filter the import to the records you mean to pay for. This is the most expensive failure on this pair and all of it happens outside Clay.
On HubSpot and Clay, which needs a plan upgrade on one side
A private channel does not appear when associating a record
WhyThe HubSpot app is not a member of it. Associations only work with public channels and private channels the app has been added to.
Add the app in that Slack channel, then refresh the record. No HubSpot setting substitutes for it.
On HubSpot and Slack, which needs a plan upgrade on one side
The workflow posts to the wrong room
WhyThe Slack workflow action takes a static channel. It cannot resolve the channel associated with the record being processed.
Use the record association for per-deal messages, or branch the workflow and give each branch a fixed channel. The second only scales to a handful of channels.
On HubSpot and Slack, which needs a plan upgrade on one side
A deal lost its channel after a merge
WhyThe Slack channel association comes from the primary record in a merge.
Associate the channel with the record you will keep as primary before merging, or choose the record that already has it as the primary.
On HubSpot and Slack, which needs a plan upgrade on one side
Notifications arrive for one person and not the team
WhyPersonal notification settings are per user, under Settings, Notifications, Other apps.
Tell people to turn their own on. An admin cannot do it for them, which makes this a rollout communication rather than a configuration task.
On HubSpot and Slack, which needs a plan upgrade on one side
The channel is noisy and now everybody has muted it
WhyEvery activity type was ticked when the channel was associated.
Re-open the association and uncheck everything that is not acted on. A muted channel is worse than no channel, because the team believes alerting works.
On HubSpot and Slack, which needs a plan upgrade on one side
Nothing from a shared channel with a customer is in the CRM
WhySlack Connect conversations are not covered.
There is no setting. Either keep deal discussion in an internal associated channel, or accept that the customer-facing thread is outside the record.
On HubSpot and Slack, which needs a plan upgrade on one side
One object syncs and another does not
WhyThe connected user cannot see it. HubSpot performs every action through that user's permissions, so an object outside their profile is invisible in both directions.
Log in as the connected user and look. Then add Modify All on that object to their profile rather than widening the integration settings.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Everything broke after somebody changed the connected user
WhyThe replacement has narrower permissions, or belongs to a different Salesforce production org.
Give the new user permissions equal to or greater than the old one, in the same org. Treat the connected user as infrastructure rather than as somebody's login.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Records sync once, then stop
WhyWith selective sync, a record has to keep meeting the sharing rule. HubSpot warns specifically that records the integration itself creates in Salesforce will stop syncing unless they also match the criteria.
Write the sharing rule so records created by the integration satisfy it, then test with a form submission rather than with a hand-made record.
On HubSpot and Salesforce, which needs a plan upgrade on one side
A record never arrives in HubSpot at all
WhyNo valid email address. HubSpot documents that those do not sync.
Check the email field before suspecting the mapping. If you need the record anyway, it has to arrive by another route.
On HubSpot and Salesforce, which needs a plan upgrade on one side
The sync looks slow or stuck
WhySalesforce to HubSpot runs on a cycle of roughly 10 to 15 minutes. It is not instant and is not supposed to be.
Wait a cycle before investigating. If it is still missing after that, go to the connected user's permissions first.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Salesforce API limits are being eaten
WhyHubSpot sets its API usage from your Salesforce limit, and a single contact sync can take up to four API calls per record, varying with what changed.
Size the limit against your Salesforce allowance rather than against record count, and use an inclusion list or selective sync to stop syncing records nobody needs.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Custom objects will not sync
WhyCustom object sync is HubSpot Enterprise only, and the HubSpot object needs at least one required field.
Check the tier first, then the required field. Both are cheaper to check than the mapping screen is to debug.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Field mappings disappeared after a Salesforce migration
WhyMappings survive a move to a new production org only where the Salesforce field keeps the same internal name.
Match internal names before the cutover, or plan to rebuild the mappings and budget for it.
On HubSpot and Salesforce, which needs a plan upgrade on one side
Syncing started before anybody was ready
WhyThe six-hour configuration window expired and Apollo enabled syncing automatically.
Adjust the settings now, in Settings, Integrations, HubSpot. The settings stay editable; what you cannot undo is the first run.
On HubSpot and Apollo, which needs a plan upgrade on one side
Contacts arrived that should have been filtered out
WhySomebody pushed them manually. Apollo documents that a manual push overrides the sync settings, including stage restrictions.
Treat the conditions as a default rather than a control, and train the team on what the push button on a profile actually does.
On HubSpot and Apollo, which needs a plan upgrade on one side
One admin owns every contact Apollo created
WhyThe pushing users have not linked their personal HubSpot credentials in Apollo, so ownership falls to the shared authentication.
Have each rep link their own credentials. Reassigning afterwards is possible and tedious.
On HubSpot and Apollo, which needs a plan upgrade on one side
Every Apollo contact has the same source
WhyThe source field defaults to Apollo and was never changed.
Point it at the field your reporting uses, and pick the picklist value if that field is a picklist.
On HubSpot and Apollo, which needs a plan upgrade on one side
A push silently did nothing
WhyIt failed, and the failure lives in the integration views rather than on the record.
Open Error logs under Contacts or Accounts, then Push, and retry from there. Queue activity shows what is still waiting.
On HubSpot and Apollo, which needs a plan upgrade on one side
The integration is not available at all
WhyApollo's free plan excludes CRM integrations.
That is a plan question. The extension still works for manual research in the meantime.
On HubSpot and Apollo, which needs a plan upgrade on one side
The first trigger stopped firing when a second one was activated
WhyHubSpot allows one webhook. n8n registers it on activation, and activating another trigger takes the registration with it.
Run one trigger node and branch inside the workflow. If two workflows genuinely need the same event, have the first one call the second.
On HubSpot and n8n
Authentication credentials not found. This API supports OAuth 2.0 authentication
WhyA developer API key was used against a test account. HubSpot documents that developer API keys do not work for test accounts.
Use OAuth or a private app token for anything pointed at a test account. This is also worth knowing before you build the whole workflow against a sandbox.
On HubSpot and n8n
A self-hosted instance never receives the webhook
WhyHubSpot has to reach n8n over a valid HTTPS endpoint. An instance behind a self-signed certificate or no public address looks correctly configured from inside n8n and receives nothing.
Put it behind a real certificate. Practitioners on r/n8n report a Cloudflare tunnel fixing exactly this after every guide had been followed.
On HubSpot and n8n
A form submission arrived without the file somebody uploaded
WhyHubSpot's webhook sends text fields. The file is not in the payload and never was.
Call HubSpot's API from n8n with the HTTP Request node to fetch the file URL. That call needs a token, so the webhook alone will not do it.
On HubSpot and n8n
OUTPUT_VALUES_TOO_LARGE from a HubSpot custom code action
WhyA string data output exceeded 65,000 characters. This is the HubSpot side of the pair rather than the n8n side, and it is the usual reason a working action starts failing on one record.
Truncate or split the output. Remember the harder ceilings on the same action: 20 seconds of runtime, 128 MB of memory, and a maximum of 50 properties passed in.
On HubSpot and n8n
This action has been paused to stay within the configured rate limit
WhyRate limiting was turned on for a HubSpot custom code action. It is off by default, and when on it also delays every action after it in the workflow.
Read the workflow action log, which names the resume time. If the limit is not what you wanted, it is configured per action under Configure rate limit rather than globally.
On HubSpot and n8n
A retry never happens after a 429
WhyHubSpot only retries a custom code action if the error is thrown. Catching it quietly means HubSpot treats the execution as a success.
Throw the error in the catch block in Node.js, or raise it in the except block in Python. Swallowing it is the behaviour that turns a transient limit into missing data.
On HubSpot and n8n
The node does not have the operation the workflow needs
WhyThe HubSpot node covers seven resources and no custom objects. That is the documented scope of it rather than a gap to work around.
Use the HTTP Request node on the same credential, which is n8n's own recommendation. Everything HubSpot exposes is reachable that way, and the authentication is already configured.
On HubSpot and n8n
Every Zap broke at once and nothing changed on your side
WhySomebody added a second Zapier connection to the same HubSpot account, which invalidates the previous one.
Reconnect, then agree who owns the connection. There is no way to run two, so this is a people problem with a technical symptom.
On HubSpot and Zapier
Dates arrive a day early, or at midnight
WhyHubSpot takes dates as UNIX timestamps and Zapier rounds date-time values down to UTC midnight.
Store the precise value in a separate property if you need it. Nothing in the mapping screen prevents the rounding.
On HubSpot and Zapier
The list you want is missing from Add Contact to List
WhyIt is an active list. Only static lists appear.
Write a property instead and let an active list pick the contact up by rule, which is what active lists are for.
On HubSpot and Zapier
The Zap is slow and it is not Zapier's fault
WhyA polling trigger on an account without polling control, or an app-imposed minimum interval.
Switch to an instant trigger if one covers your event. Deal Property Change is instant; most of the created-or-updated triggers are not.
On HubSpot and Zapier
Original source reporting is full of Zapier
WhyA record created by an automation is attributed to that automation.
Create the contact through the native form or the Forms API where attribution matters, and use the Zap for everything after creation.
On HubSpot and Zapier
Requests start failing in bursts
WhyHubSpot allows 190 requests per 10 seconds regardless of tier, so a Zap that fans out hits the rate limit before the daily cap.
Add a delay step or batch the work. A HubSpot upgrade raises the daily ceiling and leaves the burst limit where it was.
On HubSpot and Zapier
A scope needs removing and there is no way to do it
WhyMake states that once scopes are added to a connection they cannot be removed.
Create a new connection with only the scopes you want and repoint the scenarios at it. Treat an experimental connection as disposable from the start.
On HubSpot and Make
Watch Notifications never fires
WhyThe scopes are needed in two places with two different names: on the HubSpot custom app and again as connection custom scopes in Make.
Check both against Make's subscription table. A module missing one of the pair does not error, it simply never triggers, which is why this is hard to spot.
On HubSpot and Make
A subscription needs adding to an existing webhook module
WhyMake warns that the Subscriptions field cannot be updated at a later time.
Rebuild the module with the full list. This is the one setting on this pair worth over-specifying at the start.
On HubSpot and Make
A second webhook will not attach to the custom app
WhyEach HubSpot custom application can be associated with only one webhook URL.
Add more subscriptions to the existing webhook rather than creating a second one, or create a separate custom app if your HubSpot subscription allows another.
On HubSpot and Make
The OAuth redirect fails on the advanced connection
WhyThe Redirect URL has to be exactly https://www.integromat.com/oauth/cb/hubspotcrm, which is the pre-rename domain and looks wrong to anybody who knows Make by its current name.
Use it as documented, and leave the Install URL blank. Typing the make.com equivalent is the obvious mistake here.
On HubSpot and Make
Make an API Call returns a permissions error
WhyMake cannot infer the scopes for an arbitrary endpoint, so this is the one module where you select them yourself.
Add them under Connection, Custom Scopes in the module settings, remembering that they then cannot be removed from that connection.
On HubSpot and Make
A contact cannot be subscribed to an email address
WhyMake documents it as a plain constraint: you cannot subscribe a contact to an email address that is already subscribed.
Check the subscription state first and branch, rather than treating the error as a failure to handle.
On HubSpot and Make
Somebody else's HubSpot integration started hitting limits
WhyHubSpot's daily API cap is shared across every app in the account, and a Make scenario looping record by record spends from the same pool.
Batch where the modules allow it, and check API call usage in HubSpot under Development, Monitoring. The burst limit is per app; the daily one is everybody's.
On HubSpot and Make
Prospects are missing and nothing failed
WhyThey have no email address. HubSpot matches contacts on email and excludes records without one by default.
Open the Excluded column on the sync. These are listed there rather than raised as errors, which is why nobody finds them.
On HubSpot and Outreach, which needs a plan upgrade on one side
Opens and clicks are missing for some people
WhyEvent sync only applies to contacts HubSpot already holds, so engagement on a prospect who has not synced yet has nowhere to land.
Get the contact across first. The events do not backfill once it arrives.
On HubSpot and Outreach, which needs a plan upgrade on one side
A rep insists they emailed somebody and neither system shows it
WhyThey sent it from a mail client without the Outreach extension. Only email sent through Outreach or through a client running the extension reaches HubSpot.
This is a training and extension-deployment problem rather than a sync one. Nothing flags the gap.
On HubSpot and Outreach, which needs a plan upgrade on one side
The initial sync seems to have started over
WhySomebody saved the configuration again. HubSpot restarts the full index when you do.
Decide the configuration, save once and wait. Several days is documented for large record counts.
On HubSpot and Outreach, which needs a plan upgrade on one side
A filter is not keeping records out
WhyFilters limit which records sync initially. A record already synced keeps syncing on its field mappings regardless.
Filter before the first pass, or unsync the records individually. Changing the filter later does not reach back.
On HubSpot and Outreach, which needs a plan upgrade on one side
A field will not map
WhyIt is not a standard mapping, and custom field mappings need a Data Hub subscription.
Confirm by building the mapping, which you can do without the subscription. If it needs Data Hub, price that before committing to a go-live date.
On HubSpot and Outreach, which needs a plan upgrade on one side
Every meeting appears twice in HubSpot
WhyCalls are being exported as HubSpot meetings while HubSpot is also syncing Google Calendar. Gong documents this combination as producing duplicate meetings.
Export as calls or notes instead. Note that changing the type does not convert the records already there, so you will be cleaning up the first batch by hand.
On HubSpot and Gong, which needs a plan upgrade on one side
Telephony calls appear twice
WhyAll calls was selected while another application also exports calls to HubSpot. All calls covers telephony calls imported into Gong as well as Gong Dialer ones.
Switch to Gong Dialer calls only. This narrows what Gong claims rather than disabling the other tool, which is usually the easier conversation.
On HubSpot and Gong, which needs a plan upgrade on one side
A call happened and nothing is on the record after an hour
WhyNothing is wrong. Gong documents that exporting its data to HubSpot can take up to six hours.
Wait, then read the CRM export status report rather than the timeline. It distinguishes failed from not yet exported, which the record cannot.
On HubSpot and Gong, which needs a plan upgrade on one side
A meeting created no HubSpot activity at all
WhyNo external participant matched a HubSpot record. Gong requires at least one match before it creates an activity from a meeting invite.
Check whether the attendee exists in HubSpot with that email. This is also why Gong distinguishes participants, who joined, from attendees, who joined and have a contact record.
On HubSpot and Gong, which needs a plan upgrade on one side
One imported field is permanently empty in Gong
WhyThe field type is unsupported or the format is wrong. Multiple checkboxes, file fields and HubSpot user fields are not imported at all, and date fields have to be epoch in milliseconds.
Check the type before the mapping. A long single-line text or dropdown value is a different case: those import and display only the first 120 characters.
On HubSpot and Gong, which needs a plan upgrade on one side
A rich text field lost its formatting after somebody edited it in Gong
WhyRich text has limited support. It displays without formatting, and an edit made in Gong writes back to HubSpot without it.
Keep rich text fields out of the imported set if anybody edits in Gong. The flattening is not recoverable from the HubSpot side.
On HubSpot and Gong, which needs a plan upgrade on one side
The integration stopped working and nobody changed anything
WhyThe connecting HubSpot user was deactivated, which is what the dedicated integration user recommendation exists to prevent.
Reconnect with a service account rather than reactivating the person who left. Remember Gong sees exactly what that account sees, so check its permissions rather than assuming parity.
On HubSpot and Gong, which needs a plan upgrade on one side
Do not contact in Gong Engage never reaches the HubSpot contact
WhyThe opt-out permission is a separate authorisation, in addition to the regular integration permissions.
Click Give permission under Enable update of opt out field in HubSpot and sign in as the integration user again. Only relevant if you have Gong Engage, and a compliance problem rather than a cosmetic one if you do.
On HubSpot and Gong, which needs a plan upgrade on one side
A campaign is running and HubSpot cannot be switched on
WhySmartlead states the campaign-level integration can only be set up while creating the campaign and not midway through an active one.
Either recreate the campaign, or build a SmartAgent instead, which works against campaigns that already exist. The second is almost always the better answer.
On HubSpot and Smartlead
The CRM is connected and no campaign is syncing
WhyConnecting HubSpot to the Smartlead account does not sync it with any campaign. It has to be enabled per campaign, every time.
Enable the toggle in each new campaign's creation flow, and select the HubSpot list and group while you are there.
On HubSpot and Smartlead
HubSpot shows as disconnected after authorising
WhySmartlead lists this as its first troubleshooting case: the OAuth account may lack the necessary CRM permissions.
Re-authorise from SmartAgents, Integrations, with an account that has CRM permissions. Tool connections are one-time otherwise and do not need periodic reconnection.
On HubSpot and Smartlead
The Configuration Required notice will not clear
WhySlack is the usual culprit. The SmartAgents app has to be present in the target channel before the agent can be deployed.
Add the app to the channel using the in-app link, then return to the workflow. Connecting Slack as an integration is not the same as adding it to the channel.
On HubSpot and Smartlead
The agent ran and the contact is not in HubSpot
WhyThree documented causes: check the run logs for that execution, confirm the lead has a valid email address, and confirm the HubSpot OAuth connection is still active.
Work through all three in that order. The email is the match key for the upsert, so a lead without one cannot produce a contact.
On HubSpot and Smartlead
The agent runs but contacts are never updated
WhyThe Upsert Contact step is not receiving the right lead data, or the connection logic between the fetch step and the HubSpot step is wrong.
Open the connector between the two steps, choose Edit Connection Logic, and check what is being passed. Reset to Default is there if you changed it and want it back.
On HubSpot and Smartlead
The trigger is wrong and cannot be changed
WhySmartlead states that event-based triggers cannot be edited after the agent is created.
Create a new agent. This is the one irreversible decision in the SmartAgents flow, so it is worth being deliberate about scope and event type before clicking Proceed.
On HubSpot and Smartlead
Nothing about replies or opens is reaching anywhere
WhyThose are webhook events rather than part of this integration: email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated.
Point them at a server. Smartlead retries failed deliveries, marks an event failed after three attempts, and exposes a Retrigger Webhooks endpoint for the failures.
On HubSpot and Smartlead
Every call shows as Connected whatever the rep marked
WhyThe status has no mapping. Either it is a custom lemlist status, or your portal's call outcomes were deleted and recreated so the default mapping targets ids that no longer exist.
Map each status explicitly in Settings, CRM, Activities, Calls. Do it for all of them rather than the ones that look wrong, because a correct-looking outcome may be a coincidence.
On HubSpot and lemlist
Opens and clicks are nowhere in the Email object
WhyHubSpot does not allow third-party applications to write open and click data to its dedicated email objects. lemlist stores them as Notes because that is the only place available.
Look in Notes, and filter the Activity tab by type to find them. There is no configuration that moves them, and every tool in this category faces the same wall.
On HubSpot and lemlist
A field mapped last week is still empty on older contacts
WhyField mapping is not retroactive. It applies from the moment it is set, not to records already imported.
Re-import the affected leads, and from now on create the HubSpot property, map the field, then import. That order is the single most common support thread on this pair.
On HubSpot and lemlist
A contact is not being created in HubSpot at all
WhyMandatory properties are enabled and the lead does not meet the required field conditions, so lemlist declines to create the record.
Check the mandatory property rules in Advanced settings against the lead. Also confirm the lead has an email, a LinkedIn URL or a company domain, since matching needs one of the three.
On HubSpot and lemlist
Activity is landing with the wrong owner
WhyUser mapping is missing or incorrect, so the fallback owner is being used. The fallback is configured per sync direction and applies to everything unmapped.
Map the lemlist user to the HubSpot user in User Mapping, then check the Define default ownership section for each direction rather than just one.
On HubSpot and lemlist
A call has no transcript or summary on the HubSpot record
WhyNeither exists when the call ends: they arrive on a later refresh. The call may have no summary at all, or it came from Aircall or Ringover rather than lemlist calling.
Reopen the record later, confirm the call in lemlist actually has both, and check Calls transcript and Calls summary are on. Syncing never generates a summary that does not already exist.
On HubSpot and lemlist
Somebody edited a call note in HubSpot and it reverted
Whylemlist rebuilds the note on every refresh rather than merging it, so a manual edit is replaced.
Write call notes in lemlist on the call record. Also note the 65,000 character cap: longer content is cut from the end, which means the transcript goes first with no warning.
On HubSpot and lemlist
A manual unsubscribe never reached HubSpot
Whylemlist only pushes the unsubscribe when the lead unsubscribed themselves from the campaign. A lead added to the Unsubscribe section by hand is not pushed.
Handle manual opt-outs on the HubSpot side as well, as a process rather than a setting. In a team that manages opt-outs by hand this is a compliance gap rather than a nuisance.
On HubSpot and lemlist
A rep cannot connect their inbox at all
WhyA View-Only seat, or a Gmail account enrolled in Google's Advanced Protection Program. Neither is supported for an individual work email.
Check the seat type first, since it is the one you can change. Advanced Protection is a Google policy decision and there is no HubSpot setting that works around it.
On HubSpot and Google
Emails from the shared address stopped logging properly
WhyThe same account is being used as both an individual work email and a team email, which HubSpot does not allow.
Disconnect it and reconnect it as a shared inbox. Decide which it is before the rollout, because the switch loses the arrangement people have got used to.
On HubSpot and Google
Logging works and tracking does not
WhyThey are separate features. Tracking needs an assigned Sales Hub seat, and it does not work with customised Gmail layouts.
Check the seat, then have the rep turn off the custom layout in Gmail and retest.
On HubSpot and Google
An email logged against nobody
WhyIt was sent from an address that is not a user, a connected address or a configured alias.
Add the alias in the connected inbox or in Profile and Preferences. Nothing errors when this is wrong, so it has to be checked rather than waited for.
On HubSpot and Google
Opens are not registering for some contacts
WhyData privacy settings are on, and opens are only tracked for contacts with an assigned legal basis for processing.
That is a legal configuration rather than a bug. Your legal team decides the basis; the tracking follows it.
On HubSpot and Google
Meetings from the second calendar never arrive
WhyThe integration syncs one calendar.
Move the meetings that matter onto the connected calendar, or accept that the other one is invisible to the CRM.
On HubSpot and Google
The migration fails on phone numbers
WhyAttio validates country and area codes and expects the format plus country code followed by the subscriber number including the area code.
Normalise them in HubSpot before exporting. Hyphens are fine; a missing or wrong country code is not.
On HubSpot and Attio, which needs a plan upgrade on one side
Domain values are rejected
WhyAttio verifies that domains are valid and stores only the root. A full URL or a malformed prefix errors rather than being tidied up.
Strip to the root domain in HubSpot first. attio.com and www.attio.com are both accepted formats.
On HubSpot and Attio, which needs a plan upgrade on one side
Fewer people arrived than HubSpot had
WhyEmail address is the unique identifier for a person and each email can only be linked to one record, so duplicates in HubSpot merge on the way in.
Expect it and count it. If those were genuinely different people sharing a mailbox, that has to be fixed in HubSpot before the migration rather than after.
On HubSpot and Attio, which needs a plan upgrade on one side
A deal import failed with everything apparently present
WhyAttio notes that some objects, Deals among them, have required attributes that must be included for a successful import.
Check the required attributes for each object you enabled, rather than assuming the rules that worked for contacts apply.
On HubSpot and Attio, which needs a plan upgrade on one side
There are attributes in the workspace nobody created
WhyThe migration creates attributes to hold what it found. Attio tells you to review them after the sample migration and update or archive as needed.
Do that review at the sample stage. After a full run they are mixed in with everything else and much harder to attribute.
On HubSpot and Attio, which needs a plan upgrade on one side
The migration needs redoing from scratch
WhyThere is no partial undo. Attio documents a bulk delete as the way back.
Navigate to Companies or People, clear all filters, tick the first checkbox next to the column header, then More and Delete records. This is why the sample run exists.
On HubSpot and Attio, which needs a plan upgrade on one side
An error appears mid-migration with no obvious cause
WhyImport2 is running the migration, not Attio, so the diagnostic path leaves Attio.
Email help@import2.com with Attio support copied at support@attio.com, including the migration ID and a screenshot of the error. That is the documented route.
On HubSpot and Attio, which needs a plan upgrade on one side
Something in HubSpot changed after the migration and Attio does not know
WhyBy design. This is a one-time move with no ongoing sync in either direction.
Pick a cutover date and stop writing to HubSpot. Running both as systems of record is the failure this pair makes easy and nothing here prevents it.
On HubSpot and Attio, which needs a plan upgrade on one side