Phantombuster
Phantombuster: launch a Phantom, follow the run it queues, and read back the console output and the result object that run produced.
OCNORA ships 8 typed Phantombuster operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.phantombuster.com/api/v2 through the HTTP node with the same credential.
Before you connect Phantombuster
- Authentication
- API key
- Credential
- the API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Phantombuster
Operations, grouped by what they do to your data.
Read and search 6
Delete and cancel 1
Other operations 1
A sample Phantombuster workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Phantombuster trigger is needed.
- 2Get Agentphantombuster.get_agentRead one Phantom's record, with the URLs of its result files.
- 3Launch Agentphantombuster.launch_agentQueue one run of a Phantom and return the run's container id.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Get AgentRead one Phantom's record, with the URLs of its result files.phantombuster.get_agent
- Get Agent OutputRead the console output and progress of a Phantom's most recent run.phantombuster.get_agent_output
- Get RunRead one run by its container id to see whether it has finished.phantombuster.get_container
- Get Run ResultRead what one run produced, by its container id.phantombuster.get_container_result
- Launch AgentQueue one run of a Phantom and return the run's container id.phantombuster.launch_agent
- List AgentsList the Phantoms in the workspace, or just the ones named.phantombuster.list_agents
- List RunsList the past runs of one Phantom, newest first.phantombuster.list_containers
- Stop AgentAbort a Phantom that is currently running.phantombuster.stop_agent
Phantombuster questions
- How does OCNORA authenticate with Phantombuster?
- With a stored API key credential, shaped the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Phantombuster?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Phantombuster operation I need is not listed?
- Call https://api.phantombuster.com/api/v2 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Phantombuster?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Phantombuster calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Phantombuster workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.