Messaging
What it does
Read, search, send, and manage messages across connected platforms (Slack, Gmail, Telegram) from a single conversation. Provider-specific tools (gmail_archive, slack_add_reaction) sit beside generic messaging_send / messaging_read / messaging_search.
Setup
Each platform is its own connect. Slack: OAuth, “Connect my Slack.” Gmail: OAuth, “Connect my Gmail.” Telegram: bot token from BotFather, “Connect my Telegram.” User Slack integration and Slack bot are different connects.
Permissions
- OAuth tokens / bot tokens in the local vault. The model never sees raw tokens.
- Sends ask first unless you wrote a trust rule.
- No host-desktop grant.
Common prompts
| You say | What happens |
|---|---|
| “What is happening in #general on Slack?” | Reads recent channel messages |
| “Send a message in #design: mockups are ready” | Posts, after approval |
| “Summarize my unread Slack messages” | Digest |
| “Check my Gmail for anything from Amazon” | Searches Gmail |
| “What did Alice say in #engineering yesterday?” | Finds messages by person and channel |
Configuration
- Each platform is independent. Channel access follows what you authorized.
- Live status:
assistant oauth statusandassistant channels list. Catalog vs live are different answers.
Tips
- You can ask across platforms in one request: “Do I have anything important on Slack or Gmail?”
- Telegram is a bot token, not OAuth.
- See Channels and OAuth integrations.
Related: Gmail, Phone calls.