Vibe Prospecting Plugin for OpenClaw

Run B2B prospecting, enrichment, research, and GTM data workflows directly inside the OpenClaw gateway.

Getting started · Core capabilities · Use cases and example workflows · Tool reference · vibeprospecting.ai ↗

What is Vibe Prospecting Plugin?

Vibe Prospecting Plugin is a workflow layer for Explorium's B2B data platform, packaged as a native OpenClaw plugin. It lets users search companies, discover contacts, match raw lead lists, enrich CRM records, filter audiences, research accounts, and export structured prospecting data — all from inside an OpenClaw session.

GTM teams and AI agents can run repeatable, data-intensive workflows powered by live company and contact intelligence from Explorium's network of 150M+ companies and 800M+ professionals across 50+ data sources.

The plugin ships SKILL.md and reference docs; all tool execution runs through the vpai CLI (installed via npm install -g @vibeprospecting/vpai@latest, with npx @vibeprospecting/vpai@latest as a fallback).

Getting started

Prerequisites

• OpenClaw 2026.5.26 or later — verify with openclaw --version
• Node.js 22.19.0 or later — verify with node --version

Install

From ClawHub:

openclaw plugins install clawhub:vpai-plugin
openclaw plugins enable vpai-plugin

For local development:

openclaw plugins install --link .
openclaw plugins enable vpai-plugin

Then restart the gateway — the plugin will not appear in tool lists until you do:

openclaw gateway restart

Verify it is active:

openclaw plugins list          # expect `vpai-plugin` with status `enabled`

Authenticate

Authenticate with your Vibe Prospecting account using either method.

Option A — CLI login (recommended):

npm install -g @vibeprospecting/vpai@latest
vpai login
# Open the printed URL, approve in your browser, then poll until sign-in completes:
vpai login --poll

If global install is blocked (sandbox, permissions), use npx @vibeprospecting/vpai@latest in place of vpai.

Credentials are stored at ~/.config/vpai/config.json and persist across sessions.

Protect this file. It holds a long-lived API key in plaintext. Restrict its permissions (chmod 600 ~/.config/vpai/config.json), be cautious on shared/multi-user hosts and in backups, never print the key into chat, logs, or version control, and rotate it (logout then re-login) if it may have been exposed. See Security, authentication, and data handling.

Option B — VP_API_KEY env var:

export VP_API_KEY=your-key-here

Restart the gateway after authenticating. To switch accounts or sign out, run vpai logout.

Run your first workflow

Start a new OpenClaw session and ask:

Find 50 B2B SaaS companies in the US with 200 to 1,000 employees. For each company, find the VP of Marketing or Head of Growth and return name, title, company, LinkedIn URL, email if available, and company domain.

Expected output

Core capabilities

Use cases and example workflows

Vibe Prospecting is designed for multi-step workflows — the kind you would otherwise build in Clay or n8n — but running natively inside OpenClaw. Each section below describes a use case and includes a ready-to-use prompt.

Working with personal data. Several of these workflows match, enrich, and export personal and professional contact data (names, emails, phones, LinkedIn URLs). Only upload, process, or export contact lists you are authorized to handle, and follow the data handling guidance below.

1 — Build a targeted prospect list

Define ICP filters, discover matching companies, find relevant contacts, enrich records, and export structured lists ready for outreach or CRM import.

For: GTM engineers, SDR leaders, growth operators  |  Output: CSV of qualified prospects

Find 500 US-based cybersecurity companies with 50 to 500 employees. For each company, find the VP Sales, Head of Partnerships, or CRO. Return company name, domain, headcount, revenue range, contact name, title, LinkedIn URL, and email if available.

2 — Enrich CRM records

Match existing leads and accounts by email, LinkedIn URL, or name and company. Fill missing fields — title, domain, phone, revenue, headcount — and prepare clean records for CRM update.

For: RevOps, SalesOps, CRM admins  |  Output: Clean CSV ready for CRM import

Take this CSV of Salesforce leads. Match each person by email, LinkedIn URL, or name and company. Add current title, company domain, LinkedIn URL, work email, phone if available, headcount, revenue, and industry. Export a clean CSV for CRM update.

3 — Find work emails from LinkedIn URLs

Match LinkedIn profile URLs to professional records and return verified work contact details.

For: SDRs, sales engineers, growth teams  |  Output: Work email, title, company, domain, confidence

For each LinkedIn URL in this CSV, match the person to a professional profile and return work email, current company, title, company domain, and confidence level.

4 — Build an ABM account list

Build targeted account lists, filter by company attributes, and find two to three decision-makers per account by role and seniority.

For: Demand gen, field marketing, enterprise sales  |  Output: Account list with 2–3 contacts per account

Find 300 fintech companies in North America with 100 to 2,000 employees. Filter for companies likely to have sales or marketing operations teams. Find 2 to 3 senior marketing or revenue leaders per account.

5 — Score inbound leads

Enrich form submissions, identify the company, evaluate ICP fit against firmographic and technographic criteria, and rank or route leads based on match score.

