Connect a field-service app

A trade division that keeps its own field-service app can point every job at the right project — without changing how that app works.

The operating system built exclusively for post-frame and barndominium builders.

Part of The Trade Network
What it is

For a builder whose in-house trade division runs Workiz, FieldPulse or another field-service app. The account creates an API key; the other app lists active projects and links its jobs back, and its webhooks link new jobs by the project number. Leads 2 Build can also keep a dropdown of active projects filled inside that app, so whoever books a job just picks the project. Linked jobs show on the project and on the trade they belong to.

Also called: workiz integration · fieldpulse integration · zapier · api key · project api · webhook · linked jobs · project dropdown

See it, piece by piece
01

A key that does one job

Try it

Create key makes an API key for the division's app. It is shown once to copy; only a fingerprint is stored. It can list your active projects and link jobs to them — it can't see money, contacts or anything else — and Revoke stops it at once. Links it already made stay.

Connect a field-service system — API keys

Connect a field-service system

For a trade division that runs its own app (Workiz, FieldPulse). Its jobs point at the right project here without changing how it works — and everything it does, Leads 2 Build can also do on its own (trade visits on each project).

1 · API keys
  • Demo field appl2b_live_3fT9…last used 10/9/2026
Create a key: it shows once, then only its first characters are listed. Real screen · sample data.
Without it

Connecting another app meant handing it a login that could see everything.

Why we built it

The other app gets exactly what it needs, and switching it off is one click.

Sound familiar?“our HVAC division uses Workiz and nothing connects to the builder side”
02

Their project dropdown stays filled

Try it

With the other app's own API key and the id of a dropdown field, Leads 2 Build pushes your active projects into that dropdown — on demand and every night. Labels read 26-BROOKS-001 · Brooks · site address, never change once used, and finished projects drop off. Whoever books a job just picks the house.

Connect a field-service system — the project dropdown

Connect a field-service system

For a trade division that runs its own app (Workiz, FieldPulse). Its jobs point at the right project here without changing how it works — and everything it does, Leads 2 Build can also do on its own (trade visits on each project).

2 · Keep their "L2B project" dropdown filled
WorkizConnectedOn

Pushed 7 active projects · Sat, Oct 10, 9:15 AM

FieldPulse
Workiz is connected and pushed 7 projects; set up FieldPulse with Save & push now. Real screen · sample data.
Without it

One wrong digit typed into the division's app and the job never found its house.

Why we built it

Picking from a list the builder keeps current beats typing a project number from memory.

Sound familiar?“I can't tell which field jobs belong to which house”
03

Jobs land on the house — and on the trade

Try it

A webhook from Workiz, FieldPulse or Zapier reads the job's project number and links it to that project, and to its trade when the job says which trade it is. Linked jobs on the project lists them — WZ-47930 and WZ-48211 on the HVAC trade, the perc test on septic — and + Link a job or Unlink fixes one by hand. The same jobs show inside each trade on barndominium trades.

Project window — Linked jobs
WorkizWZ-47930Load calc & equipment orderHVACDone
WorkizWZ-48211HVAC rough-inHVACScheduled
FieldPulseFP-10422Perc test & septic designSepticComplete

Jobs from the division's own app land here by the project number 26-BROOKS-001; a job that says its trade lands on that trade too.

Link a job by its number and trade, or unlink one. Real screen · sample data.
Without it

Nobody on the builder side could tell which field jobs belonged to which barndo.

Why we built it

The house's whole trade history is on the house, wherever the division booked it.

Sound familiar?“we're not ready to switch apps”
04

Everything it does works here too

Try it

The connection never makes the other app required. Each trade on a project carries its own visits — site visit, rough-in, trim-out, start-up, service call, inspection — with the day, who's going and a status, and each lands on the company calendar. A division can keep its app, or run its work orders here alone.

Trade — HVAC, Visits

