Phantombuster is a cloud-based automation and data extraction platform. It's used by marketers, sales teams, and growth hackers to automate tasks like lead generation, social media scraping, and data enrichment.
Official docs: https://phantombuster.com/help
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Phantombuster. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete .
```bash
membrane search phantombuster --elementType=connector --json
```
Take the connector ID from output.items[0].element?.id, then:
```bash
membrane connect --connectorId=CONNECTOR_ID --json
```
The user completes authentication in the browser. The output contains the new connection id.
When you are not sure if connection already exists:
```bash
membrane connection list --json
```
If a Phantombuster connection exists, note its connectionId
When you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| --- | --- | --- |
| Create or Update Script | create-update-script | Update an existing script or create a new one if it does not exist. |
| Launch Agent | launch-agent | Add an agent to the launch queue to run it. |
| Get Agent Output | get-agent-output | Get data from an agent including console output, status, progress and messages. |
| Get Script | get-script | Get a script record by its name, including metadata and optionally the script contents. |
| List Agent Containers | list-agent-containers | Get a list of ended containers (execution instances) for an agent, ordered by date. |
| Get Agent | get-agent | Get an agent record by ID, optionally including the associated script. |
| Abort Agent | abort-agent | Abort all running instances of an agent. |
| Get User | get-user | Get information about your Phantombuster account and your agents, including time left, emails left, captchas left, st... |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Phantombuster API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
| ------ | ------------- |
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.共 2 个版本