List Runs

phantombuster.list_containers
ActionBusiness appsconnection required

Calls the Phantombuster API with the connection's credentials.

List the past runs of one Phantom, newest first.

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

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

FieldTypeRequiredDefaultConstraintsExample
agent_id
The Phantom's numeric id, which its URL in the Phantombuster dashboard ends with.
stringYes——1234567890123456
limit
How many runs to return.
numberNo—≥ 1—
mode
Which runs to include: all of them, or only the ones that have finished.
stringNo—one of "all", "finalized"—
with_runtime_events
Also return each run's runtime events.
booleanNofalse——

Example configuration

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

{
  "agent_id": "1234567890123456",
  "with_runtime_events": false
}

Output

One shape.

result

FieldTypeExample
agent_id
The Phantom whose runs were listed.
string—
containers
The runs, as Phantombuster returned them.
array—
count
How many runs came back.
number—
{
  "agent_id": "",
  "containers": [],
  "count": 0
}

Notes

  • 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 List Runs 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.