Bob with Microsoft Outlook: bring email work into Slack

Matthew, founder of Bob · Published July 30, 2026

Short answer

Bob can connect to Microsoft Outlook through the connection catalog and use the authenticated actions that the service exposes for the connected Microsoft account. Microsoft Graph supports mailboxes, folders, messages, search, replies, drafts, and sends through its Outlook mail API. The exact subset Bob can invoke depends on the live connection, granted scopes, tenant policy, and account permissions.

That distinction matters. Outlook is available in Bob, but this page does not turn every Microsoft Graph endpoint into a guaranteed Bob action. Ask Bob for the job; he can inspect the available authenticated actions, use what is connected, and say clearly when a required action is unavailable.

Five useful Bob and Outlook workflows

1. Summarize an important thread

"Find the latest Outlook thread with Contoso and summarize the decisions, unanswered questions, and owners."

This is a read-oriented starting point. It turns mail context into decisions without changing the mailbox.

2. Prepare a grounded reply

"Use the Contoso thread, the Salesforce opportunity, and the launch plan in OneDrive to prepare a reply. Do not send it."

Bob is most useful when Outlook is one source in a complete job, not the final destination for another generic summary.

3. Find overdue follow-ups

"Find customer threads from the last two weeks where we promised a next step and have not followed up. Show me the evidence."

Confirm the live Outlook connection exposes the search and message actions needed for this request.

4. Send an approved update

"Send the release update we just approved to the recipients on the thread."

Microsoft documents programmatic message creation and sending in Graph. Bob treats the send as an external write and asks by default.

5. Build a recurring account brief

"Each weekday, summarize new mail from our priority accounts and join it with Salesforce stage changes."

Bob's schedule can deliver the brief in Slack. Validate the first run before turning it into a standing workflow.

Connection scope and setup

1. Ask Bob in Slack to connect Microsoft Outlook.
2. Open the hosted connection flow and authenticate with Microsoft.
3. Review the requested scopes and tenant consent screen.
4. Return to Slack and ask Bob to retry the job.

The Outlook catalog connection is workspace-scoped in Bob today. Choose the acting identity deliberately. A shared connection should use the least-privileged account appropriate for the team, not an administrator merely because that account is convenient.

Limits worth knowing

• Catalog actions vary. Confirm the exact Outlook actions Bob discovers at run time.
• Tenant policy wins. Microsoft administrators can limit consent and mailbox access.
• Workspace scope needs an owner. Be explicit about which mailbox identity the team expects Bob to use.
• Writes ask by default. Sending, moving, or changing email is consequential and should stay reviewable.

FAQ

How does Bob connect to Microsoft Outlook?

Through a hosted OAuth flow. The catalog connection is workspace-scoped today, so the connected identity should be chosen deliberately.

What can Bob do with Outlook?

Bob can use the authenticated Outlook actions available in the live connection and permitted by Microsoft. Exact actions are discovered at run time.

Does Bob ask before sending email?

Yes. Sending or changing external mail asks by default unless a matching policy has been granted.

Can Bob access every Microsoft 365 mailbox?

No. Access is bounded by identity, tenant policy, OAuth scopes, and the available connection actions.

Start read-only, then add the smallest useful write

Begin with one thread summary or follow-up report and verify the sources. Add OneDrive, Microsoft Excel, or Salesforce when the job needs more context.