# Connect JobLogic to Mucka Source: https://help.mucka.ai/integrations/connect-joblogic Category: Integrations Last updated: 2026-08-28 > Keep JobLogic as your system of record and mirror your customers, sites, jobs, engineers, visits and completed engineer forms into Mucka. If you run your business on JobLogic, Mucka can sit on top of it. JobLogic stays your source of truth, and Mucka mirrors your customers, sites, jobs and engineers across on a schedule so you get the Mucka AI layer without changing how your team works day to day. This is currently a pilot, so it may not be switched on for your workspace yet. If you use JobLogic and want in, just tell us. ## Before you start You need two things from JobLogic first: 1. **API credentials.** Ask JobLogic for API access. They send a **client ID** and a **client secret** (in two separate emails, for safety). 2. **An IP allowlist entry.** JobLogic only accepts calls from approved servers, so ask JobLogic to whitelist Mucka's server IP. We'll give you that IP when you start the pilot. Without it, the sync can't reach your account. ## Connect Head to [**Settings → Connections → Integrations**](/settings/connections/integrations) and open the **Field service** tab, then **JobLogic**. 1. Tap **Connect JobLogic** 2. Paste your **client ID** and **client secret** 3. Pick **Production** (or **UAT** if you're testing against a JobLogic sandbox) 4. Tap **Connect** Mucka checks the credentials, saves them securely, and starts a first sync in the background. Give it a few minutes, then refresh the panel to see how many customers, sites, jobs and engineers came across. ## What syncs, and how often - **Customers** become Mucka clients (residential or commercial) - **Sites** become Mucka properties, linked to the right customer - **Jobs** become Mucka jobs, with their status and type matched to yours - **Engineers** become assignable team members. Anyone who has left JobLogic comes across too, so their old work still has their name on it, but they can't be booked onto anything new - **Visits** — every trip to the job, not just the last one - **Completed forms** — the paperwork your engineers filled in on the job, like gas safety certificates and call slips - **Job notes** — the office's running notes on a job, read live from JobLogic when you open it - **Time booked off** — holidays, bank holidays, training days and anything else booked as non-productive time, which lands on the Mucka diary against the right person Mucka polls JobLogic every 15 minutes and pulls anything that changed. You can also tap **Sync now** for an immediate refresh. ## Jobs you went back to Plenty of jobs take more than one visit. JobLogic records each trip separately, and Mucka now keeps all of them. That matters when you ask Mucka what someone did on a particular day. If Tim went out on the 15th and again on the 17th to finish the job, asking "what did Tim do on the 15th" gives you that job, and Mucka tells you he went back on the 17th. Before, it only knew about the second trip, so the job looked like it belonged to the 17th and nothing else. It works the same way for "how did Tim get on today" — a job he returned to today shows up, even though it was first booked in weeks ago. On the job itself, look for **Visits from JobLogic**: each trip with the date, who went, how long they were there and whether it went ahead or was called off. Jobs done in a single visit don't show the section, because the date at the top of the page already tells you everything. ## Days off the tools Anything your team books in JobLogic with **Book Non-Productive Time** now comes across onto the Mucka diary. Holidays, bank holidays, training days, a jab, and the bits a lot of firms book that way — a doctor's appointment, a supplier meeting, an hour set aside to ring round about a job. Each one lands against the right person, with the reason you typed in JobLogic, and shows up in four places: - **On the schedule**, next to that engineer's jobs for the day - **When you ask what's on.** "What's on the diary tomorrow?" gives you the jobs **and** who isn't on the tools. You don't have to name anybody - **When you ask about one person.** "What was Tim doing on the 15th?" answers with the jobs and the time off together, so a day with no jobs doesn't come back as a day with nothing on it - **On the phone.** Mucka won't offer a customer an hour somebody has booked off If somebody is booked off **and** has a job in the same hours, Mucka tells you. That clash is usually worth a look before the day runs. A whole day booked off shows as all day. A block with times on it — "doctors appt 9am" — keeps its times. ### Changing it Time off that came from JobLogic is read-only in Mucka, the same as your customers, sites and jobs. Change it in JobLogic and it comes across on the next sync. If you try to edit or delete it in Mucka, Mucka will tell you where it lives instead of letting you make a change that would be undone at the next sync. How quickly that happens depends on how much there is to bring across. Mucka checks JobLogic every 15 minutes, but time off is refreshed at the end of a full pass over your data, so on a big account it can be a good while longer than the check itself. If something you have just booked is not showing yet, give it a bit rather than booking it twice. Appointments you book in Mucka yourself are unaffected — those are still yours to move or cancel from here. ## Reading the notes on a job JobLogic keeps two different things that both look like notes, and Mucka now shows you both. The **job description** at the top of the page is the brief the job was raised with — the fault, the case reference, the appliance. That has always been here. Underneath, **Notes from JobLogic** is the running commentary: the callback attempts, the authorisation from the insurer, "left voicemail to discuss". That's what you'd find under Info → Notes in JobLogic, newest first, with who wrote each one and when. You can ask Mucka for them too. "What are the notes on the Kingston Lane job?" reads them out — all of them, the way the office would if an engineer rang in and asked. Two things worth knowing: - Notes marked **private** in JobLogic show with an **Internal** label. Only people who can see all jobs get them; an engineer or subcontractor doesn't. - The section only appears on jobs that actually have notes. Most jobs don't, so you won't see an empty box everywhere. Notes aren't copied into Mucka — they're fetched from JobLogic the moment you open the job, so you're always reading the current version. That takes about a second on a job that has them. ## Finding the paperwork on a job Open any mirrored job and look for **Forms from JobLogic**. It lists what your engineer completed on that visit — the gas safety certificate, the call slip — with who filled it in and when. Tap one to open the PDF, exactly as JobLogic produced it, photos and signatures included. The section only appears on jobs that actually have paperwork against them, so you won't see an empty box on every job. Forms stay in JobLogic. Mucka fetches each one fresh when you open it, so you're always looking at the current document rather than an old copy. ## These records are read-only in Mucka Because JobLogic is the source of truth, anything mirrored from JobLogic is **read-only in Mucka**. You'll see a "Managed in JobLogic" note, and editing happens in JobLogic. Your next sync brings the change across. ## Matching statuses JobLogic's job statuses won't always line up with yours. Mucka matches them automatically by name, and you can fine-tune it: open the JobLogic panel and tap **Map statuses** to point each JobLogic status at the Mucka status you prefer. ## Disconnecting Tap **Disconnect JobLogic** to stop the sync. The records already mirrored into Mucka stay put. If you'd rather they became ordinary Mucka records you can edit, tick **Make the mirrored records editable in Mucka** when you disconnect.