List Folder (Next Page)

dropbox.list_folder_continue
ActionFiles & storageconnection required

Calls the Dropbox API with the connection's credentials.

Read the next page of a folder listing using the cursor the previous page returned.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Dropbox
Secret shape
the Dropbox access token
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
cursor
The cursor from the previous dropbox.list_folder or dropbox.list_folder_continue result.
stringYes———

Output

One shape.

result

FieldTypeExample
entries
The files and folders on this page, each a Dropbox metadata object.
array—
cursor
Pass this to dropbox.list_folder_continue for the next page.
string—
has_more
True when another page is waiting behind the cursor.
boolean—
{
  "cursor": "",
  "entries": [],
  "has_more": false
}

Notes

  • Paths are absolute and start with a slash ('/Reports/2026/q1.csv'); the account root is the empty string. A Dropbox file id ('id:…') or revision ('rev:…') may be used anywhere a path is asked for.
  • Uploads and downloads use content.dropboxapi.com and everything else uses api.dropboxapi.com; the nodes pick the right host for you.
  • The connection's access token must carry the scope the call needs — files.content.write to upload, move, delete or restore, files.content.read to download, files.metadata.read to list, search or read metadata, sharing.read to list shared links, sharing.write to create or revoke one, and account_info.read for space usage.
  • A cursor can be invalidated by Dropbox ('reset'); start again from dropbox.list_folder when that happens.

See List Folder (Next Page) run in a workflow.

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