enrich-industry
À propos
Cette compétence de workflow HubSpot copie automatiquement les données sectorielles des fiches entreprises vers leurs contacts associés, permettant une segmentation par secteur pour des campagnes B2B ciblées. Elle comble l'écart courant où les entreprises disposent de données sectorielles mais pas les contacts. Utilisez-la pour alimenter la classification du client idéal (ICP), le scoring des leads et envoyer des messages pertinents plutôt que des campagnes d'emails génériques.
Installation rapide
Claude Code
Recommandénpx skills add TomGranot/hubspot-admin-skills -a claude-code/plugin add https://github.com/TomGranot/hubspot-admin-skillsgit clone https://github.com/TomGranot/hubspot-admin-skills.git ~/.claude/skills/enrich-industryCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Enrich Contact Industry from Associated Company
Copy industry data from company records to their associated contacts. In a typical B2B CRM, company records have industry populated at high rates (80-90%) while contact records have almost none. This workflow bridges that gap automatically.
Why This Matters
Without industry on contact records, you cannot segment email campaigns by vertical. For B2B companies targeting specific industries, this makes the difference between spray-and-pray email blasts and targeted, relevant messaging. Industry data on contacts also feeds ICP tier classification and lead scoring models.
Prerequisites
- HubSpot Marketing Hub Professional or Sales Hub Professional (for Workflows)
- Company name enrichment (enrich-company-name skill) should be completed first, as it may trigger new company associations
- Access to Settings > Properties to verify/create the contact Industry property
Plan
- Verify the contact Industry property exists and is compatible with the company Industry property
- Audit how many contacts can be enriched (before state)
- Build a workflow that copies industry from the associated company
- Verify enrichment results (after state)
Before State
Check Property Compatibility
This is the most important pre-step. Contacts may have TWO industry properties: industry and industry_name. You must verify which one HubSpot uses for lists and reports.
- Go to Settings > Properties > Contact properties
- Search for "Industry"
- Note ALL industry-related properties on the contact object
- Check which property is used in existing lists, reports, and workflows
- The target property must be compatible with the company Industry property:
- If both are dropdown select: option values must match exactly (same spelling, same case)
- If the contact property is single-line text: it will accept any value (safest option)
- If unsure, use single-line text to avoid copy failures
If no contact Industry property exists, create one:
- Object: Contact
- Group: Contact information
- Label: Industry
- Field type: Dropdown select (copy all values from the company Industry property) OR Single-line text (accepts any value)
Audit Enrichment Opportunity
import os
from hubspot import HubSpot
from dotenv import load_dotenv
load_dotenv()
api_client = HubSpot(access_token=os.getenv("HUBSPOT_API_TOKEN"))
# Count contacts missing industry
result = api_client.crm.contacts.search_api.do_search(
public_object_search_request={
"filterGroups": [{
"filters": [{
"propertyName": "industry",
"operator": "NOT_HAS_PROPERTY"
}]
}],
"limit": 0
}
)
print(f"Contacts missing industry: {result.total}")
Also create a HubSpot list to estimate enrichable contacts:
- Filter 1: Contact Industry > is unknown
- Filter 2: AND Associated company > Industry > is known
- This count tells you how many contacts will actually be enriched
Execute
Create the Enrichment Workflow
This workflow is nearly identical to the company name enrichment workflow. If you already built that one, clone it and swap the property references.
- Go to Automation > Workflows > Create workflow
- Select Contact-based > Blank workflow
- Name:
AUTO-ENRICH: Copy Industry from Company
Enrollment trigger:
- Contact property > Industry > is unknown
- AND Associated company > Industry > is known
Re-enrollment:
- Enable re-enrollment on the same criteria. This ensures contacts that later get associated with a company are also enriched.
Action: Copy property
- Copy FROM: Company > Industry
- Copy TO: Contact > Industry
Activate:
- Click Review > Turn on
- Select Yes, enroll existing contacts
Note: Unlike the company name workflow, no delay is needed here. If the contact already has an associated company with industry data (checked by the enrollment trigger), the copy can happen immediately.
After State
Wait 1-2 hours for the workflow to process, then verify.
Script approach:
result = api_client.crm.contacts.search_api.do_search(
public_object_search_request={
"filterGroups": [{
"filters": [{
"propertyName": "industry",
"operator": "NOT_HAS_PROPERTY"
}]
}],
"limit": 0
}
)
print(f"Contacts still missing industry: {result.total}")
Verification checklist:
- Contact industry count should jump from near-zero to tens of thousands
- The enrichment list (missing industry + has company association) should be near 0
- Spot-check 20+ contacts for accuracy:
- Open the contact record
- Verify the Industry field shows a value
- Click the associated company and confirm the industry matches
- Check that the industry distribution on contacts roughly mirrors the company industry distribution
- Check workflow history for failures — most common is property value mismatch (company has a value that does not match a dropdown option on the contact)
Key Technical Learnings
- Two industry properties can exist. Some HubSpot portals have both
industryandindustry_nameon contacts. Verify which one is authoritative before building the workflow. Writing to the wrong one means your lists and reports will not see the data. - Dropdown value matching is case-sensitive and exact. If the company Industry has "Healthcare" and the contact Industry dropdown has "healthcare" (lowercase), the copy will fail. Ensure values match exactly.
- Consider consolidating similar industries. Many CRMs have overlapping values like "Healthcare" and "Hospital & Health Care". For segmentation, consider creating a separate "Industry Group" property that maps similar values into broader categories. This is optional but improves list usability.
- This does not overwrite existing values. The enrollment trigger requires "Industry is unknown", so contacts that already have industry data are not affected.
- If using a text field instead of dropdown: Enrichment works, but you lose the ability to filter by exact dropdown values in lists. You can convert to a dropdown later but will need to clean up inconsistent text values first.
- Run this after company name enrichment. Company name enrichment may trigger new company associations, which increases the number of contacts eligible for industry enrichment.
- Clone the company name workflow. The structure is nearly identical. Clone it in HubSpot and swap the property references to save time.
Dépôt GitHub
Compétences associées
llamaguard
AutreLlamaGuard est le modèle de Meta, doté de 7 à 8 milliards de paramètres, conçu pour modérer les entrées et sorties des LLM selon six catégories de sécurité comme la violence et les discours haineux. Il offre une précision de 94 à 95 % et peut être déployé avec vLLM, Hugging Face ou Amazon SageMaker. Utilisez cette compétence pour intégrer facilement le filtrage de contenu et des garde-fous de sécurité dans vos applications d'IA.
cost-optimization
AutreCette compétence de Claude aide les développeurs à optimiser les coûts du cloud grâce au redimensionnement des ressources, aux stratégies d'étiquetage et à l'analyse des dépenses. Elle fournit un cadre pour réduire les dépenses cloud et mettre en œuvre une gouvernance des coûts sur AWS, Azure et GCP. Utilisez-la lorsque vous devez analyser les coûts d'infrastructure, redimensionner les ressources ou respecter des contraintes budgétaires.
quantizing-models-bitsandbytes
AutreCette compétence quantifie les LLMs en précision 8 bits ou 4 bits à l'aide de bitsandbytes, permettant une réduction de 50 à 75 % de la mémoire utilisée avec une perte de précision minime. Elle est idéale pour exécuter des modèles plus volumineux sur une mémoire GPU limitée ou pour accélérer l'inférence, prenant en charge des formats comme INT8, NF4 et FP4. La compétence s'intègre à HuggingFace Transformers et permet l'entraînement QLoRA ainsi que l'utilisation d'optimiseurs en 8 bits.
dispatching-parallel-agents
AutreCette compétence Claude déploie plusieurs agents pour enquêter et résoudre simultanément 3 problèmes indépendants ou plus. Elle est conçue pour des scénarios impliquant des défaillances non liées qui peuvent être résolues sans état partagé ni dépendances. La capacité fondamentale est la résolution de problèmes en parallèle, en assignant un agent par domaine problématique indépendant afin de maximiser l'efficacité.
