Connect your Google Calendar and your Mucka jobs and appointments land in it automatically, as you book them. Change something either side and the other keeps up.
Connect your account
Head to Settings → Connections → Integrations → Google Calendar and tap Connect.
Google asks you to sign in and grant Mucka access to your calendar. The permissions you're granting:
- See and edit events on all your calendars (so Mucka can write new jobs in)
- See the list of your calendars (so you can choose which of your other calendars Mucka reads)
- Your email address and basic profile (so Mucka can show "Connected as ryan@gmail.com")
Approve and Google sends you back to Mucka with a "Connected" confirmation.
Personal vs work Google accounts
Mucka works with both:
- Personal Gmail (your own calendar)
- Google Workspace (your business calendar if you use Google for work)
Connect whichever calendar you want your Mucka jobs to appear in. Most engineers connect their work calendar so their team can see what they're booked on.
Each engineer connects their own
Calendar connections are per-user. Every engineer connects their own Google account. The owner doesn't connect everyone, each person picks their own calendar.
The owner can see (in their own Integrations tab) which engineers have connected, and disconnect them if needed for offboarding.
More than one calendar
Got a work calendar, a personal one and one your partner shares with you? Mucka can read all of them.
Under Calendars Mucka reads on the same page you'll see every calendar on your Google account. Switch on the ones you want, and for each one Mucka asks: Should this block time in your diary?
- Yes, I'm busy. Events on it block your time, exactly like your main calendar. Nothing gets booked over them, not even by the AI receptionist.
- No, just show it. Events show on your diary, faded, so you can see them, but Mucka still books work over them. Good for a partner's calendar.
You can change the answer any time, including for your main calendar. Mucka reads up to five extra calendars.
One event at a time works too: an event you've set to show as free in Google shows on your diary but doesn't block the time. All-day events are the exception. Google sets those to free unless you change it, so Mucka keeps treating an all-day event as busy. That way a holiday never gets booked over.
Your jobs still only go onto your main calendar. The others are read, never written to.
Events from a calendar someone shared with you show to your team as "Personal time" unless you tick Show event titles to your team under it.
If you connected before October 2026 you'll see Let Mucka see your other calendars instead. Tap it, approve the extra permission on Google's screen, and the list appears.
What syncs
-
Mucka jobs → Google Calendar automatically as you schedule them
-
Google Calendar changes → Mucka when you reschedule or cancel in Google
-
Cancel in one, cancel in both so you don't end up double-booked
-
Pencilled bookings show as pencils, titled Pencilled and marked tentative, until you confirm them. Want only confirmed work on your calendar? Switch off Pencilled bookings on your calendar in Settings → Work → Diary.
-
Personal appointments and time off both ways, so nothing gets booked over them — not even by the AI receptionist
-
Your engineers' colours, if you've set any. A job arrives in the colour of whoever it's assigned to — see Colour-code your team in the diary. That's worth having on the calendar of whoever syncs all company jobs, where everybody's work lands in one column. Or colour every job by where it's at instead (booked, invoiced, paid and so on): see Colour your calendar by where each job is at.
Reminders you've set on a Mucka appointment come across as Google's own popup alerts.
What a job looks like on your calendar
The title starts with the job number, then the customer and the job: J-014 · Pat Example — Boiler service. That's the number your engineers read to the merchant, and it tells two jobs at the same customer apart at a glance. Jobs already on your calendar pick it up the next time they change.
Each job goes on at the job's own address. If the job is at a property, that's the property, not the customer who pays the bill, so on a rented house it's the house and not the letting agent's office. Tap the address and your maps app takes you there.
The details on the event say who the customer is and how to reach them, then the address, what the job is, and how you're getting in (Key collect, Someone home and so on) if you've recorded it. Your own notes on the job follow underneath.
Disconnect any time
Same page has a Disconnect button. Tapping it:
- Removes Mucka's access to your Google Calendar and stops syncing straight away
- Takes your Google events off your Mucka diary. Every busy block from that Google account (and any extra calendars you had switched on) comes off your Mucka diary at once. You don't need to delete them one at a time.
- Leaves your Mucka jobs and appointments where they are. Anything you turned into a job stays, because it's a Mucka job now.
Mucka asks before it disconnects. The box Also remove all Mucka events from this calendar is ticked to start with. Leave it ticked and Mucka takes the jobs and appointments it put in your Google Calendar back out. Untick it and they stay in Google. Events you made in Google yourself are never touched.
Reconnect any time by going through the Connect flow again. Switching to a different Google account works the same way: disconnect, then connect the new one. The old account's events leave your diary and the new one's come in.
Common gotchas
- "This app isn't verified" warning from Google. Tap Advanced then Go to Mucka (unsafe). Mucka is verified with Google, but Google sometimes shows this warning for newer scopes. Safe to proceed.
- "Needs calendar permission" after connecting. On the Google screen there's a tick-box for "See, edit, share and permanently delete all the calendars". If it's left unticked, Mucka can sign you in but can't write jobs to your calendar, so nothing syncs. Tap Reconnect and make sure that box stays ticked.
- "That account has no Google Calendar." The Google account you signed in with isn't signed up for Calendar at all, so there's nothing for Mucka to sync into. Reconnecting the same account won't change it — connect one that has Calendar turned on.
- Deleted a job's event in Google? The job stays in Mucka — deleting it in Google only takes it off your calendar. Mucka stops updating that event, and the next time you change the job it goes back on your calendar as a fresh one. Delete the job in Mucka if you want it gone for good.
- Connected the wrong account. Disconnect and reconnect, Google will prompt you to pick again.
- Workspace admin blocks third-party apps. If you're on a managed Google Workspace, your admin might need to allow Mucka. Send them the help URL and they can whitelist the OAuth client.
- Token expired showing in the status. Tap Reconnect to refresh, takes 10 seconds.