Coming soonOOMU is launching soon. Downloads will open at launch.
OOMU
← All documentation

How-to guides

Connecting services

Let OOMU work with your email, calendar, files, and chat, and reach you where you already are, without ever pasting a password into the interface.

Open Connections in the OOMU sidebar. You will see two views:

  • Apps OOMU can use connects the work and personal services OOMU can draw on while it helps you.
  • Message OOMU lets you talk with OOMU from Telegram, Discord, or Slack.

Connecting a service grants access. It does not approve every action. Routine, read-only requests can proceed within the access you have already granted. OOMU always asks first before anything consequential: creating, changing, sending, sharing, or deleting.

Apps OOMU can use

Open Apps OOMU can use and choose a service. Each one shows an honest status, and, before you approve, the exact access it will have. Sign-in happens on the service's own secure page. OOMU never asks you to paste a password, client secret, or API token into the app.

Apple apps

Apple apps use the permissions already built into macOS. There is no OOMU account to create and no password to paste.

Today OOMU can:

  • read Calendar events;
  • find Contacts;
  • read selected Mail messages;
  • read basic information about a limited set of photos;
  • read basic information about a limited set of songs; and
  • create or change Calendar events, after you approve.

To use one:

  1. Ask OOMU to do something specific, for example, "What is on my calendar tomorrow?"
  2. The first time, macOS may ask whether OOMU can control or access that app.
  3. Read the macOS prompt and choose Allow if it matches what you intended.
  4. Return to OOMU. If macOS asks you to restart OOMU, quit and reopen it once.

If you turned an app down earlier, open System Settings → Privacy & Security → Automation, find OOMU, and switch on the app you want it to use. Other privacy categories may appear when an app needs them.

If an Apple app is not in the list above, this connection does not reach it yet.

Google Workspace

Google Workspace connects Gmail, Google Calendar, and Google Drive through Google's own secure sign-in page.

  1. Open Connections → Apps OOMU can use → Google Workspace.
  2. Choose Connect.
  3. Review the access OOMU will request, then choose Continue to Google Workspace.
  4. Sign in to the Google account you want to use and approve the access you recognize.
  5. Return to OOMU and wait until the account shows Ready.
  6. Under Project access, choose Use in all my projects, or pick only the Projects that need this account.
  7. Choose Save project access. OOMU will not use the connection in a Project until you save this choice.

The connection can read Gmail and create Gmail drafts, read Google Calendar and change it after you approve, and search or read Drive. Creating a Gmail draft never sends it.

Slack for work

Slack uses one shared account with two separate capabilities:

  • Work access lets OOMU search and read the Slack conversations your account can already see. OOMU can prepare a reply for your review, but work access alone cannot post it.
  • Messaging access lets approved people talk with OOMU from approved Slack conversations. It is optional and may not be included in every OOMU version. See Slack messaging below.

Work access connects straight from OOMU to Slack using Slack's secure desktop sign-in. OOMU never asks for your Slack password, client secret, or an API token.

  1. Open Connections → Apps OOMU can use → Slack.
  2. Choose Connect.
  3. Review the requested access, then continue to Slack.
  4. Choose the right Slack workspace and approve the access Slack shows. Your workspace may require an administrator to approve OOMU.
  5. Return to OOMU and wait until the workspace shows Ready.
  6. Set and save Project access.

OOMU can use only the conversations visible to the Slack member who connected the account, and only in the Projects you saved. Any reply it prepares stays a draft until Slack messaging is enabled and you approve the send.

If Slack shows "Unavailable." That OOMU build does not include the public Slack app identity needed to open Slack sign-in. There is no password, API key, or local setting for you to supply. If Slack instead reports that the redirect URL does not match, the app registration needs a fix; do not paste credentials or keep retrying. Report it to OOMU support. The registered desktop callback must be http://localhost:53682/oauth/callback.

Microsoft 365

Microsoft 365 connects a Microsoft account through Microsoft's own secure sign-in page. Access starts small, and you can add individual capabilities later. Some organization features, including SharePoint and Teams, need a work or school account.

  1. Open Connections → Apps OOMU can use → Microsoft 365.
  2. Choose Connect Microsoft 365.
  3. Review the requested account access, then choose Continue to Microsoft.
  4. Sign in with the Microsoft account you want OOMU to use.
  5. Return to OOMU and wait until the account shows Ready.
  6. Set and save Project access.
  7. Choose Review access whenever you want to add a capability. OOMU shows the exact new permission before it opens Microsoft sign-in again.

Depending on the access you add, OOMU can search or read Outlook mail, prepare an unsent Outlook draft, read calendars, prepare a calendar event locally, search or read OneDrive and SharePoint, update a bounded file after approval, search a selected Teams chat, or prepare a Teams message locally. It never asks for permission to send Outlook mail, send invitations, share files, or post to Teams through this connection.

If OOMU says Microsoft 365 is not available in this version, the app was built without the secure Microsoft sign-in identity. There is nothing to enter locally; use a version that includes Microsoft 365 access.

Custom tools

Custom tools appear only in developer builds. They use tool providers configured outside the normal Connections screen. If you do not see Custom tools, nothing is missing from the standard OOMU experience. If you do see it, follow the instructions from whoever configured that provider; OOMU can use only the actions and destinations that provider reports. For how these fit into a workflow, see Building automated workflows.

Message OOMU

Messaging connections work while OOMU is running on your Mac. Keep the Mac awake and online when you expect OOMU to receive or answer messages.

