Short answer: Drop the "Microsoft OneDrive → Create OneDrive Sharing Link" 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 |
|---|---|---|---|
Item ID itemId | string | Required | Item ID |
Link Type type | options | Required | Link Type. Options: View only, Edit, Embed |
Scope scope | options | Optional | Scope. Options: Anyone with the link, Organization only |
{"itemId": "{{trigger.itemId}}","type": "{{trigger.type}}","scope": "{{trigger.scope}}"}
{"id": "link-123","link": {"type": "view","webUrl": "https://1drv.ms/..."},"roles": ["read"]}
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.