An AI agent across your SharePoint sites.
Connect SharePoint and an OpenHelm agent can monitor document libraries, summarise new and updated files, and produce recurring digests of what changed where, useful when important documents move faster than anyone can read them.
Recurring jobs
What an OpenHelm agent can do with SharePoint.
Each of these runs as a scheduled, self-correcting job: you describe it in plain English, approve the plan once, and an independent evaluator checks every run against the goal.
Library change digest
A weekly summary of documents added or updated in selected libraries, grouped by site, with one-line summaries of each change.
Policy and contract summaries
When new versions of key documents appear, summarise what changed against the previous version and email the owners.
Document register upkeep
Maintain a data table of controlled documents with owner, review date and status, flagging anything overdue for review.
Get started
Connect SharePoint in minutes.
- 1
Connect SharePoint
Add SharePoint under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.
- 2
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
- 3
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
- 4
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
For developers
Or provision the connection over the API.
curl https://api.openhelm.ai/v1/connections/links \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "provider": "<provider id>", "name": "SharePoint" }'
# → a short-lived hosted link; open once to authorise, then
# poll GET /v1/connections until it shows as authenticated.
# Provider ids are listed in the Connections API docs.The same connections back runs started over REST. See the AI agent API and the Connections API docs.
Related ways to put agents to work with SharePoint:
Common questions about the SharePoint integration
Docs & storage
More integrations in this category.
Put an agent to work in SharePoint this week.
Connect once, describe the job, approve the plan. From then on it runs on schedule, checks its own work, and reports back with evidence.