# Connect your email Source: https://help.mucka.ai/integrations/connect-your-email Category: Integrations Last updated: 2026-09-24 > Link your Gmail so you can read your email inside Mucka, against the customer it is about. The Inbox is in early access, so we switch it on for the businesses that ask rather than for everyone at once. Open [**Skills**](/skills), find Inbox and hit **Request access**. We will come back to you on your support ticket, and once it is switched on you install it yourself from the same page. Connect your email and you can read it inside Mucka, on the same screen as the job it is about. ## What works today Gmail. Microsoft 365 and other providers are coming. When you first connect, Mucka reads the last 30 days. The page says it is fetching and fills in on its own, usually inside a minute — you do not have to sit and watch it, and it finishes whether the page is open or not. After that Mucka keeps the mailbox up to date every few minutes and shows the conversation on the Inbox page, just under Actions in the menu. Where the sender is somebody already on your books, the email shows on their record too. ## Send your quotes and invoices from your own address By default Mucka sends your paperwork on your behalf, and replies come back to you. Once a mailbox is connected you can have quotes, invoices, certificates and job reports go out **from your own address** instead, so they land like any other email you send. Go to **Settings → Connections → Email** and pick the address under *Send my quotes and invoices from*. Three things worth knowing before you change it: - It changes **where the customer's reply goes** — into that mailbox, not wherever they were landing before. - Only the **workspace owner** can change it. Connecting your own mailbox is one thing; deciding what address the business sends from is another. - You can only pick a **shared mailbox or your own**. Somebody else's private mailbox is theirs — ask them to share it first. If that mailbox ever stops working, Mucka goes back to sending on your behalf rather than letting a quote sit unsent. ## Mucka drafts your replies Ask Mucka to answer an email — "reply to Karen and say Thursday's fine" — and it writes the reply and puts it on a **Reply ready — Not sent** card. The same reply sits in your Gmail **Drafts**, inside the conversation, so it is there whichever one you open first. Read it, then tap **Send reply**. It goes from your own address to whoever emailed you last in that conversation. Mucka never picks who it goes to. Once it is switched on for your account, Mucka also drafts one **on its own** when an email needs answering: somebody asking for work, a customer asking about a job, or a complaint, when it needs an answer today or soon. Supplier mail, receipts, newsletters and out-of-office replies are left alone. It only drafts for mail that has just arrived, never for the backlog it read when you first connected. Two things worth knowing: - **Changed it in Gmail, or sent it from there?** Then the card will not send. It tells you, and your version is the one that counts. That is how you avoid a customer getting the same reply twice. - **The card is only yours.** It quotes your email, so nobody else on the team sees it, even people who approve everything else. On WhatsApp or a phone call, Mucka reads the reply back to you and sends it when you say yes. ## Mucka does the little bits of admin an email implies - **Somebody new asking for work?** The reply Mucka drafts asks for their best number and a good time to call. Sending it also saves them to your client book as a **Lead**. Untick the box on the card if you'd rather not. - **A customer gives you a new number or email address?** You get a card to add it to their record. Mucka never overwrites a number you already have: a different one goes in as their second number. - **"Please go ahead"?** A card to mark their quote accepted, and to book it in if they said when. - **"Can we move it to Friday?"** A card to move the visit. **"Please cancel"?** A card to cancel it, which also tells the engineer. - **"The key's in the key safe, code 4471"?** A card to save it on the property, under Getting in, so the engineer has it on the job. - **A new supplier writing in?** A card to save them to your contacts as a supplier. You're only asked once per supplier. - **"I've paid"?** A card to record the payment against their invoice. It reminds you to check the money has actually arrived before you tap. - **"Can you send me the gas safety certificate?"** The reply Mucka drafts has the certificate attached. If Mucka can't tell which one, it attaches nothing. - **Anything else they need?** A to-do on your notepad. If Mucka can't tell which quote or which visit they mean, you get a to-do instead of a guess. Every card quotes the line of the email it came from, and nothing changes until you tap it. You can also change the reply's wording on the card before it goes. ## Supplier invoices go straight to your books When a supplier emails you an invoice or a receipt, Mucka reads the attachment (a PDF or a photo) and gets it ready for you: - **With Xero, QuickBooks, FreeAgent or Sage connected**, you get the usual **Add to accounts** card: supplier, total, VAT and date read off for you, an expense account picked, and it goes in as a bill still to pay. Change anything before you approve. Pick a job on the card and the cost goes on that job too. - **With no accounts app**, you get a **Put on a job** card instead. Choose the job and the cost goes on it, with the invoice attached. Nothing goes into your books or onto a job until you approve the card. Mucka only does this for mail that arrives after it is switched on, never the old mail it read when you first connected. If the same receipt turns up twice, say as an invoice and a receipt for one payment, you only get one card. ## What is not built yet - Putting the conversation on the right job on its own That is being built now. ## Connect a mailbox 1. Install **Inbox** from [**Skills**](/skills) once it is switched on for you. Mucka opens a short setup: what the Inbox does, then **Connect Gmail**. (Later, it is always under **Inbox** in the menu, and in **Settings → Connections**.) 2. Sign in to Google. Google will say it **hasn't verified the app**. That is expected while we are in early access: tap **Advanced**, then **Go to Mucka**. 3. Leave the email permissions ticked. That last one matters. Google lets you sign in while switching the email permissions off, and if you do, Mucka can see which account you picked and nothing else. If that happens, the Inbox page says so and you can connect it again. ## Who can see it A mailbox you connect is yours. Nobody else in the workspace sees it unless you share it, and sharing is a choice you make per mailbox. Anyone on your team with permission to see the Inbox can read a shared mailbox. Your own stays yours. ## Mucka never sends an email on its own Every reply Mucka writes waits for you to read it first. Nothing goes to a customer over your name until you tap Send or say yes. ## What Mucka keeps, and getting rid of it Mucka keeps a copy of the mail in the connected account so it can show it to you and search it. You choose how long that copy is kept. Disconnect the mailbox and the copy is deleted — the messages and the attachments both. Your email is never used to train anything.