List Pushes

pushbullet.list_pushes
ActionChat & messagingconnection required

Calls the Pushbullet API with the connection's credentials.

Retrieve one page of push history, most recently changed first.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Pushbullet
Secret shape
the access token, or {"access_token": "…"}
Config it needs
device_iden
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
active
Leave on to skip pushes that have been deleted.
booleanNotrue——
modified_after
Return only pushes changed after this Unix timestamp, in seconds.
numberNo—≥ 0—
cursor
Cursor from a previous page, to fetch the next one.
stringNo———
limit
Maximum number of pushes to return in this page.
numberNo—1–500—

Example configuration

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

{
  "active": true
}

Output

One shape.

result

FieldTypeExample
pushes
The page of pushes, most recently changed first.
array—
count
How many pushes this page carried.
number—
cursor
Cursor for the next page, empty when this was the last one.
string—
{
  "count": 0,
  "cursor": "",
  "pushes": []
}

See List Pushes run in a workflow.

In a technical demo we add the Pushbullet connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.