Visits

  • Site visitTue, Oct 13, 2:00 PMNate O.Walk the shell with the framer — chase locations
  • Rough-inMon, Oct 26, 1:00 PMNate O., Bess K.Air handler in the mech closet
  • Trim-outMon, Nov 23, 1:00 PMBess K.
  • Start-upTue, Nov 24, 2:00 PMNate O.
Schedule a visit: pick the kind, a day, the people going, then Save visit. Real screen · sample data.
Without it

Connecting meant the division could never leave its old app.

Why we built it

Linking the app is a choice, not a dependency.

How it works
  1. 1Settings → Integrations → Connect a field-service system creates an API key. It is shown once; only a fingerprint is stored, and revoking it stops it at once.
  2. 2The other app reads the active-project list (number, name, client, site address, build mode and trades) and links a job, estimate, visit or invoice to a project by its id or project number.
  3. 3Webhooks from Workiz, FieldPulse or Zapier read the job's "L2B project" field and link the job to that project — and to its trade when the job says which trade it is. A job it can't place is acknowledged with the reason, and the raw payload is kept.
  4. 4With the app's own API key and a dropdown field id, Leads 2 Build pushes the active projects into that dropdown as "26-SMITH-042 · Smith · site" labels. A label never changes once used; finished projects drop off.
  5. 5Everything is also native: trade visits on each project do the job of the field app's work orders, so a division could run on Leads 2 Build alone.
Why we built it

A barndominium builder's in-house trade division often already runs its own field-service app, and both apps send invoices to the same QuickBooks. Replacing that app on day one isn't realistic, but its jobs have to land on the right project — today that's someone typing a name and hoping. A shared project number, a dropdown the builder keeps filled, and a webhook that links the job make the connection automatic, while the setup steps say plainly not to invoice the builder's own jobs there, because that would book a sale between two parts of the same company.

The problem
  • Field-service jobs had no reliable link to the builder's project.
  • Project lists in the other app were typed by hand and drifted.
  • Connecting meant replacing the division's app.
What you get
Jobs link themselves to the right project by its number.
The other app's project dropdown stays current on its own.
Keys are shown once, scoped to projects and links, and revocable.
A native path in Leads 2 Build for when the division is ready to switch.
INTEGRATIONS

See connect a field-service app
on one of your own jobs.

Thirty minutes with Keith — your building, your numbers. Bring the job where “our HVAC division uses Workiz and nothing connects to the builder side” — we will show you exactly where that stops.

Book 30 minutes with KeithSee every feature →
leads2build.com
Overhead doors on a finished building
Settings → Integrations — Connect a field-service system

Connect a field-service system

For a trade division that runs its own app (Workiz, FieldPulse). Its jobs point at the right project here without changing how it works — and everything it does, Leads 2 Build can also do on its own (trade visits on each project).

1 · API keys
  • Demo field appl2b_live_3fT9…last used 10/9/2026
2 · Keep their "L2B project" dropdown filled
WorkizConnectedOn

Pushed 7 active projects · Sat, Oct 10, 9:15 AM

FieldPulse
3 · Setup steps
  1. In Workiz: Feature Center → turn on the Developer API add-on (and Custom Fields).
  2. Settings → Integrations → Developer → create a v2 API key with Read & Write on Custom fields and Jobs.
  3. Settings → Custom fields → add a Job field "L2B project" of type Drop Down, limited to your builder job types. Copy its id (CF-…).
  4. Paste the key and the field id here and press Save & push now. L2B refreshes the options every night, so new projects appear and finished ones drop off by morning.
  5. Workiz → Automations → "Job created / updated" → Send webhook to the URL below, so the job links itself to the project.
Webhook URL (create a key above first)
https://app.leads2build.com/api/v1/webhooks/workiz?key=l2b_YOUR_KEY
Copy

Don't invoice the builder's own jobs in Workiz: it sends invoices to QuickBooks, which would book a sale between two parts of the same company. The agreed price lives on the project's Trades section instead.

Connect a field-service app — Leads2Build