Microsoft OneDrive
Secure business file storage access.
What it does
Files and folders in OneDrive. The Microsoft filing cabinet, same job as Drive.
What you need
An account with Microsoft OneDrive that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Microsoft OneDrive's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.
Connecting it
Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.
- Open the project and stay on the Visual Editor tab.
- Open the Tools & Integrations rail on the right.
- Find Microsoft OneDrive and press Connect.
- Authorise in the window that opens, then come back. The rail will show it as connected.
The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.
To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Microsoft OneDrive's own security settings, which works even if you never open RAiN again.
What an agent can do with it
54 actions are available once connected, 8 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Microsoft OneDrive is never offered them.
| Action | What it does |
|---|---|
onedrive_checkin_item |
Check In Drive Item |
onedrive_checkout_item |
Checkout Drive Item |
onedrive_copy_item |
Copy Item |
onedrive_create_item_permission |
Create Drive Item Permission |
onedrive_create_sharepoint_list_item |
Create SharePoint List Item |
onedrive_create_link |
Create Sharing Link |
onedrive_unfollow_item |
Delete Drive Following ⚠️ deletes things |
onedrive_delete_item_permission |
Delete Drive Item Permission ⚠️ deletes things |
onedrive_delete_item |
Delete Item ⚠️ deletes things |
onedrive_delete_sharepoint_item_permission |
Delete SharePoint Item Permission ⚠️ deletes things |
onedrive_delete_share_permission |
Delete Shares Permission ⚠️ deletes things |
onedrive_discard_checkout |
Discard Checkout ⚠️ deletes things |
onedrive_get_drive |
Get Drive |
onedrive_get_root |
Get Drive Root Folder |
| … | and 40 more, all listed in the rail |
Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.
A worked example
A recruiter's agent files each CV received by email into a folder per role, named by candidate and date.
When it goes wrong
Paths are case sensitive and unforgiving. Use the folder id from a list action rather than typing a path.
See also
- Integrations & Connected Accounts — who holds the authorisation
- Action steps — running one action exactly as written
- Sequences — how steps fit together

