Short answer: Drop the "Microsoft OneDrive → Create OneDrive 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 |
|---|---|---|---|
Parent Path parent_path | string | Required | Path to create the folder in (use 'root' for root) |
Folder Name name | string | Required | Folder Name. Example: Q1 Reports |
{"parent_path": "root","name": "e.g. Q1 Reports"}
{"id": "folder456","name": "Q1 Reports","folder": {"childCount": 0},"webUrl": "https://onedrive.live.com/..."}
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.