AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
{
"section_id": "integrations",
"title": "Integrations",
"markdown": "**What it is:** The channels that connect the Executive to where your team already works, so proposals, updates and replies reach people in familiar tools instead of only the web app.\n\n**What it does:**\n\n- **Slack / Google Chat:** receive direct messages and mentions, reply in threads, and send proposals and alerts.\n- **Discord / Telegram:** direct-message conversations for questions, proposals and approvals.\n- **Email:** the Executive reads its own inbox on a regular poll and replies from its own address.\n- **Google Workspace:** the Executive can send and draft Gmail (recipients limited to your People roster) and manage Calendar events, including Google Meet links.\n- **Microsoft 365:** the Executive can send, reply to and draft Outlook mail and manage Outlook calendar events with Teams links (recipients and attendees limited to your People roster). Its own inbox and calendar can run on either Google or Microsoft. This is a per-install setting, not a per-message choice.\n- **MCP:** expose the Executive's specialist council and company context to external AI tools.\n- Everything the Executive sends on these channels as itself ends with a line saying it is an AI assistant, unless the install turns that off.\n\n**How to use:**\n\n*Before anyone can use a channel,* an administrator turns it on with environment settings (see *Setup* below) and restarts the app. There is no page in the app for turning channels on or off. Then add each person's channel ID under **People → Contact & routing** (**Slack user ID**, **Discord user ID**, **Telegram chat ID**). The person's **Preferred channel** there decides where proposals routed to them are sent. **Settings → Advanced → Setup status** then shows whether each channel is working, when it last received a message, and what to do if it isn't working.\n\n*Talking to the Executive*\n\n- **Slack**: DM the app, or @mention it in a channel; it replies in a thread. Keep replying in that thread without mentioning it again.\n- **Discord**: DM the bot, or @mention it in a server channel (it answers in a new thread). Or use the slash commands `/ask` and `/today`.\n- **Telegram**: message the bot directly in a private chat. Text, documents, photos and voice notes all work.\n- **Google Chat**: DM the app, or add it to a space and @mention it.\n- **Email**: send mail to the Executive's address. It picks up unread inbox mail on a regular poll (every 60 seconds unless the install changes it).\n- **Signing off a paused workflow**: reply in the thread on Slack, Discord or Telegram: \"yes\", \"LGTM\", \"no\", \"not now\".\n\n*Who it answers*\n\n- Slack, Discord, Telegram and email answer only people on your People list.\n- When someone who isn't on the list writes to it directly, their message is held. They get one fixed reply saying it arrived and is waiting for confirmation. The owner gets a card on Home and a message on their preferred channel asking who it is. Once the owner confirms them, the held messages are answered.\n- In a Slack channel the \"waiting\" reply is shown only to the sender. In a Telegram group, nothing is sent.\n- Google Chat answers anyone in a space it is in. It reads attached files only from people on your People list.\n- Files shared on Slack, Discord, Telegram and Google Chat are read only for people on your People list.\n- Voice notes recorded in Slack, Discord or Telegram are written out as words when speech to text is set up, and the reply is just the answer. Other audio files, and recordings attached to email, are read like a document.\n\n*Writing as you*\n\n- **Act as me** (under **Delegate**) works in a direct message to the Executive on Slack or Discord and in a private Telegram chat, as well as in the web app. It does not work in a shared channel or thread, on Google Chat or by email. See the Delegate section of this guide.\n\n**Example (Slack):** *\"@Executive what's blocking the Q3 hiring plan?\"* The answer arrives in a thread, and you can follow up there.\n\n*Setup (administrators)* — each channel is switched on with environment settings:\n\n| Channel | Settings |\n|---|---|\n| Slack | `SLACK_BOT_TOKEN`, `SLACK_APP_TOKEN` (Socket Mode). Or, on a server Slack can reach, leave `SLACK_APP_TOKEN` unset, set `SLACK_SIGNING_SECRET` and point the app's Event Subscriptions at `/webhook/slack` |\n| Discord | `DISCORD_BOT_TOKEN`, `DISCORD_APP_ID`; enable the bot's Message Content intent (see the README). Optional: `DISCORD_NOTIFY_CHANNEL_ID` for alerts |\n| Telegram | `TELEGRAM_BOT_TOKEN`, `TELEGRAM_WEBHOOK_SECRET`; webhook at `/webhook/telegram`; see `docs/telegram_setup.md` |\n| Google Chat | `GOOGLE_CHAT_PROJECT_NUMBER` plus a service account (`GOOGLE_CHAT_SERVICE_ACCOUNT_FILE` or `GOOGLE_CHAT_SERVICE_ACCOUNT_EMAIL`); webhook at `/webhook/google-chat`; see `docs/google_chat_setup.md` |\n| Email, Gmail & Calendar | `EXEC_EMAIL_ADDRESS` plus the Google Workspace connection — see `docs/deployment.md`. `EMAIL_POLL_INTERVAL_SECONDS` sets how often the inbox is read |\n| Microsoft 365 | `MS365_MCP_CLIENT_ID`, `MS365_MCP_TENANT_ID`, `MS365_MCP_EXPECTED_USERNAME`, then a one-time sign-in with `ms365-mcp-launch.sh --login` — see `docs/deployment.md`. `EMAIL_PROVIDER` / `CALENDAR_PROVIDER` choose whether the Executive's own inbox and calendar are Google or Microsoft |\n\n*Use the Executive from other AI tools (MCP)* — the API serves an MCP endpoint at `/mcp`; clients authenticate with the backend shared secret. In Claude Code:\n\n```bash\nclaude mcp add --transport http open-executive http://localhost:8000/mcp \\\n --header \"x-api-key: YOUR_BACKEND_SHARED_SECRET\"\n```\n\nOther MCP clients take the same URL and `x-api-key` header. They get `ask_executive`, `consult_specialist`, `search_knowledge` and `list_workflows`, plus read-only company context: the company profile, the Today briefing, recent activity, the People roster, department state, and remembered decisions, initiatives and advice.\n\n- They answer as the person signed in, with the same rules as the web app: remembered decisions, initiatives and advice and recent activity are the owner's alone, and the Today briefing and People roster need someone on your People list. With no sign-in in front of the endpoint, the client is the owner.\n- By default `ask_executive` reads and advises only. It never sends, posts, books or changes anything; to do that, ask in Open Executive itself.\n- To let an AI tool act, have it send the header `x-mcp-client-actions: on` with the `x-api-key` (with no backend shared secret set, `MCP_CLIENT_ACTIONS=true` turns it on instead). It can then make your changes inside Open Executive (alerts, open loops, follow-ups, the watchlist, goals, decisions, remembered facts and the company profile), with the same permissions you have in the web app. It can't change your People list. A message or a meeting it asks for is left as an approval card for you to approve in the web app, or it goes on its own when **Handle it for me** is on, everyone on it has been on your People list for at least a week and nothing on it is sensitive. It never runs scripts or workflows, connects tools or reads your mailbox, and the Audit Log shows which AI tool asked.\n\n*Note: every channel is recorded in the Audit Log. Replying to approve a paused workflow works on Slack, Discord and Telegram only, not email or Google Chat. While the Executive is paused, chat and direct messages on every channel still get answers.*\n",
"mermaid": null,
"generated_at": "2026-10-15T21:00:00Z"
}