MCP HubMCP Hub
스킬 목록으로 돌아가기

enrich-industry

TomGranot
업데이트됨 2 days ago
7 조회
33
11
33
GitHub에서 보기
기타aiautomation

정보

이 HubSpot 워크플로우 스킬은 회사 기록에서 산업 데이터를 연락처 레코드로 자동 복사하여 B2B 타겟 캠페인을 위한 산업 기반 세분화를 가능하게 합니다. 회사는 산업 데이터를 보유하지만 연락처에는 없는 일반적인 데이터 격차를 해소합니다. 이를 사용하여 이상적 고객 프로필(ICP) 분류와 리드 스코어링에 데이터를 제공하고, 일반적인 이메일 대량 발송 대신 관련성 높은 메시지를 전송하세요.

빠른 설치

Claude Code

추천
기본
npx skills add TomGranot/hubspot-admin-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/TomGranot/hubspot-admin-skills
Git 클론대체
git clone https://github.com/TomGranot/hubspot-admin-skills.git ~/.claude/skills/enrich-industry

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

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

  1. Verify the contact Industry property exists and is compatible with the company Industry property
  2. Audit how many contacts can be enriched (before state)
  3. Build a workflow that copies industry from the associated company
  4. 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.

  1. Go to Settings > Properties > Contact properties
  2. Search for "Industry"
  3. Note ALL industry-related properties on the contact object
  4. Check which property is used in existing lists, reports, and workflows
  5. 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.

  1. Go to Automation > Workflows > Create workflow
  2. Select Contact-based > Blank workflow
  3. 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:

  1. Contact industry count should jump from near-zero to tens of thousands
  2. The enrichment list (missing industry + has company association) should be near 0
  3. 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
  4. Check that the industry distribution on contacts roughly mirrors the company industry distribution
  5. 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 industry and industry_name on 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.

GitHub 저장소

TomGranot/hubspot-admin-skills
경로: skills/enrich-industry
0

연관 스킬

llamaguard

기타

LlamaGuard는 폭력 및 혐오 발언 등 6가지 안전 범주에서 LLM 입력과 출력을 조정하기 위한 Meta의 70-80억 파라미터 모델입니다. 94-95% 정확도를 제공하며 vLLM, Hugging Face 또는 Amazon SageMaker를 사용해 배포할 수 있습니다. 이 기술을 사용하여 AI 애플리케이션에 콘텐츠 필터링 및 안전 가드레일을 손쉽게 통합하세요.

스킬 보기

cost-optimization

기타

이 Claude Skill은 리소스 적정화, 태깅 전략, 지출 분석을 통해 개발자들이 클라우드 비용을 최적화할 수 있도록 지원합니다. AWS, Azure, GCP에서 클라우드 비용을 절감하고 비용 거버넌스를 구현하기 위한 프레임워크를 제공합니다. 인프라 비용을 분석하거나, 리소스를 적정화하거나, 예산 제약을 충족해야 할 때 사용하세요.

스킬 보기

quantizing-models-bitsandbytes

기타

이 스킬은 bitsandbytes를 사용하여 LLM을 8비트 또는 4비트 정밀도로 양자화하며, 최소한의 정확도 손실로 50-75%의 메모리 감소를 달성합니다. 제한된 GPU 메모리에서 더 큰 모델을 실행하거나 추론을 가속화하는 데 이상적이며, INT8, NF4, FP4와 같은 형식을 지원합니다. 이 스킬은 HuggingFace Transformers와 통합되어 QLoRA 학습 및 8비트 옵티마이저를 가능하게 합니다.

스킬 보기

dispatching-parallel-agents

기타

이 Claude Skill은 3개 이상의 독립적인 문제를 동시에 조사하고 해결하기 위해 다중 에이전트를 배치합니다. 공유 상태나 의존성 없이 해결 가능한 무관련 장애 시나리오에 맞게 설계되었습니다. 핵심 기능은 병렬 문제 해결로, 각 독립 문제 영역마다 하나의 에이전트를 할당하여 효율성을 극대화합니다.

스킬 보기