delete-no-email-contacts
정보
이 스킬은 이메일 주소가 없는 HubSpot 연락처를 자동으로 식별하고 삭제하여 과금 대상 연락처 수를 줄이고 CRM 위생을 유지합니다. 완전 자동화를 위해 HubSpot의 검색 및 일괄 아카이브 API를 사용합니다. 개발자는 의사소통이 불가능한 연락처가 누적될 때 정기적인 데이터베이스 정리를 위해 이를 구현해야 합니다.
빠른 설치
Claude Code
추천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/delete-no-email-contactsClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Delete Contacts With No Email Address
Purpose
Contacts without an email address serve no functional purpose in a HubSpot Marketing Hub instance. They cannot receive marketing emails, sales sequences, or transactional messages. They inflate the billed contact count. This skill identifies and deletes them via the API.
Prerequisites
- A HubSpot private app access token with
crm.objects.contacts.readandcrm.objects.contacts.writescopes - Python 3.10+ with
uvfor package management - A
.envfile containingHUBSPOT_ACCESS_TOKEN
Execution Pattern
This skill follows a 4-stage execution pattern: Plan -> Before State -> Execute -> After State.
Stage 1: Plan
Before writing any code, confirm these items with the user:
- Root cause: Ask whether any integrations (CRM sync, form tool, import process) are intentionally creating contacts without email. If so, fix the inflow first.
- Threshold: The default safety abort threshold is 500 contacts. If the user expects more, adjust the threshold in the execute script.
- Recovery window: Confirm the user understands that deleted contacts are recoverable for 90 days via HubSpot Settings > Data Management > Deleted Objects.
Stage 2: Before State
Run a count query to establish the baseline. Save results for comparison.
"""
Before State: Count contacts with no email address.
"""
import os
import json
import requests
from dotenv import load_dotenv
load_dotenv()
TOKEN = os.environ["HUBSPOT_ACCESS_TOKEN"]
BASE = "https://api.hubapi.com"
headers = {
"Authorization": f"Bearer {TOKEN}",
"Content-Type": "application/json",
}
search_payload = {
"filterGroups": [
{
"filters": [
{
"propertyName": "email",
"operator": "NOT_HAS_PROPERTY",
}
]
}
],
"properties": ["firstname", "lastname", "createdate", "hs_object_id"],
"limit": 1, # Only need the total count
}
url = f"{BASE}/crm/v3/objects/contacts/search"
response = requests.post(url, headers=headers, json=search_payload)
response.raise_for_status()
data = response.json()
total = data.get("total", 0)
print(f"BEFORE STATE: {total} contacts exist with no email address.")
if total > 0 and data.get("results"):
sample = data["results"][0]
props = sample.get("properties", {})
print(f" Sample: ID {sample['id']}, "
f"{props.get('firstname', '(empty)')} {props.get('lastname', '(empty)')}, "
f"created {props.get('createdate', '(unknown)')}")
Expected output: A count of contacts with no email and a sample record for sanity checking.
Present findings to the user before proceeding. Ask for explicit confirmation to continue.
Stage 3: Execute
Collect all contact IDs via paginated search, export a CSV audit trail, then batch-delete.
"""
Execute: Delete all contacts with no email address.
Steps:
1. Paginated search to collect all contact IDs
2. Export CSV audit log before deletion
3. Batch archive in groups of 100
"""
import os
import csv
import time
import requests
from dotenv import load_dotenv
load_dotenv()
TOKEN = os.environ["HUBSPOT_ACCESS_TOKEN"]
BASE = "https://api.hubapi.com"
headers = {
"Authorization": f"Bearer {TOKEN}",
"Content-Type": "application/json",
}
# --- Step 1: Collect all contact IDs ---
all_contacts = []
after = None
search_payload = {
"filterGroups": [
{
"filters": [
{
"propertyName": "email",
"operator": "NOT_HAS_PROPERTY",
}
]
}
],
"properties": ["firstname", "lastname", "createdate", "hs_object_id"],
"limit": 100,
}
while True:
payload = search_payload.copy()
if after:
payload["after"] = after
resp = requests.post(
f"{BASE}/crm/v3/objects/contacts/search",
headers=headers, json=payload,
)
resp.raise_for_status()
data = resp.json()
for contact in data.get("results", []):
props = contact.get("properties", {})
all_contacts.append({
"id": contact["id"],
"firstname": props.get("firstname", ""),
"lastname": props.get("lastname", ""),
"createdate": props.get("createdate", ""),
})
paging = data.get("paging", {})
after = paging.get("next", {}).get("after")
if not after:
break
time.sleep(0.2) # Rate limiting
print(f"Total contacts to delete: {len(all_contacts)}")
# --- Step 2: SAFETY CHECK ---
ABORT_THRESHOLD = 500
if len(all_contacts) > ABORT_THRESHOLD:
print(f"SAFETY ABORT: Found {len(all_contacts)} contacts, "
f"exceeds threshold of {ABORT_THRESHOLD}.")
print("Review the data and adjust the threshold if this is expected.")
exit(1)
# --- Step 3: Export CSV audit trail ---
os.makedirs("data/audit-logs", exist_ok=True)
csv_path = "data/audit-logs/deleted-no-email-contacts.csv"
with open(csv_path, "w", newline="") as f:
writer = csv.DictWriter(f, fieldnames=["id", "firstname", "lastname", "createdate"])
writer.writeheader()
writer.writerows(all_contacts)
print(f"Audit log saved: {csv_path} ({len(all_contacts)} records)")
# --- Step 4: Batch delete ---
all_ids = [c["id"] for c in all_contacts]
BATCH_SIZE = 100
deleted_count = 0
failed_ids = []
for i in range(0, len(all_ids), BATCH_SIZE):
batch = all_ids[i : i + BATCH_SIZE]
delete_payload = {"inputs": [{"id": cid} for cid in batch]}
resp = requests.post(
f"{BASE}/crm/v3/objects/contacts/batch/archive",
headers=headers, json=delete_payload,
)
if resp.status_code == 204:
deleted_count += len(batch)
print(f" Batch {i // BATCH_SIZE + 1}: deleted {len(batch)} contacts")
else:
failed_ids.extend(batch)
print(f" Batch FAILED: {resp.status_code} — {resp.text[:200]}")
time.sleep(0.5) # Rate limiting between batches
print(f"\nDeleted: {deleted_count}, Failed: {len(failed_ids)}")
Key API details:
POST /crm/v3/objects/contacts/searchwithNOT_HAS_PROPERTYfilter onemail- Paginate with
aftercursor, 100 results per page POST /crm/v3/objects/contacts/batch/archiveaccepts up to 100 IDs per call- Successful archive returns HTTP 204 (no content)
Stage 4: After State
Re-run the before-state query to confirm zero contacts remain.
"""
After State: Verify no contacts with missing email remain.
"""
# (Same search payload as Before State)
response = requests.post(url, headers=headers, json=search_payload)
response.raise_for_status()
total = response.json().get("total", 0)
if total == 0:
print("SUCCESS: 0 contacts with no email remain.")
else:
print(f"WARNING: {total} contacts with no email still exist.")
print("New contacts may have been created since deletion. Investigate.")
Present results to the user. If new contacts appeared, investigate the source (form submissions, integrations, imports).
Safety Mechanisms
| Mechanism | Detail |
|---|---|
| Abort threshold | Hard-coded at 500 contacts by default. If the search returns more, the script exits without deleting anything. Adjust only with explicit user confirmation. |
| CSV audit trail | Every contact ID, name, and create date is exported to CSV before any deletion occurs. |
| Confirmation prompt | Always present the Before State count to the user and wait for explicit confirmation before running Execute. |
| 90-day recovery | Deleted contacts can be restored via HubSpot Settings > Data Management > Deleted Objects for 90 days. |
| Archived contacts audit | After deletion, you can retrieve deleted contacts via the standard contacts endpoint with archived=true parameter to verify what was removed. |
Technical Gotchas
-
NOT_HAS_PROPERTYvsEQ "": UseNOT_HAS_PROPERTYoperator, notEQwith an empty string. HubSpot treats "property not set" differently from "property set to empty string." -
Search API pagination limit: The HubSpot CRM Search API has a hard cap of 10,000 results per query. For this use case (typically a few hundred contacts), this is not an issue. If you encounter it, use segmented queries (e.g., filter by create date ranges).
-
Rate limiting: The search API allows ~4 requests/second for a private app. The batch archive API is more restrictive. Use
time.sleep(0.5)between batch archive calls. -
Batch archive returns 204: A successful batch archive returns HTTP 204 with an empty body, not 200. Check for
status_code == 204. -
Contacts may reappear: If an integration or form is creating contacts without email, new ones will appear after deletion. Always investigate the root cause.
Package Setup
uv init hubspot-cleanup
cd hubspot-cleanup
uv add requests python-dotenv
Create a .env file:
HUBSPOT_ACCESS_TOKEN=pat-na1-xxxxxxxx
GitHub 저장소
연관 스킬
railway-docs
문서이 스킬은 Railway의 기능, 작동 방식 또는 특정 문서 URL에 대한 질문에 답하기 위해 최신 Railway 문서를 가져옵니다. 개발자들이 Railway의 공식 소스로부터 정확하고 최신 정보를 직접 받을 수 있도록 보장합니다. 사용자가 Railway의 작동 방식을 묻거나 Railway 문서를 참조할 때 사용하세요.
n8n-code-python
문서이 Claude Skill은 n8n의 Code 노드에서 Python 코드를 작성할 때 전문적인 지침을 제공하며, 특히 Python 표준 라이브러리 사용과 n8n의 특수 구문인 `_input`, `_json`, `_node` 작업에 중점을 둡니다. 이는 개발자가 n8n 내에서 Python의 제한 사항을 이해하도록 돕고, 대부분의 워크플로에는 JavaScript 사용을 권장하면서도 특정 데이터 변환 요구사항에 대한 Python 솔루션을 제안합니다.
archon
문서Archon 스킬은 REST API를 통해 RAG 기반 시맨틱 검색과 프로젝트 관리를 제공합니다. 이 스킬을 사용하여 문서 검색, 계층적 프로젝트/태스크 관리, 문서 업로드 기능을 갖춘 지식 검색을 수행할 수 있습니다. 외부 문서를 검색할 때는 다른 소스를 사용하기 전에 항상 Archon을 최우선으로 활용하세요.
n8n-code-javascript
문서이 Claude Skill은 n8n의 Code 노드에서 JavaScript 코드 작성에 대한 전문적인 지침을 제공합니다. `$input`/`$json` 변수, HTTP 헬퍼, DateTime 처리와 같은 필수적인 n8n 특정 구문을 다루며 일반적인 오류를 해결합니다. Code 노드에서 사용자 정의 JavaScript 처리가 필요한 n8n 워크플로우를 개발할 때 활용하세요.
