Copy OneDrive File: Microsoft OneDrive action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Source Item ID itemId	string	Required	Source Item ID
New Name name	string	Optional	Leave empty to keep original name
Destination Folder ID parentId	string	Required	ID of the destination folder

Sample request

{
  "itemId": "{{trigger.itemId}}",
  "name": "Copy of report.pdf",
  "parentId": "{{trigger.parentId}}"
}

Returns

{
  "id": "item_mic_456",
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Copy OneDrive File.

What does the Copy OneDrive File action do in Microsoft OneDrive?

Copies a file to a different folder, optionally renaming. For "template-based document creation" — copy the template Doc/Excel/PPT to a new location with workflow-supplied name.

What inputs does Copy OneDrive File require?

Required: Source Item ID, Destination Folder ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Microsoft OneDrive returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Copy OneDrive File support batch operations?

Yes. Run Copy OneDrive File inside a Loop node to process arrays. Tiny Command handles Microsoft OneDrive's rate limits automatically so you don't have to throttle manually.

More actions