For: Marketing ops, demand gen, SDR teams  |  Output: Lead list with ICP fit score for routing

Enrich these inbound leads, identify their companies, add headcount, revenue range, and industry, and score each lead from 1 to 5 based on ICP fit for a mid-market B2B SaaS sales motion.

6 — Clean and enrich a CSV

Normalize company names, deduplicate contacts, match each row to a real profile, enrich missing fields, and export a clean standardized output.

For: RevOps, data teams, GTM engineers  |  Output: Standardized, enriched CSV

Normalize company names, deduplicate contacts, match each row to a person or company profile, enrich missing fields, and export a standardized CSV.

7 — Research account pain points

Look up company signals and summarize likely business or technical pain points per account for outbound messaging.

For: AEs, SDRs, ABM teams  |  Output: Account research table with outreach angles

For these 100 target accounts, summarize likely business or technical pain points relevant to data infrastructure, GTM operations, or sales productivity. Include company name, domain, pain point summary, and suggested outreach angle.

8 — Run a multi-step GTM workflow

Chain company discovery, signal-based filtering, content enrichment, and contact discovery into a single workflow — the kind of pipeline you would normally build in Clay or n8n, running natively inside OpenClaw.

For: GTM engineers, growth teams, sales leaders  |  Output: Signal-filtered companies with qualified growth contacts

/vibe_prospecting

Find 500 B2B SaaS companies in the US with 200 to 1,000 employees. Fetch companies and filter down so that 500 companies remain after applying the event filter. Enrich each company with LinkedIn posts and keep only companies that have the keyword "event" in one of their posts. For the remaining companies, find the head of growth or a similar senior growth/marketing leader. Return the results as a CSV with these columns: name, title, company, linkedin_url, professional_email, company_domain

Output examples

Prospect output

{
  "company_name": "Example Bank",
  "company_domain": "examplebank.com",
  "industry": "Commercial Banking",
  "headcount": "1,001-5,000",
  "revenue_range": "$100M-$500M",
  "contact_name": "Jane Smith",
  "title": "VP Marketing",
  "linkedin_url": "https://www.linkedin.com/in/example",
  "email": "jane.smith@examplebank.com",
  "confidence": "high"
}

CRM enrichment output

{
  "input_email": "sam@example.com",
  "matched_person_id": "person_123",
  "current_title": "Director of Revenue Operations",
  "current_company": "ExampleCo",
  "company_domain": "exampleco.com",
  "linkedin_url": "https://www.linkedin.com/in/example",
  "work_email": "sam@exampleco.com",
  "phone": "+1-555-000-0000",
  "match_confidence": "medium"
}

Company enrichment output

{
  "company_name": "ExampleCo",
  "domain": "exampleco.com",
  "industry": "B2B SaaS",
  "headcount": "201-500",
  "revenue_range": "$10M-$50M",
  "hq_country": "United States",
  "hq_city": "Austin",
  "tech_stack": ["HubSpot", "Gong", "Outreach"],
  "linkedin_url": "https://www.linkedin.com/company/exampleco"
}

Tool reference

Workflow rules and tool mechanics are in skills/vibe-prospecting/SKILL.md; per-tool parameters come from each tool's live input schema (vpai <tool> --all-parameters).

Security, authentication, and data handling

Protecting credentials

• Authentication is handled through your Vibe Prospecting account via the vpai CLI (~/.config/vpai/config.json) or the VP_API_KEY env var. No credentials are baked into the plugin bundle.
• Treat ~/.config/vpai/config.json as a secret: it stores a long-lived API key in plaintext and persists across sessions. Restrict its permissions (chmod 600 ~/.config/vpai/config.json), and be aware that it can be exposed through shared/multi-user hosts, backups, or endpoint compromise.
• Do not include raw API keys or credentials in prompts, command output, shell history, logs, exported files, or version control.
• Rotate the key if it may have been exposed: run npx @vibeprospecting/vpai@latest logout, then re-authenticate.

Handling personal data

• Prospecting, matching, and enrichment return personal and professional contact data (names, work emails, phone numbers, LinkedIn URLs, job history). CSV/JSON exports make this data easy to copy and redistribute, so handle it responsibly.
• Only process and export contact data you are authorized to handle, and ensure you have a lawful basis (e.g. consent or legitimate interest) for the intended use.
• Apply data minimization — request only the fields and volume you actually need — and define a retention plan so contact data is not kept longer than necessary.
• Be mindful of cross-border data transfer and applicable privacy regulations (e.g. GDPR, CCPA) when processing third-party personal data.
• All data queries are routed through Explorium's API infrastructure. Data is subject to Explorium's data terms and your account permissions.
• For enterprise data, compliance, handling, and DPA questions, contact Explorium.

Troubleshooting

See docs/install-openclaw.md for the full troubleshooting table.

Learn more

Vibe Prospecting Plugin is built and maintained by Explorium. It connects OpenClaw to Explorium's B2B data platform for GTM teams, AI agents, and revenue operations workflows.