--- title: Integrations description: Connect Google Drive and Telegram — pick files from Drive, save a package copy, let Lexi write a Google Doc, and get Lexpoint alerts on your phone. product: Lexpoint — Individuals audience: People managing their own Canadian immigration doc_type: guide canonical_url: https://docs.lexpoint.io/individuals/account/integrations/ app_routes: https://my.lexpoint.io/app/settings/integrations, https://my.lexpoint.io/app/settings/notifications requires: The same Google account you use to sign in to Lexpoint (for Drive), Telegram installed on a phone or desktop (for Telegram) last_verified: 2026-09-04 keywords: integrations, Google Drive, Google Docs, Connect Drive, Choose from Drive, Save to Drive, Lexi Google Doc, Telegram notifications, immiwatch_bot, connect Telegram, verification code expired, reply from Telegram license: Documentation © Lexpoint. Quote with attribution and a link to the canonical URL. --- # Integrations Connect the accounts Lexpoint uses for files and alerts at [**Settings → Integrations**](https://my.lexpoint.io/app/settings/integrations). The heading reads *Connect the accounts Lexpoint uses for files and alerts.* Two rows sit on the page: **Google Drive** and **Telegram**. Drive connects on this page. Telegram is listed here so you can see whether it is linked; connecting it still happens on the **Telegram** tab under [Notifications](/individuals/account/notifications/). ```media id: settings-integrations type: screenshot caption: Settings → Integrations, with Google Drive connected and Telegram listed below it. shot: /app/settings/integrations — Drive connected so the Google account caption and Disconnect → are visible, Telegram showing a username and Notifications →. Demo account, light mode, 1440×900. Redact the Google email, Telegram username, and header identity. src: /media/individuals/settings-integrations.webp ``` **Suggest an integration →** opens a support ticket if you want Lexpoint to connect something that is not on the list yet. ## Google Drive Connect Google Drive once. That one connection is what Lexpoint uses to pick files from your Drive, copy an application package into it, and let Lexi save draft notes as a Google Doc. ### Connecting 1. Open [Settings → Integrations](https://my.lexpoint.io/app/settings/integrations). 2. On the **Google Drive** row, press **Connect →**. 3. Finish Google's permission window with **the same Google account you use to sign in**. 4. You return to Integrations. The page says *Google Drive connected.*, and the row caption changes from *Not connected* to that Google account's name. Three things can go wrong on the way back, and each has its own line: | The page says | What to do | |---|---| | *That Google account does not match the one you use to sign in.* | Connect the Google account you already use for Lexpoint, not a different one. | | *The connect window expired. Try again.* | Press **Connect →** again. | | *Google connect did not finish. Try again.* | Press **Connect →** again. | Until Drive is connected, places that need it send you here. Lexi does the same if you ask it to write a Doc before you have connected. ### Choose files from Drive On a case requirement, the **Add** window's **Upload new** tab includes **Choose from Drive →** once Drive is connected, or **Connect Drive to choose files →** if it is not. While the picker opens, the control reads *Opening Drive…*. The picker accepts **PDF, JPEG, PNG, DOC, and DOCX** — the same types as a computer upload. Native Google Docs, Sheets, and Slides are refused with *Google Docs, Sheets, and Slides cannot be imported yet. Download as PDF first.* See [Uploading documents](/individuals/cases/uploading-documents/). ### Save a copy of your package to your Drive On **Packages**, the middle cell is labelled **Your Drive**. It is a copy of the generated package into *your* Drive, not the firm's Drive folder your legal team may use. | The cell reads | Meaning | |---|---| | **Not connected** | Connect first. The action is **Connect Drive →**. | | **No package yet** | Generate the package before you can save it. | | **Ready** | A package exists. **Save to Drive →** copies it. | | **Queued** or **N of M** | The copy is in progress. Stay on the page or come back; it continues. | | **Saved** | The copy is in your Drive. **Open in Drive →** opens it. | | **Failed** | The copy did not finish. The cell shows the error. Try **Save to Drive →** again. | See [Finalization](/individuals/cases/finalization/). ### Let Lexi write a Google Doc In your **private** Lexi panel, ask for a clean Doc — an ImmiReport summary, a letter, or draft notes. Lexi gathers the facts from your account, then pauses: *Save draft notes to your Drive as “Lexpoint · {title}” (not for IRCC filing).* **Confirm** creates the Google Doc. **Skip** does not. After Confirm, Lexi does not paste a docs.google.com link into the chat. A chip with the title and **→** opens the Doc instead. In Drive the file name starts with **Lexpoint ·**; the chip drops that prefix so the row stays short. ```media id: lexi-google-doc-chip type: screenshot caption: Lexi after saving an ImmiReport summary as a draft Google Doc, with the title chip under the reply. shot: /app/dashboard with Ask Lexi open on a chat where Lexi has already saved an ImmiReport summary Google Doc, so the chip (title plus →) is visible under the reply. Demo account, light mode, 1440×900. Redact header identity. Do not press Confirm (the Doc is already created) and do not open the chip. src: /media/individuals/lexi-google-doc-chip.webp ``` The chip is the way into the Doc. The prose will say the summary was saved as a draft Google Doc — not for direct IRCC filing. That limit is the product's, not a suggestion. If Drive is not connected, Lexi points you to Integrations rather than creating a file. Shared Lexi on a case cannot write this Doc; use the private assistant. See [What Lexi can do](/individuals/lexi/what-lexi-does/) and [Asking Lexi](/individuals/lexi/asking-lexi/). ### Disconnecting Drive On the **Google Drive** row, press **Disconnect →**. The caption asks *Disconnect this Drive?*, with **Cancel** and **Disconnect**. Confirming returns the row to *Not connected* and the page says *Google Drive disconnected.* Lexpoint then cannot pick files, copy a package, or create a Doc until you connect again. Files already in your Drive stay in your Drive — delete those in Google if you do not want them. ## Telegram Telegram gives you Lexpoint notifications on your phone as they happen, and lets you reply to a case message without opening the app. It is an addition to email, never a replacement for it — the required email categories keep arriving either way. Everything happens through one bot: **@immiwatch_bot**. The **Telegram** row on Integrations shows *Not connected*, or your Telegram username once it is linked. **Notifications →** opens the **Telegram** tab on [Settings → Notifications](https://my.lexpoint.io/app/settings/notifications). ### Connecting 1. Open the **Telegram** tab and press **Connect Telegram**. 2. Lexpoint shows **Scan or Click to Connect** — a QR code, a **six-digit code**, and an **Open in Telegram** button. 3. Use whichever suits where you are: - **On a computer, with your phone in hand** — scan the QR code with your phone's camera. - **On your phone** — tap **Open in Telegram**. The bot opens with the code already attached. - **By hand** — open Telegram, search for **@immiwatch_bot**, start the chat, and send the six-digit code as a message. 4. The bot replies *Connected. Hey [your name], your Telegram is now linked to your Immigratic account.* 5. The page moves to **Telegram Connected** on its own, showing your Telegram username and the date you connected. ```media id: settings-telegram-qr type: screenshot caption: The connect screen, with the QR code, the six-digit code, and the Open in Telegram button. shot: /app/settings/notifications?tab=telegram → press "Connect Telegram" so the "Scan or Click to Connect" panel with QR, code, and button is showing. Demo account, light mode, 1440×900. Blur the QR code and redact the six-digit code. src: /media/individuals/settings-telegram-qr.webp ``` :::caution[The code is valid for ten minutes] The panel says so under the button: *Code expires in 10 minutes*. Send an expired code and the bot replies *This code has expired. Please get a new code from Settings -> Notifications in the app.* Nothing is broken — press **Cancel**, then **Connect Telegram** again. ::: The page watches for the connection itself, so you do not need to reload. If you would rather not wait, **Refresh Status** checks immediately. ### If you tapped Start without the code This is the common stumble. Opening the bot and pressing Telegram's **Start** button does not link anything unless the code travelled with it. The bot answers a bare `/start` with *Welcome. To connect your account, go to Settings -> Notifications in the app and send the 6-digit code shown there.* The fix is to send the code as an ordinary message in that same chat. The pending panel says the same: *Send the code again if you already tapped Start without it.* ### If the code is refused Sending a code that no longer matches a pending connection gets *Invalid or expired code. Please get a new code from Settings -> Notifications in the app.* Return to the Telegram tab, press **Cancel**, and start again. ### What you get once connected The connected panel states the rule: *You'll receive Telegram notifications for all enabled categories above.* Your Telegram messages mirror your email preferences rather than having settings of their own — turn a category off under **Email Preferences** and it stops arriving in both places. See [notification preferences](/individuals/account/notifications/) for which categories are optional and which are always on. ### Replying from Telegram The bot is two-way. You can answer a Lexpoint case message from your phone, and your reply lands in the case thread it belongs to. **Use Telegram's reply function on the specific Lexpoint message.** That reply is how the bot identifies which thread you mean. A message sent into the chat without one is answered with *Reply directly to a Lexpoint message in this private chat so I know which case thread to post into* — the bot declines to guess rather than posting your words in the wrong place. Four limits are worth knowing before you rely on it: | What you do | What happens | |---|---| | Reply to a Lexpoint message with text | Posted into the matching case thread | | Send a message with no reply target | Rejected, with guidance to reply to a message | | Send a photo, document, or other attachment | Rejected — *Attachments are not supported here yet. Please upload documents in the app, or reply with plain text* | | Reply to a very old message | *That message can no longer accept replies here. Please continue the conversation from the app* | :::note[Private chat only] The bot works in a direct private chat and nowhere else. Add it to a group and it answers *For privacy, this bot only works in a direct private chat.* This is deliberate — your immigration notifications should never be one mis-tap away from a group of people. ::: Documents always go through the app. Telegram is for text replies and alerts, not for sending identity documents into a chat. ### Disconnecting Telegram Press **Disconnect Telegram** on the connected panel and confirm. The bot sends a closing message — *your Telegram has been disconnected from Immigratic. You won't receive notifications here anymore* — and Telegram messages stop immediately. Your email preferences are untouched. To reconnect later, come back to the same tab and run the connection again with a fresh code. ## Related - [Settings overview](/individuals/account/settings-overview/) — where Integrations sits among the other settings - [Notification preferences](/individuals/account/notifications/) — which emails Telegram mirrors, and which cannot be switched off - [Uploading documents](/individuals/cases/uploading-documents/) — Choose from Drive on a requirement - [Finalization](/individuals/cases/finalization/) — Your Drive on Packages - [What Lexi can do](/individuals/lexi/what-lexi-does/) — the Drive Doc write, and that it needs Confirm - [Cases](/individuals/cases/) — the case threads your Telegram replies post into ## Frequently asked questions ### Does a Lexi Google Doc replace a file I would send to IRCC? No. The confirmation and the chat both say the Doc is a draft, not for IRCC filing. Use it as notes. Filing still goes through your case package. ### Can I import a Google Doc, Sheet, or Slide into a requirement? Not yet. The picker accepts PDF, JPEG, PNG, DOC, and DOCX. For a native Google file, download it as PDF first, then choose that PDF. ### Why was my Google account refused? Drive must be the same Google account you use to sign in. If it is not, the page says That Google account does not match the one you use to sign in. ### Which Telegram bot is the real one? @immiwatch_bot, and only that one. Lexpoint never asks you to start a different bot, and never asks for your code anywhere except in that private chat. ### Can I reply to a Lexpoint message from inside Telegram? Yes, but you must use Telegram's reply function on the specific Lexpoint message. That is how the bot knows which case thread your words belong in. A plain message with no reply target is rejected with guidance rather than posted somewhere arbitrary. ### Does connecting Telegram stop my emails? No. Telegram is an additional channel. Email preferences are set separately on Notifications, and connecting or disconnecting Telegram does not change them. ### My Telegram code expired before I sent it. Is something broken? No. Codes are valid for ten minutes by design. Press Cancel, then Connect Telegram again for a fresh one.