Inbox & chat
An AI agent for your Outlook mailbox.
Connect Outlook and an OpenHelm agent can triage, draft and follow up from your Microsoft 365 mailbox on a recurring schedule. Every run is logged, results are checked by a separate evaluator, and drafts wait for your approval unless you raise the autonomy level.
What agents do with Outlook. Recurring jobs, checked every run.
Daily mailbox triage
Each morning, sort new mail into folders by intent, flag anything urgent, and email you a two-minute summary of what actually needs a human.
Draft replies for routine mail
Prepare replies to recurring request types, such as scheduling, documents and status queries, and leave them in Drafts for one-click review.
Awaiting-reply chaser
Keep a list of threads you are waiting on and send measured follow-ups on a working-day cadence until they resolve.
Attachment filing and extraction
Pull key fields from attachments such as invoices or purchase orders into a data table, so nothing lives only in a buried email.
Connect Outlook. A few minutes, once.
Connect Outlook
Add Outlook 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": "Outlook" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.Questions
Does this work with shared or delegated mailboxes?
The agent operates on the mailbox the connection is authorised for. If your Microsoft 365 permissions include a shared mailbox, jobs can be scoped to it; otherwise each mailbox gets its own connection.
How does OpenHelm connect to Outlook?
Through a scoped OAuth grant: you sign in to Outlook 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 Outlook 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.
More in Inbox & chat
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.