Get Agent Output
phantombuster.get_agent_output
ActionBusiness appsconnection required
Calls the Phantombuster API with the connection's credentials.
Read the console output and progress of a Phantom's most recent run.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Phantombuster
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- org_id, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
agent_id The Phantom's numeric id, which its URL in the Phantombuster dashboard ends with. | string | Yes | — | — | 1234567890123456 |
from_output_pos Start from this position in the output instead of the beginning, so a polling loop only receives what is new. | number | No | — | ≥ 0 | — |
prev_container_id The run a previous poll was reading, so the output continues from the run after it. | string | No | — | — | 9876543210987654 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"agent_id": "1234567890123456",
"prev_container_id": "9876543210987654"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
agent_id The Phantom whose output was read. | string | — |
output Phantombuster's output response for the most recent run, passed through unchanged. | object | — |
{
"agent_id": "",
"output": {}
}Notes
- This reads the MOST RECENT run of the Phantom, which is not necessarily the one a Launch Agent step queued if the Phantom also runs on its own schedule.
- A run queued by Launch Agent may not have finished yet; a run still in progress answers with what it has so far rather than failing.
- The org this acts for comes from the connection's optional org_id, sent as the X-Phantombuster-Org header; leave it unset when the key already names one org.
Related Phantombuster nodes
See Get Agent Output run in a workflow.
In a technical demo we add the Phantombuster connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.