Microsoft SharePoint
Team site document libraries.
What it does
Reads and writes SharePoint lists and libraries. Where a larger client keeps shared records, and often where the real operational data sits.
What you need
An account with Microsoft SharePoint that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Microsoft SharePoint'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 SharePoint 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 SharePoint's own security settings, which works even if you never open RAiN again.
What an agent can do with it
16 actions are available once connected. They appear in the tool list for this project only — a project that has not connected Microsoft SharePoint is never offered them.
| Action | What it does |
|---|---|
sharepoint_create_list_item_by_id |
Create SharePoint List Item by GUID |
sharepoint_get_site_root |
Get SharePoint Root Site |
sharepoint_get_site_page_content |
Get SharePoint Site Page Content |
sharepoint_get_site_by_hostname |
Get SharePoint Site by Hostname |
sharepoint_get_site_by_id |
Get SharePoint Site by ID |
sharepoint_get_site_drive_item_by_path |
Get Site Drive Item by Path |
sharepoint_list_sites |
List SharePoint Sites |
sharepoint_list_site_drives |
List Site Drives |
sharepoint_list_subfolders_in_folder |
List Subfolders in Folder |
sharepoint_search_files |
Search Files Across All Sites |
sharepoint_update_file_item |
Update File Item Metadata |
sharepoint_update_list |
Update SharePoint List |
sharepoint_update_list_item |
Update SharePoint List Item |
sharepoint_update_site |
Update SharePoint Site |
| … | and 2 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 facilities team keeps a maintenance log as a SharePoint list. An agent adds each new fault report and escalates anything still open after 48 hours.
When it goes wrong
Permissions bite here more than anywhere. The connected account only sees what that person sees. Connect an account with access to the site you mean.
See also
- Integrations & Connected Accounts — who holds the authorisation
- Action steps — running one action exactly as written
- Sequences — how steps fit together

