Skip to main content

​
SharePoint

Shanone’s SharePoint integration gives your agent 13 tools for finding sites, browsing document libraries, and moving files in and out of SharePoint — a focused set covering the operations agents actually need, rather than the full SharePoint admin surface.

​
Getting Started

1

Connect via OAuth

Ask your agent to do something with SharePoint (e.g. “find the Q3 budget file in our finance site”), or connect proactively from Integrations in the Shanone dashboard.
2

Authorize the Microsoft account

Approve Microsoft’s OAuth consent screen for the account that has access to the SharePoint sites you want Shanone to use.
3

Retry your request

Once connected, shanone_execute_tool calls for sharepoint_* tools will succeed.

​
Available Tools

Shanone provides 13 tools for SharePoint, organized into these categories:
sharepoint_get_file_info, sharepoint_download_file, sharepoint_upload_file, sharepoint_delete_file, sharepoint_search_files
sharepoint_list_folder, sharepoint_create_folder, sharepoint_delete_folder
sharepoint_create_sharing_link, sharepoint_list_permissions
sharepoint_list_sites, sharepoint_get_site, sharepoint_search_sites

​
Common Use Cases

Document lookup

Search across sites for a file by name or keyword and download it for review

Drop-off automation

Upload a generated report into the right site’s document library on a schedule

External sharing links

Generate a view-only sharing link for a file instead of manually setting permissions

Access audits

List permissions on a sensitive folder to check who currently has access

​
Troubleshooting

The connected account must actually be a member of the target site — SharePoint search is scoped to sites the authenticated user can see, not the whole tenant.
Check shanone_get_tool_schema for sharepoint_upload_file — very large files (typically over a few MB) often need a different upload session flow than small ones, so break large uploads into smaller files where possible.
Deleted items go to the site’s recycle bin rather than disappearing immediately; this is expected SharePoint behavior, not a tool failure.