Each messaging connection has an owner boundary: OOMU accepts requests only from the account you approve. Discord and Slack can be narrowed further to specific conversations.

Telegram

You need two values: a Telegram bot token and your numeric Telegram chat ID.

Create the bot. In Telegram, open the official BotFather, send /newbot, and follow the prompts. BotFather gives you a bot token; treat it like a password. Then open your new bot and send it /start, because a bot cannot start the conversation for you.

Find your chat ID. Telegram does not show it in normal settings, so ask the official Bot API for it. Open Terminal, paste the command below, and press Return. When prompted, paste the bot token and press Return; it stays hidden and is not saved to your shell history.

read -s "token?Telegram bot token: "; echo; curl --silent "https://api.telegram.org/bot${token}/getUpdates" | python3 -m json.tool; unset token

In the result, find the most recent message, then its chat, then id. That number is your chat ID.

Connect it in OOMU. Open Connections → Message OOMU → Telegram → Configure, paste the bot token and your chat ID, then choose Save. OOMU checks the token before saving. Send the bot a short test message from the approved Telegram account to confirm it works.

For more detail, see Telegram's bot introduction and getUpdates reference. If the token is ever exposed, use BotFather to revoke it, create a new one, and replace it in OOMU.

Discord

You need a Discord bot token, your Discord user ID, and, recommended, the IDs of the channels where OOMU may listen and reply.

  1. Open the Discord Developer Portal and create an application.
  2. Open the application's Bot page. Create or reset the bot token and save it somewhere secure. Discord will not show it again.
  3. On the Bot page, turn on Message Content Intent. OOMU needs it to read ordinary server messages.
  4. Open Installation. Configure a server installation with the bot scope and only the permissions OOMU needs: View Channels, Send Messages, and Read Message History.
  5. Use the installation link to add the bot to a server you control. A server administrator may need to approve it.
  6. In Discord, open User Settings → Advanced and turn on Developer Mode.
  7. Copy your user ID from your profile. Copy each allowed channel ID from the channel's context menu. Discord's ID guide shows the current steps.
  8. In OOMU, open Connections → Message OOMU → Discord → Configure.
  9. Paste the bot token and your user ID. Add one allowed channel ID per line.
  10. Choose Save, then send a short test message in an allowed channel.

Leaving the channel list blank allows every channel the bot can see. For a safer setup, list only the channels you intend to use. Discord documents the full process in its getting-started guide.

Slack messaging

Slack messaging reuses the same Slack workspace you connected under Apps OOMU can use. You do not paste a token, and you do not connect the workspace twice.

This capability needs OOMU's secure real-time Slack messaging service, and its availability is shown separately from Slack work access. If Message OOMU → Slack says real-time messaging is unavailable, Slack work access still connects and works normally; only inbound and outbound Slack messaging is missing from that build.

When Slack messaging is available:

  1. Open Connections → Message OOMU → Slack.
  2. If Slack is not connected, choose Install OOMU in Slack. If it is already connected for reading, choose Turn on messaging.
  3. Finish the secure Slack sign-in and return to OOMU.
  4. Choose the one Slack member who may ask OOMU to act.
  5. Choose at least one channel or direct message where OOMU may listen and reply.
  6. Choose Save.
  7. Send OOMU a short test message from the approved member in an approved conversation.

If no conversations appear, add OOMU to the Slack conversation first, then try again. If the workspace blocks the added access, ask a Slack administrator to approve OOMU. Turning on Slack messaging does not remove Project access controls and does not approve unrelated consequential actions.

Review, repair, or remove a connection

For a connected work app, open Connections → Apps OOMU can use, choose the service, then:

  • use Check connection to verify it;
  • use Reconnect if access expired or was revoked;
  • use Review access to see what OOMU can use;
  • change and save Project access to narrow where the account is available; or
  • use Remove connection to remove the saved sign-in from this Mac.

Removing a connection from OOMU does not delete anything in the connected service. For a complete revocation, also remove OOMU from that service's own account settings. For Telegram, Discord, or Slack messaging, open Connections → Message OOMU and choose Disable to stop that channel.

If something does not work

  • Slack work access is available but Slack messaging is not. This is intentional, capability-level availability, not a broken account. You can still use Slack under Apps OOMU can use. Real-time Message OOMU support needs a build that includes OOMU's secure Slack messaging service.
  • A work service says it is unavailable in this version. There is nothing to configure locally. Install a version of OOMU that includes the named sign-in identity.
  • Secure sign-in opened but OOMU did not finish connecting. Return to OOMU, wait a moment, then use Check connection or Reconnect. Make sure you completed sign-in in the account and workspace you intended.
  • The account is connected but OOMU cannot use it in a Project. Open the connection, choose the Project under Project access, and select Save project access.
  • An Apple app stays blocked. Review OOMU under System Settings → Privacy & Security → Automation, then quit and reopen OOMU if macOS asks.
  • Telegram receives nothing. Make sure you sent /start to the bot, used the chat ID from that same conversation, and kept OOMU running.
  • Discord receives nothing. Confirm Message Content Intent is on, the bot can view and send in the channel, your user ID is correct, and the channel is on OOMU's allowlist.
  • Slack shows no conversations. Add OOMU to the channel or direct message you want, then reload the conversation list.

When in doubt, narrow a connection rather than widen it. Give OOMU only the accounts, Projects, people, and conversations it actually needs.