Outlook

Operate Outlook through your OOMOL-connected account. This skill calls the outlook connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Outlook. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "outlook" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "outlook" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• create_draft — Create a new Outlook draft message with subject, body, recipients, and other writable message properties. [write]
• get_mailbox_settings — Get the current Outlook mailbox settings, including automatic replies, locale, time zone, and working hours.
• get_message — Get a single Outlook message by message ID, including message metadata and optional body formatting.
• get_profile — Get the current Outlook account profile from Microsoft Graph so you can identify the connected mailbox.
• list_mail_folders — List the root-level Outlook mail folders for the connected mailbox, with optional hidden folders and field selection.
• list_messages — List Outlook messages from the mailbox or from a specific mail folder, with support for OData filters, sorting, field selection, and pagination.
• reply_email — Reply to an existing Outlook message with either a comment or a replacement body, and optionally add more recipients to the reply. [write]
• send_draft — Send an existing Outlook draft message by message ID. [write]
• send_email — Send a new Outlook email in a single operation, without creating a standalone draft first. [write]
• update_draft — Update an existing Outlook draft message. Use this to revise the subject, body, recipients, or other draft-only properties before sending. [write]
• update_mailbox_settings — Update Outlook mailbox settings such as automatic replies, locale, time zone, working hours, and date or time formatting. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Outlook state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Outlook is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:

  https://console.oomol.com/app-connections?provider=outlook
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Outlook homepage: https://www.microsoft.com/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook