JobTread’s AI Connector: what it can touch, and three checks before you trust a draft

If you’ve connected Claude or ChatGPT to JobTread, the assistant can do more than write. Depending on one setting, it can change things in your account too. Here’s what it can read, what it can change, and three checks to run before you trust a draft it writes for a client.

What the AI Connector is

The AI Connector is JobTread’s own link between your JobTread account and an AI assistant you already use, such as Claude or ChatGPT.[1][2] JobTread built and runs the connector, but the AI isn’t part of JobTread: you bring your own assistant. JobTread doesn’t charge extra for it.[3]

In practice, your assistant asks a question, the connector fetches the answer from your account and, depending on the access you granted, the assistant can also act on it.

What it can read

Reading is most of what it does. JobTread’s listing in the Claude directory names jobs and projects, estimates and budgets, schedules, customers and contacts, vendors and subcontractors, and documents and daily logs.[4]

There’s a catch worth knowing. It only sees what the person who connected it can see.[5] If that person’s role hides job costs, a budget-versus-actual report will be built without them, and the assistant won’t necessarily say so.

What it can change

That depends on the access level chosen when the connector is set up.[5] With write access, it can create and update records. JobTread’s own list of high-risk examples includes sending an estimate to a customer, marking an invoice as sent, moving a job to a new stage and recording a payment.[6] Each of those happens as you, under your name.

With delete access, it can remove records, and JobTread says it can’t restore data deleted through AI actions.[5] JobTread’s blog puts it plainly: “There is no built-in undo.”[1]

The one screen that decides it

When you connect, JobTread’s authorization page asks for two things.[5]

• A grant name. Whatever you type here appears in JobTread’s history log next to anything done through that connection.
• An access level: Read Only, Read and Write, or Read, Write and Delete.

That one screen decides what the assistant can touch. It deserves a moment’s thought.

Three quiet ways a report draft goes wrong

None of these are faults in JobTread. They follow from how any assistant works with live business data.

• The wrong job. Two clients share a surname, or two jobs share a street, and “write the Henderson update” finds the wrong one. JobTread warns that instructions are interpreted rather than guaranteed, and that vague prompts lead to incomplete or incorrect results.[1][6]
• A partial view. The report is drafted from a role that can’t see costs, so the numbers look complete and aren’t.[5]
• Acted on before anyone looked. With write access, “OK, send that to the client” is one sentence away from an estimate or email going out in your name.[6]

01Connect it Read Only

For reporting, Read Only is all it needs. The assistant can still read your jobs and draft the whole update. It just can’t send, change or delete anything.[5] You copy the draft, check it and send it yourself.

If someone needs write access for other work, give that its own connection with its own grant name. JobTread also suggests telling the assistant to confirm what it’s about to do before any high-risk action,[6] and Anthropic advises choosing “Allow always” only for tools you trust to run unsupervised.[7]

02Name the job, and ask what it read

Name the exact job in the prompt, the way JobTread’s own examples do (“the Riverside Remodel job”), and add the job number when two jobs or clients share a name.[6] Then ask the assistant to list the records it used and anything it couldn’t see, which follows JobTread’s own advice to ask the AI to list its assumptions.[2]

Before you read the rest of the draft, check the job number, client name and address at the top. Then check one figure, such as cost to date, against JobTread yourself.

03Check the history log

JobTread records what the AI does in its history log. You can show the “Created By Grant Name” field and filter on it, or save an “AI Actions” view that lists everything done through a connection.[5] Look there after any session on a connection that could change something.

Two habits from JobTread’s own guidance help here: export your data before asking the assistant to update or delete anything, and avoid asking it to act on many records at once.[5] If schedule dates could change, set a schedule baseline first so the original dates are kept.[8]

One limit to know: JobTread describes the log as covering actions, meaning what was created and changed.[3][5] We found nothing saying that reads are logged.

What it’s genuinely good for

Set up this way, the connector earns its place.

• Job summaries without copying and pasting between screens.[6][2]
• Client update drafts that a person checks and sends.[6][1]
• Finding what’s overdue across jobs: bids with no reply, invoices past due, jobs running close to budget.[6]

JobTread’s guidance is candid about the risks. It rates actions from low to high, offers a Read Only level and keeps a named trail of what the AI changed.[6][5] That’s a sound place to start. Final numbers, sending, and anything you can’t undo should stay with a person.

Where your data goes

Connector traffic passes through the AI provider you chose, under that provider’s data terms. Anthropic says raw content from connectors isn’t used to train its models on its consumer plans, though what you paste into the chat itself can be if model improvement is switched on.[9] For ChatGPT, it depends on your plan and your data controls.[10] JobTread’s terms and privacy policy don’t mention AI connector traffic.[11][12]

What we couldn’t confirm

• Whether the Read Only level is enforced on JobTread’s side for every operation. It’s documented, but we found no public test.
• Whether the ChatGPT setup offers the same three access levels. JobTread’s ChatGPT setup article sits behind a login.
• Whether reads, not just changes, show up anywhere an owner can see them.

Facts change. We checked every claim here against the sources below on 16 October 2026. If JobTread changes its access levels or log fields, this guide changes too.