| name | sales-phantombuster |
| description | PhantomBuster (phantombuster.com) platform help — code-free web/LinkedIn automation + scraping + lead-gen: 'Phantoms' (LinkedIn search export, scrapers, auto-connect, email finder), Flows that chain them, AI Agents + a cloud LinkedIn Leads database. Developer surface: a REST API (base phantombuster.com/api/v2, X-Phantombuster-Key-1 header) to launch agents (POST /agent/{id}/launch → container id) and fetch run results (/containers/fetch-result-object), plus the Leads storage and per-agent webhooks (secret param, 11s timeout) on run completion. Billed by execution time + slots; API on all paid plans. Use when launching a Phantom or fetching its scraped output via the API, wiring a run-finished webhook, handling the async agent→container model, managing slots/execution-time, or LinkedIn cookie/safety issues. Do NOT use for prospect-list / lead-sourcing strategy across tools (use /sales-prospect-list), enrichment strategy across vendors (use /sales-enrich), or outbound cadence strategy (use /sales-cadence). |
| argument-hint | [describe what you need help with in PhantomBuster] |
| license | MIT |
| version | 1.0.1 |
| tags | ["sales","prospecting","automation","platform"] |
| github | https://github.com/phantombuster |
PhantomBuster Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Launch a Phantom via the API and fetch its scraped output (agent → container → result)
- B) Get notified when a run finishes (per-agent webhook)
- C) Pick/configure a Phantom (LinkedIn search export, profile scraper, auto-connect, email finder)
- D) Chain Phantoms into a Flow/Workflow, or add an AI Agent step
- E) Manage slots + execution-time limits, or the LinkedIn Leads storage
- F) Handle LinkedIn session cookies / avoid getting an account flagged
-
API or no-code? Code → REST API (X-Phantombuster-Key-1) + webhooks. No endpoint → run Phantoms in-app, or Zapier/Make/n8n.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Prospect-list / lead-sourcing strategy across tools (which scraper, ICP) | /sales-prospect-list {question} |
| Contact enrichment strategy across vendors | /sales-enrich {question} |
| Outbound sequence/cadence for the leads you scrape | /sales-cadence {question} |
| LinkedIn outreach strategy / account safety across tools | /sales-cadence {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-prospect-list build a LinkedIn ICP list safely".
Step 3 — PhantomBuster platform reference
Read references/platform-guide.md for the full reference — the Phantom/Flow/Agent model, the slots + execution-time + email-credits limits, the LinkedIn-cookie + safety model, plan tiers, and quick-start recipes (launch a Phantom; fetch results; wire a webhook).
Read references/phantombuster-api-reference.md for the integration surface — base https://phantombuster.com/api/v2, X-Phantombuster-Key-1 auth, the (, , ), (, ), and (LinkedIn Leads DB) endpoints, responses, the model, and per-agent (secret query param, 11s timeout).
