JobsiteOn

Connect an AI Assistant to JobsiteOn

Connect your workspace, review proposed changes, and check the result.

Ethan Rivera
Written by Ethan RiveraUpdated yesterday17 min readBeginner

Open Settings, AI connections to see all six options. Claude’s setup is open when you arrive. Choose ChatGPT, Gemini, Grok or Perplexity to see its steps and open its connector settings. Choose Other MCP clients for Claude Code or VS Code.

Use the arrows to move through setup at your own pace, or press Play. Open Setup guide for the written steps. For custom connectors, use Copy beside Connector address. If your workspace is outside the pilot, the page explains how to request access.

Your assistant receives the fields needed to prepare a change. You'll still review the proposed values in JobsiteOn before anything is saved.

What's included

Connecting Claude is included with Starter, Team, Business and Enterprise, and during an active free trial. Reading workspace records through the connection doesn't use JobsiteOn AI credits. Your Claude account has its own limits and charges. Creating a job or sending a text still uses the normal JobsiteOn allowance or credit charge. Approval shows the applicable usage before you act.

Your JobsiteOn role and plan still control what you can use. Starter includes basic calendar access; dispatch and reports require the corresponding plan features. A trial must still be active. An owner or admin can turn connections or specific permissions off for the workspace.

Connect Claude to your workspace

  1. Open Settings, AI connections and choose Claude. Select Open Claude directory, then Connect on the JobsiteOn listing.
  2. To use a custom connector, open Custom connector setup. In Claude, choose Customize, Connectors, then Add custom connector. Name it JobsiteOn and paste the address. Use Claude's published identity when offered. If a client ID is required, copy it from JobsiteOn or ask your administrator. Leave the client secret blank.
  3. Sign in to JobsiteOn in your own browser session. The page shows the assistant's logo next to JobsiteOn's and nothing else from JobsiteOn's menus. The workspace you're working in is already chosen; pick another if you want. Only live workspaces are listed: assistants never connect to sandbox data. Under Requested permissions, each area (customers, buildings and contacts; jobs; visits and the schedule; and so on) is one row that says what Claude can read there and how many changes need your approval. Open a row to see every line, such as "Archive a contact" or "Email an invoice", or choose Show all details. Every area is listed; anything your role or your workspace's plan doesn't include is marked Not included, with the reason. Allow connection and Cancel stay at the bottom of the screen while you read.
  4. Enable the connection in your Claude conversation. Start by asking which workspace is connected.

For a question like “How much do customers owe on overdue invoices?”, the assistant can use List invoices and answer in chat. All JobsiteOn AI connectors read workspace records directly from JobsiteOn. Record links in an answer are there for you to open. If a lookup is unavailable, the connector directs the assistant to explain the limit in chat.

If Claude asks to open JobsiteOn in Chrome, choose Decline and ask it to use the JobsiteOn connector. You can also turn off Claude in Chrome for that conversation and keep JobsiteOn enabled.

Claude may separately ask to use List invoices. Choose Always allow if you want Claude to remember that choice and your workspace allows it.

The connection stays active between chats until you disconnect it, which you can do under Your connections. Open Connection details for the permissions and connection date. Choose Refresh to check a new connection.

A Claude Team or Enterprise administrator may need to allow the connector first. Each person connects with their own JobsiteOn account. Claude's supported plans and setup screens can change; check its custom connector guide.

Review a proposed change

Claude can look up permitted records and prepare a change. It cannot approve that change for you. Open the review link, check the workspace, records, dates, amounts and recipients, then approve or reject it. A preview expires after ten minutes. If a record, price or permission changes, ask for a fresh preview. A change belongs to the live workspace you connected. If you open the review link while JobsiteOn is in your sandbox, the page says so and offers Switch to live workspace, which switches and reopens the review. A connection made to a sandbox workspace before November 7, 2026 no longer works. It shows Reconnect needed in Settings, AI connections. Disconnect that connection, then reconnect from your assistant and choose your live workspace.

