PhantomBuster Automation
Automate lead generation, web scraping, and social media data extraction workflows through PhantomBuster's cloud platform via Composio
What this skill does
# PhantomBuster Automation Automate cloud-based data extraction and lead generation -- manage agents and scripts, monitor organization resources and usage, track container execution, and solve captcha challenges -- all orchestrated through the Composio MCP integration. **Toolkit docs:** [composio.dev/toolkits/phantombuster](https://composio.dev/toolkits/phantombuster) --- ## Setup 1. Connect your PhantomBuster account through the Composio MCP server at `https://rube.app/mcp` 2. The agent will prompt you with an authentication link if no active connection exists 3. Once connected, all `PHANTOMBUSTER_*` tools become available for execution --- ## Core Workflows ### 1. List All Agents Fetch every agent associated with your account or organization to inventory automation workflows. **Tool:** `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` ``` No parameters required -- returns all agents with IDs and metadata. Authenticate your API key first. ``` Use agent IDs from this response when fetching containers or monitoring specific automations. --- ### 2. List All Scripts Retrieve all scripts available under your account (without code bodies) for script management. **Tool:** `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL` ``` No parameters required -- returns script metadata without source code. ``` --- ### 3. Monitor Organization Resources & Quotas Check your organization's current resource usage and quota limits to plan automation capacity. **Tool:** `PHANTOMBUSTER_GET_ORGS_FETCH_RESOURCES` ``` No parameters required -- returns resource allocation and current usage metrics. ``` --- ### 4. Retrieve Agent Containers Fetch all execution containers for a specific agent to monitor run history and status. **Tool:** `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL` | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `agentId` | string | Yes | Agent ID from `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` | --- ### 5. Export Agent Usage Report Download a CSV report of all agents' run statistics for your organization. **Tool:** `PHANTOMBUSTER_GET_ORGS_EXPORT_AGENT_USAGE` ``` Returns a downloadable CSV with comprehensive agent execution statistics. ``` --- ### 6. Solve hCaptcha Challenges Obtain a valid hCaptcha token for automated form submissions or scraping flows that require captcha solving. **Tool:** `PHANTOMBUSTER_POST_HCAPTCHA` | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `siteKey` | string | Yes | Public site key of the hCaptcha widget | | `pageUrl` | string | Yes | Full URL of the page with the captcha | | `proxy` | string | No | Proxy URL (e.g., `http://user:pass@host:port`) | | `userAgent` | string | No | Custom User-Agent string to simulate | --- ## Known Pitfalls | Pitfall | Details | |---------|---------| | **Agent ID required for containers** | `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL` requires a valid `agentId` -- always resolve it first via `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` | | **API key authentication** | All PhantomBuster tools require a valid API key connection -- verify authentication before calling any tools | | **Script bodies not included** | `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL` returns metadata only, not source code | | **Organization scope** | Resource and usage tools operate at the organization level tied to your API key -- ensure the correct org is targeted | | **Branch operations** | `PHANTOMBUSTER_GET_BRANCHES_FETCH_ALL` and `PHANTOMBUSTER_GET_BRANCHES_DIFF` are for advanced script versioning -- use them to assess staging vs. release changes before deployment | --- ## Quick Reference | Tool Slug | Purpose | |-----------|---------| | `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` | List all agents in your account | | `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL` | List all scripts (metadata only) | | `PHANTOMBUSTER_GET_ORGS_FETCH_RESOURCES` | Check organization resource usage and quotas | | `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL` | Get all containers for a specific agent | | `PHANTOMBUSTER_GET_ORGS_EXPORT_AGENT_USAGE` | Export agent usage as CSV | | `PHANTOMBUSTER_POST_HCAPTCHA` | Solve hCaptcha challenges for automation | | `PHANTOMBUSTER_GET_ORGS_FETCH` | Fetch organization details | | `PHANTOMBUSTER_GET_ORGS_FETCH_AGENT_GROUPS` | Get agent groups and ordering | | `PHANTOMBUSTER_GET_BRANCHES_FETCH_ALL` | List all script branches | | `PHANTOMBUSTER_GET_BRANCHES_DIFF` | Compare staging vs. release branches | --- *Powered by [Composio](https://composio.dev)*
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.