Inbox & chat
An AI agent for Microsoft Teams channels and chats.
Connect Microsoft Teams and an OpenHelm agent can summarise busy channels, chase actions agreed in meetings, and post scheduled updates. It runs in the background on the cadence you choose and reports back with a log of exactly what it read and wrote.
What agents do with Microsoft Teams. Recurring jobs, checked every run.
Channel and chat digest
Each morning, condense the previous day across selected teams and channels into a short brief: decisions, blockers and direct requests.
Action-item follow-through
After recurring meetings, collect the actions agreed in the channel thread, track owners in a data table, and nudge when a due date slips.
Scheduled status posts
Post a weekly project status assembled from your other connected tools, so the update writes itself before the Monday stand-up.
Escalation watch
Monitor for messages matching themes you define, such as outages or unhappy customers, and alert the right person by email within the hour.
Connect Microsoft Teams. A few minutes, once.
Connect Microsoft Teams
Add Microsoft Teams under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.
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.
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.
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.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections/links \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "provider": "<provider id>", "name": "Microsoft Teams" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.Questions
Can it post as a bot or as me?
The agent acts through the credential you connect. Most teams connect a dedicated account so posts are clearly attributable, and every message the agent sends is recorded in the run log.
How does OpenHelm connect to Microsoft Teams?
Through a scoped OAuth grant: you sign in to Microsoft Teams once via a hosted connect flow, in the OpenHelm app or via a connect link minted with POST /v1/connections/links. OpenHelm stores no passwords, the grant is limited to what your jobs need, and you can revoke it at any time.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Microsoft Teams data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.