Short answer: Drop the "Dropbox → List Folder" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Folder Path path | string | Required | Use empty string for root, or a path like /Documents |
Recursive recursive | options | Optional | Recursive. Options: No, Yes (include subfolders) |
Limit limit | string | Optional | Limit. e.g. "100" |
{"path": "e.g. /Documents","recursive": "{{trigger.recursive}}","limit": "100"}
{"entries": [{".tag": "file","name": "report.pdf","size": 1024000,"path_display": "/Documents/report.pdf","server_modified": "2025-01-15T12:00:00Z"}],"has_more": false}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.