B2B Database Scraper

What it does

Calls a prospecting database API directly (large-scale B2B contacts, local businesses, and podcast/YouTube creators) to build deduplicated audience lists, using native exclusion when available and client-side deduplication when it isn't.

When to use it

• When you need a large, precisely segmented B2B prospect list.
• When you're looking for content creators or local businesses for an outreach campaign.
• When you want to avoid duplicates against lists you've already worked.

Steps

1. Define the database type (large B2B, local businesses, creators) and filters.
2. The assistant calls the API with those criteria.
3. It applies native exclusion against prior lists when the database supports it.
4. If no native exclusion exists, it deduplicates client-side before delivering.
5. The final list is delivered in an exportable format.
6. No message is ever sent to these contacts; that stays in your hands.

The skill

---
name: b2b-database-scraper
description: Pulls prospect lists from B2B contact databases, local businesses, and content creators via API with native deduplication.
---

# B2B Database Scraper

## 1. What it does

- Calls a prospecting database API directly (large-scale B2B contacts, local businesses, and podcast/YouTube creators) to build deduplicated audience lists, using native exclusion when available and client-side deduplication when it isn't.

## 2. When to use it

- When you need a large, precisely segmented B2B prospect list.
- When you're looking for content creators or local businesses for an outreach campaign.
- When you want to avoid duplicates against lists you've already worked.

## 3. Step by step

- Define the database type (large B2B, local businesses, creators) and filters.
- The assistant calls the API with those criteria.
- It applies native exclusion against prior lists when the database supports it.
- If no native exclusion exists, it deduplicates client-side before delivering.
- The final list is delivered in an exportable format.
- No message is ever sent to these contacts; that stays in your hands.

## 4. Safety rules

- Safety rules: everything ships as a draft first; nothing is sent, published, or paid for without your explicit approval; no data, numbers, or results are ever invented; no credentials or secrets are typed into chat.

## 5. Best practices

- Always review the full draft before approving any send, publish, or payment.
- If real information (data, numbers, results) is missing, ask for it to be flagged as pending instead of invented.
- Keep credentials and keys out of chat; set them in environment variables or your secrets manager.

## 6. GoHighLevel integration

- Where relevant, results can be saved as contacts, tags, tasks, or notes inside your GoHighLevel sub-account.
- No automation inside GHL (workflow, campaign, trigger) activates without your review first.

For Claude Code, save it as ~/.claude/skills/b2b-database-scraper/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.