how to fix HubSpot enrichment error custom property not found fails import
Fixes this failure in HubSpot enrichment - create or select the custom property using its exact internal name on the correct object type in HubSpot, then update the enrichment mapping to that internal name, not the display label. Prove it on one record, then rerun the full scope and reconcile the counts.
TL;DR
Fix this in HubSpot enrichment by acting on the exact message first: create or select the custom property using its exact internal name on the correct object type in HubSpot, then update the enrichment mapping to that internal name, not the display label. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.
how to fix HubSpot enrichment error custom property not found fails importUse this when
- The operation in HubSpot enrichment fails with this exact message: how to fix HubSpot enrichment error custom property not found fails import.
- The same failure repeats on retry with unchanged inputs.
- A run, import, export or alert is blocked until this item completes.
Not for this skill when
- The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
- The operation completes and you only disagree with its output. That is a quality review, not this failure.
Steps
- Reproduce the failure with the smallest scope that still shows it in HubSpot enrichment, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
- Apply the specific fix for this error: create or select the custom property using its exact internal name on the correct object type in HubSpot, then update the enrichment mapping to that internal name, not the display label. Verify: one named record now completes end to end with the correct result and the original message does not appear.
- Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
- Compare the result counts, fields or alerts against the source in HubSpot enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
- Rerun the original operation in HubSpot enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
- Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.
Why it happens
The enrichment wrote to a display label or a property on the wrong object, so HubSpot reported the property as not found.
Variant phrasings
how to fix HubSpot enrichment error custom property not found fails import
The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.
How to fix this failure in HubSpot enrichment
The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.
Troubleshooting this failure in HubSpot enrichment
The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.
Compatibility: HubSpot enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_xocL8kqYI56gabuWyWYpdQ