Run your JobTread jobs, customers, and address book from chat

Ask for a job by name and Foreman AI pulls the real record out of JobTread and works from it. Not a summary of a summary — the job's own details, its site address, the customer behind it, the people with access, the budget lines, the schedule, the documents, the daily logs, the comments, the files, and the plan sheets.

You can ask for the whole thing or just a slice. Asking for one slice is faster and cheaper, so if you only need the site address and the customer, say so.

Every list Foreman AI pulls back reports both how many rows exist and how many it fetched. That matters: a job with 69 budget lines used to come back as 10 with no warning that 59 were missing. If a list is truncated, Foreman AI will tell you rather than let you price off a partial budget.

A JobTread job does not point at a customer directly. It points at a location — a job site — and the location points at the customer. So a brand-new job needs two things before it can exist: a customer account and an address to build on.

Foreman AI handles that chain in one request. Tell it the customer name and the address and it creates the customer, creates the location under that customer, adds a primary contact if you gave it a name, and then creates the job on that location. If any step fails, the earlier steps are rolled back instead of leaving a half-built customer in your org.

Creating a customer in JobTread does not create an address by itself. That is why a customer added some other way may not be job-ready yet — ask Foreman AI to add the job site address to them first, then create the job.

At creation you can set the job name (JobTread caps it at 30 characters), number, description, areas, fixed-price or cost-plus, default retainage, specification text, custom field values, and a cover photo. You can also seed the new job from an existing one by copying its budget, its task list, or both.

Everything writable on a job can be changed by asking: name, number, description, areas, file folders, price type, retainage, specification description and footer, cover photo, and custom fields. Foreman AI reads the record back after every change and will not report success on a write that did not land.

Closing a job is a date, not a switch. Give Foreman AI the close date and the job closes as of that date; clear it to reopen the job.

Two things are worth knowing before you ask for them. A JobTread job has no status field of its own — job status is a custom field your organization defines, with its own fixed list of allowed values, and JobTread rejects anything off that list. Foreman AI reads the legal values back from your org, so ask it what the options are and it will tell you rather than guess.

A job also has no start or end date of its own. The dates you see on a job come from two tasks on its schedule — one nominated as the start milestone and one as the finish. To change a job's dates you change or re-point those tasks. See the JobTread Schedule & Tasks guide.

JobTread's address book holds two kinds of account: customers and vendors. Subs and suppliers are vendors, and Foreman AI can create them the same way it creates customers — with an address and a contact if you have one.

You can search the address book by name, filter to customers only or vendors only, include or exclude archived accounts, and read one account in full: its profile, its custom fields, and every contact, location, and job attached to it with real counts. Job sites are searchable on their own too, by name or by address, either within one account or across the whole organization — useful when you know the address but not the customer — and you can open a single site to see who owns it and every job that has run at that address.

Accounts can be renamed, archived and unarchived, pointed at a different primary contact or primary location, given statement descriptors, and updated on their custom fields. Locations can have their address, name, site contact, or tax rate changed. Giving Foreman AI a full street address is enough — JobTread parses it into street, city, state, and postal code.

One honest caveat on the taxable flag: in an organization whose default tax rate is zero, JobTread accepts a request to make an account taxable and then quietly stores it as not taxable. Foreman AI compares what it asked for against what actually stuck and reports any field JobTread ignored, instead of telling you a change was saved when it was not.

A contact is a person on a customer or vendor account — the homeowner, the office manager, the sub's foreman. Foreman AI can add one, set them as the account's primary contact, change their name or title, and remove them. Contacts can be listed for a single account or across your whole organization.

Separately, you can ask who is on a job. That answer covers everyone with access: their name, email, phone, role, whether they are internal staff, the customer, or a vendor, and whether they are visible to customer roles and vendor roles. Those two visibility switches are the ones that decide whether your customer sees a sub's name on the job, and Foreman AI can flip either one on request.

For your own team, Foreman AI can list the organization's people with their roles, admin flags, internal-or-external status, and when they were last active, and it can change a person's role, their internal flag, their hourly time-entry types and rates, and their Gusto or QuickBooks payroll ids. Those are real staff and payroll records, so say plainly what you want changed and for whom.

Adding a brand-new person to a job is not something Foreman AI does from the jobs side — it can adjust the access of someone who is already there. The one place a new person can be created is by assigning a task to an email address, and that is permanent; see the warning in the Schedule & Tasks guide before you do it.

Deletes in JobTread are permanent and Foreman AI treats them that way. It will not delete a job, an account, a contact, or a location on a vague instruction — it asks you to confirm first, tells you what the record still holds, and then reads the record back afterwards to prove it is actually gone.

Some deletes are refused outright until you clear the way. An account that still has jobs on it will not be deleted unless you explicitly say to force it, and a location will not be deleted while jobs still point at that address.

Writes never notify anyone behind your back. JobTread's own default is to email people when accounts change; Foreman AI turns that off on every write in this area, so nothing goes out to a customer because you renamed a record.

If something is not showing up, the first question is what your JobTread connection is actually allowed to see. Ask Foreman AI to identify the connection and it reports which JobTread user the key belongs to, which organization it resolved to, its role, and the actions it is permitted to perform.

You can also test a specific permission against a specific record — whether this connection may read a given job, see its internals or its specifications, read an account or a location, or create jobs at all. That turns "it says it can't find the job" into a definite answer.

And you can read the connected organization itself: its address and branding, its defaults for tax rate, retainage, and job folders, the roles it defines, how many accounts, jobs, locations, contacts, and people it has, and any parent or child organization connections.