List Folder Children

onedrive.list_children
ActionFiles & storageconnection required

Calls the OneDrive API with the connection's credentials.

List the files and folders directly inside a folder, following Graph paging up to max_results. With no item_id and no item_path, the drive root is listed.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
OneDrive
Secret shape
{"client_id": "…", "client_secret": "…", "refresh_token": "…"} with the Files.ReadWrite delegated scope
Config it needs
tenant, drive_id
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
drive_id
The drive to act on. Leave blank for the connected user's own OneDrive (/me/drive). A SharePoint document library's drive id also works here.
stringNo———
item_id
The driveItem id, addressing it as /drives/{drive-id}/items/{item-id}. Takes precedence over item_path when both are set.
stringNo———
item_path
The item's path inside the drive, e.g. 'Reports/Q3.xlsx', addressing it as /drives/{drive-id}/root:/Reports/Q3.xlsx. Used when item_id is blank.
stringNo———
max_results
How many children to return at most; Graph pages are followed until this many.
numberNo501–1000—

Example configuration

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

{
  "max_results": 50
}

Output

One shape.

result

FieldTypeExample
items
The driveItems returned.
array—
count
How many items were returned.
number—
{
  "count": 0,
  "items": []
}

See List Folder Children run in a workflow.

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