
Read your Outlook / Microsoft 365 inbox so Ruby can find replies, surface unread mail, and read messages by job.
Ask Ruby
Ruby reads from Outlook and grounds her answers in your data. Every connection starts read-only: she surfaces, summarizes, and drafts, and your team takes the action.
List mail folder messages
List messages from a folder in the connected Outlook / Microsoft 365 mailbox, with optional Microsoft Graph $filter and $orderby. Use it to check whether a homeowner or adjuster replied, surface unread mail, and answer latest/most-recent questions. For recency questions, combine a receivedDateTime window filter WITH orderby 'receivedDateTime desc' (Graph supports that combination; without the orderby, a filtered window comes back oldest-first). Listings return lean metadata (subject, sender, dates, bodyPreview); read a message in full with OUTLOOK_GET_MESSAGE. Defaults to the Inbox; use OUTLOOK_LIST_MAIL_FOLDERS to find other folder ids.
Get message
Read one full Outlook message by its Graph message id (from OUTLOOK_LIST_MAIL_FOLDER_MESSAGES): subject, sender, recipients, date, body, and attachment metadata. Use after a list when you need the actual contents.
List mail folders
List the mail folders in the connected Outlook mailbox (Inbox, Sent Items, and any custom folders) with their ids. Use to discover which folder id to pass to OUTLOOK_LIST_MAIL_FOLDER_MESSAGES.
Let Ruby send mail from this mailbox and draft replies, not just read it. Drafting is always available as the safer option.
An admin switches a connection to read-write in Settings > Integrations. From then on every write waits for a human’s approval before it leaves, by default, and every one lands in your audit log with what changed.
Send email
Send an email from the connected Outlook / Microsoft 365 mailbox. Sends IMMEDIATELY and cannot be recalled, so confirm recipient, subject, and body first.
Create draft
Create an Outlook DRAFT without sending it, so a person can review and send. Prefer this over OUTLOOK_SEND_EMAIL whenever the wording should be checked first.
Grounded answers
Ruby reads Outlook live and cites what she found, so answers reflect your actual data, not a stale export.
Reads by default
Every connection starts read-only. Ruby surfaces and drafts while your team takes the action; writes are opt-in per connection, human-approved by default, and always logged.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so Outlook data lands in the right operational context.
Connect Outlook once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in Outlook and the rest of your connected stack.
Claude
Bring the same secure Outlook connection into Claude so it can answer with your live data.
ChatGPT
Use Outlook from ChatGPT with the same per-company, permissioned access Ruby uses.
Do I need developer credentials to connect Outlook?
No. Outlook connects with a single click, Ruby handles the OAuth handshake and token refresh for you.
Can Ruby change anything in Outlook?
Not unless you turn it on. Every Outlook connection starts read-only. An admin can switch a connection to read-write in Settings > Integrations; from then on each write Ruby makes waits for a human's approval before it leaves (by default; the same admin can switch that off) and is recorded in your audit log either way.
Is my Outlook data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use Outlook alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie Outlook to your CRM, accounting, email, and documentation in a single answer.