Get Run Result

phantombuster.get_container_result
ActionBusiness appsconnection required

Calls the Phantombuster API with the connection's credentials.

Read what one run produced, by its container id.

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

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
container_id
The id of one run, as Launch Agent returns it in 'container_id'.
stringYes——9876543210987654

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "container_id": "9876543210987654"
}

Output

One shape.

result

FieldTypeExample
container_id
The run whose result was read.
string—
result_object
The object the Phantom set with buster.setResultObject() — the rows it collected, not its console log.
any—
found
False when the run produced no result object, which is the normal state of a run that has not finished; branch on this in a polling loop.
boolean—
{
  "container_id": "",
  "found": false,
  "result_object": null
}

Notes

  • This is the run's own result, unlike Get Agent, whose result-file URLs always point at the Phantom's latest run.
  • 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.

See Get Run Result 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.