Available changes include customers, buildings, contacts, pending jobs, job details such as priority and job type, internal job notes, tasks, visit times and assignments, quote and invoice drafts, messages, and service requests (create, update, archive and restore), plus archiving a proposal or voiding an invoice (owners and admins; an invoice with a recorded payment can't be voided), emailing a proposal or invoice to the job's customer, marking a proposal accepted or declined when the customer told you by phone or in person, and recording a payment you already received, such as cash or a check (owners and admins). Claude can also schedule a new visit on an open job, assign one crew to several visits in a single approval, cancel a visit (it stays on the job as cancelled), mark a job completed, and archive or restore a completed or cancelled job (owners and admins). Completing a job does what Complete does in JobsiteOn, including scheduling the customer's review request under your review settings; the approval page says what will happen. Like Add visit in JobsiteOn, scheduling a visit marks the job's open proposals accepted and expired ones expired; the approval page lists each one. Visit reviews show the people currently assigned and the proposed crew. An unassigned visit shows None. If a current crew member's name changes before approval, ask Claude for a fresh preview. Visits with more than 100 assigned people must be changed directly in JobsiteOn. Owners and admins can also have Claude add a price book item, change its name, SKU, unit, price, cost or taxable setting, and archive or restore it; a connected accounting app gets the change, as it does for changes made in JobsiteOn. With Dispatch, owners and admins can have Claude add equipment, change its name, category, serial number, notes or warranty, and archive or restore it. Archiving works like Delete on the asset: it leaves your active list, keeps its job and service history, and can be restored. With Capture, owners and admins can have Claude move a Capture photo onto a job, so it shows on the job's Photos tab; the job needs a Capture project first. Owners and admins can create, rename, archive and restore job types and customer types. Archiving makes a type inactive; it keeps existing records and price rules. A type used by a proposal cannot be archived. Descriptions stay out of assistant reads. Each change needs approval in JobsiteOn.

You can ask your assistant to add or update a building's site contacts, including their names, phone numbers, email and site role. It can mark a contact inactive and make it active again. Choosing a new primary coordination contact replaces the previous primary; the approval page shows who will be replaced. Private notes stay out of assistant reads. These changes do not delete contacts or edit email routing rules.

You can also create a contact follow-up task, change its text or due date, mark it complete, and reopen it. New follow-ups are assigned to you. Claude can list their completion state and dates; task text stays in JobsiteOn. Restore an inactive contact before changing its follow-ups. Permanent task deletion stays outside the connector.

You can create a checklist item inside a task, change its title or position, mark it complete, and reopen it. Claude can read the item's completion and position; its title stays in JobsiteOn. You must have access to the parent task and its linked record. Restore an archived task before changing its checklist. Each change needs your approval.

Job checklists are also supported. Create an item, change its title or details, assign an active teammate, choose a visit on that job, set a due date, or mark it complete and reopen it. Claude reads the status, dates and assignments; titles and descriptions stay in JobsiteOn. Restore an archived job first. Review each proposed change in JobsiteOn before it is saved. Checklist items cannot be permanently deleted through the connector.

Claude can read and set tags on contacts, customers, buildings and jobs. Give the complete list you want to keep, up to 50 tags of 100 characters each. Replacing the list removes tags you leave out. Clearing it shows None on the approval screen before you approve the change.

Claude can also archive or restore a contact, a customer or a building. Record details show the current status. Contacts listed under a customer also show their status, so an inactive contact is not mistaken for an active one. Archiving a contact or customer marks it Inactive, the same as changing its status in JobsiteOn; a customer with open jobs or unpaid invoices can't be archived, and archiving a customer leaves its contacts and buildings as they are. Archiving a building works like Archive on the building: its open jobs stay open. Restoring makes any of them Active again. Claude can also archive a task: it leaves every task list in JobsiteOn and stays linked to its record, and restoring it brings it back. An archived task that is still open keeps its building from being deleted until it is restored and closed. To close a task, Claude marks it done. Phone numbers Claude adds are saved in full international form; outside the US and Canada, give Claude the country code. Owners and admins can have Claude change an open proposal's title, description or valid-until date, the same as editing it in JobsiteOn; its lines and amounts stay as they are and nothing is sent. Proposal and invoice drafts can also carry the terms your customer reads. The approval page shows the proposal's valid-until date or the invoice's due date as a calendar day. Updating draft lines without changing that date keeps the existing date. An archived proposal or a voided invoice can't be restored, in JobsiteOn or through Claude. With Dispatch, owners and admins can have Claude add a vehicle, change its name, plate, VIN, condition, tracking or driver, and archive or restore it; like equipment, an archived vehicle keeps its job history.

Links to archived requests, equipment and vehicles still open their details. The page shows Archived alongside the record's last status. Restore the record before editing it or taking another action. Archived requests leave the active inbox list and its count. Service agreements include a start time, like the form in JobsiteOn. New drafts start at 09:00 unless you choose another time. Changing only the date keeps the existing start time. Claude shows the next booked visit even when all visits have already been scheduled.

Anyone but a viewer can have Claude create a service agreement as a draft, change its title, contact, description, visit length, and with finance access its visit price and invoicing (the repeat rule only while it's a draft), and start, pause, resume or cancel it, the same as the buttons on the agreement. Starting one schedules its visits as jobs, and the approval page says how many; pausing withdraws visits more than a week out, and cancelling withdraws visits after today and can't be undone. Claude can't create a second building at an address you already have. To change a building's address, edit it in JobsiteOn so its map pin and open jobs move with it. Nothing is ever deleted through the connection; an archived request, contact, customer or building can be restored. Saving a quote or invoice draft does not issue it, take payment or send it to a customer. Saving a message draft sends nothing. Sending requires a separate approval that shows the sender, recipient and message. Approving a proposal or invoice email sends it once, the same as pressing Send in JobsiteOn, to the customer email shown on the approval page, with no automatic BCC copy, text message or automatic follow-ups. Your usual BCC preference still applies when you send directly in JobsiteOn. If the proposal or invoice changed after approval, nothing is sent and Claude has to prepare it again. Recording a payment works like Mark paid: it never charges anyone, can't be more than the balance due, and the approval page shows the balance before and after.

Check the result

Recent actions appear in Settings, AI connections. Open an action to see its result. A saved record can have background updates still processing. If those updates fail, Retry background updates retries them without creating the record again.

Request links open the selected request in Inbox, Requests. Task links open the task in the task list. Field reports in a building's history link to that building and say View building.

While a message is waiting, Cancel before sending works until delivery starts. If delivery is unconfirmed, don't send another copy. Contact support with the operation ID shown on the page. An uncertain result does not mean the message failed to reach the recipient. Proposal and invoice emails stay unconfirmed until support can check that particular send. Another email in the document's Activity does not confirm it.

What Claude can read

Ask about a building by its address or name, for example "888 S Figueroa". If more than one building matches, Claude asks you which one you mean. Once you pick one, its jobs, quotes, invoices, reports and requests stay limited to that building, so 888 and 660 S Figueroa never mix. Claude can also look up customers with their billing address and payment terms, contacts, and each building's site contacts such as the property manager or chief engineer. Archived contacts, customers and buildings come up when you ask for them. With Dispatch, Claude can search your equipment and vehicles and see each one's jobs and, for equipment, its service dates. Claude can list service agreements with their repeat rule, next visit and recent visits. Owners and admins with Capture can list Capture photos for a job or your Unfiled photos, with when and where each was taken.

The connection returns selected operational fields, not every field on a record. Free-text notes, such as gate codes, parking instructions, job notes, customer notes, equipment and vehicle notes, service agreement descriptions and photo captions, aren't shared with Claude. A vehicle's location isn't shared. Claude tells you when a record has them so you can open it in JobsiteOn. Restricted imported records are excluded. Contacts and price-book items created through an approved assistant change can remain available after JobsiteOn exports them to QuickBooks. If a connected provider later changes their business fields, the source restriction applies. Disconnecting that provider doesn't remove the restriction. Older linked records with unknown origin remain excluded. Eligible price-book items can also be used on draft proposals and invoices. The same source checks apply when you review and approve those drafts. Invoices drafted through an approved assistant change can also remain available after JobsiteOn sends them to QuickBooks, so Claude can still read or void them. If a QuickBooks payment is recorded on one, the source restriction applies to that invoice. Jobs created through an approved assistant change can also remain available after export to a connected calendar. If a provider moves the job or its visit, the source restriction applies to that job and its linked records. An unchanged calendar response leaves access as it was. Disconnecting the calendar does not remove a restriction from a provider change. File text is limited to eligible plain-text files uploaded directly to JobsiteOn. Images, PDFs, imported attachments and files with unknown origin are not read through this connection. An unavailable record can therefore still exist in JobsiteOn. You can ask for an eligible text file by the name shown on its contact, property, job or quote.

Reading your email

With the Read your email permission, Claude can list and read the email conversations you can open in the JobsiteOn inbox: your own mailbox, shared or team mailboxes you have access to, and mail synced from your connected Gmail or Outlook. A teammate's personal mailbox is never included. Claude sees sender, recipients, subject, the date and the message text (at most 8,000 characters per message, the 20 most recent messages of a conversation) and the names and sizes of attachments, not the attachments themselves. Reading through Claude doesn't mark anything as read. Only live workspaces are connected.

Email is written by other people. Claude is told to treat it as information and never to follow instructions found in an email, but check anything an email asks for before you act on it.

To stop Claude reading your email, disconnect it in Settings, AI connections. An owner or admin can turn Read email off for the whole workspace on the same page: existing connections stop working at once, and people who reconnect get every other permission but not email.

Availability includes native visits and calendar busy times without private event descriptions. Check Dispatch for external calendars and recurring events that are not yet represented as individual occurrences.

Disconnecting stops future access. It cannot remove information already in a Claude conversation. Manage that conversation in Claude as well.

Disconnect or change permissions

Open Settings, AI connections and disconnect the connection. An owner or admin can also open Workspace permissions there. Changes to those permissions require people to reconnect. Leaving a workspace, losing access or reaching the end of a trial also stops new connector access.

A connection marked Paused belongs to an assistant JobsiteOn has switched off for now. It stops working until that assistant is switched back on, and you can still disconnect it.

If an older approval tab cannot load

JobsiteOn uses https://api.jobsiteon.com for assistant authorization. An assistant that saved the older authorization address is taken to the current address before JobsiteOn asks you to approve access.

If an approval tab opened before this change says the request couldn't be completed, close that tab and start Connect again in your assistant. A revoked connection still needs a new approval.

If the approval page says the request expired

An approval link works for 10 minutes, in the browser that opened it. If the page says This connection request expired. Start again in your assistant., close it and choose Connect again in your assistant. Nothing is connected until you choose Allow connection.

If ChatGPT cannot reconnect

Start Connect from the current JobsiteOn entry in ChatGPT. Each attempt creates a new approval link, so close older approval tabs instead of reopening them. If the error says invalid_client, contact support with the plugin link and error text. Keep passwords, client secrets and sign-in codes out of that message.

Connect Gemini with the JobsiteOn address

In Gemini Connectors, choose Create custom app and enter https://api.jobsiteon.com/mcp. Leave Additional settings empty. Choose Next, review Google's notice and follow the account-linking prompt. Sign in to JobsiteOn, select your live workspace, review permissions and choose Allow connection. Back in Gemini, choose Connect to save the app.

Google offers custom apps to eligible personal accounts. Check its custom app guide for current requirements.

If Gemini asks for a client ID and secret

Use the OAuth credentials issued for the exact redirect URI shown in Gemini's connection dialog. Enter them directly in that dialog, then approve the live JobsiteOn workspace. Keep the secret out of chat messages. An unused registration expires after two hours; request fresh credentials if needed.

If Gemini reports invalid_redirect_uri, the callback does not match that client registration. Start a new connection with only the MCP server URL to let Gemini register its current callback. If manual credentials are required, request credentials for the exact callback Gemini shows.

Grok connects with its reviewed public identity. It can discover that identity through registration while Gemini registration is enabled. Every workspace connection still needs your approval in JobsiteOn.

Did this answer your question?

Related Articles