> ## Documentation Index > Fetch the complete documentation index at: https://docs.mobilerun.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect Gmail, Google Workspace, GitHub, Slack, Microsoft Teams, and OneDrive so the assistant can read your data and, where allowed, act in those tools. The assistant can look things up in services you have connected to your Mobilerun account and combine that with what it does on a phone. Ask about an email, a calendar conflict, a file in Drive, or a pull request, and it answers with a short summary and links to the source items. ## Supported services | Service | Reads | Writes | | --------------- | ------------------------------------------------------------------------ | --------------------------------------------------------- | | Gmail | Search and read emails, your profile | None | | Google Calendar | List and find events | None | | Google Drive | List and find files | None | | Google Sheets | Read spreadsheet contents and structure | None | | Google Docs | Search documents, read a document | None | | Google Slides | Read a presentation | None | | GitHub | Repositories, file contents, issues, pull requests, commits, comparisons | None | | Slack | Channels, conversation history, users, team info | Send a message, open a direct message | | Microsoft Teams | Teams, channels, chats, messages, replies, members | Post to a channel or chat, reply, create a chat | | OneDrive | List, search, download files | Upload, create folders and text files, move, copy, delete | Microsoft services connect with work or school accounts only. Everything not listed under **Writes** is read-only: the assistant cannot send email, edit a spreadsheet, or open a GitHub issue, and it tells you so if you ask. ## Connecting a service Open **Agents → Integrations** in the dashboard and connect the service with its normal sign-in. You can also ask the assistant directly; if the service is not connected yet it shows a **Connect** card in the chat, and you finish the sign-in there. > Connect my Gmail so you can check for verification emails. A connection belongs to your account. The assistant only reaches a service through that connection and only while you ask it something that needs it. ## What the assistant does with a connection It narrows first, then reads. For "did anyone email me about the invoice" it searches for matching messages, reads the few that fit, and answers with the relevant lines and a link to each message. It does not dump your inbox into the chat, and very large results are summarized rather than pasted in full. Typical requests: > Check my calendar for conflicts tomorrow afternoon. > Find the latest spreadsheet in Drive with "Q3 pipeline" in the name and tell me the total in column F. > Summarize open pull requests in the mobile app repo that touch the login screen. > Post a summary of today's scrape results to the #growth channel in Slack. > Upload this CSV to my OneDrive under Reports/September. Writes always happen only when you explicitly ask for them. The assistant does not send a Slack message or move a OneDrive file as a side effect of another task. ## Combining a service with a phone The useful cases pair a connected service with device work: * Read a verification email in Gmail while signing up for an app on a cloud phone. * Take a list of leads from a Google Sheet and look each one up in an app. * Scrape a list on a phone and post the result to Slack or Teams when done. For "tell me when you are finished" without a chat message, use [Notifications](/assistant/notifications) instead of a Slack write; that path works even when the chat is closed. ## Related Phones, apps, accounts, and verification codes from managed numbers and mailboxes. How scraped data and files come back to you. Webhooks when the assistant finishes, fails, or needs you. What the assistant asks before acting.