Guide

Connect your CRM

Every lead your designer captures, and every job as it moves, can land in the system you already run: HubSpot, Pipedrive, Jobber, JobTread, GoHighLevel, Salesforce, Zoho, or a Google Sheet. The first two paths need no developer and take about twenty minutes. Every CourtBuildr step below is a picture of the exact screen, with lettered callouts on the controls; the other tool’s side is written out in order.

Where everything lives

Sign in to your dashboard and open Integrations in the left menu. Everything in this guide happens on that one page, apart from moving a job.

Tap to enlarge

Leads into HubSpot, Pipedrive, Jobber and friends (via Zapier or Make)

Zapier receives each lead the moment it happens and creates the contact, and if you like a deal, in your CRM. This needs Zapier’s Professional plan or higher: Webhooks by Zapier is a premium app, and the Filter and Formatter steps below are not on the Free plan either. Make’s Free plan includes custom webhooks and works the same way.

1. 1

   In Zapier: make the hook and copy its URL

   1. Zapier

   Create Zap.

   2. Trigger

   App Webhooks by Zapier, event Catch Hook, Continue.

   3. Copy

   The Test tab shows your webhook URL with a Copy button (it starts with hooks.zapier.com/hooks/catch/). Leave this tab open. Make: add a Custom webhook module, Create a webhook, copy its address.
2. 2

   In CourtBuildr: add it as an endpoint

   Integrations, then down to Webhooks. Paste the URL, type a label, tick lead.created, press Add endpoint.
   Tap to enlarge
3. 3

   Press Copy on the signing secret, then “I’ve saved it”

   It is shown once and I’ve saved it stays grey until you press Copy. Zapier, Make and GoHighLevel never ask for it, but keep it somewhere safe anyway: it is how a developer would prove a message came from us.
   Tap to enlarge
4. 4

   Press “Send sample lead”

   A realistic, clearly fake lead (Sample Customer, [email protected]) goes to Zapier right now, so it can learn the fields without you waiting for a real customer. Delivered (HTTP 200) means Zapier accepted it.
   Tap to enlarge
5. 5

   In Zapier: test the trigger, add the filter, then your CRM

   1. Test

   Back on the trigger’s Test tab press Test trigger, pick the newest request (Sample Customer), Continue with selected record. Zapier lists the fields as Data Name, Data Email, Data Phone… (its own name underneath is data__email; you never type that).

   2. Filter, right after the trigger

   Press + and add Filter by Zapier as step 2: Data Email → Exists, AND Test → Does not exist. When you test it Zapier says the sample “would not have continued”: correct, samples are meant to stop here; real leads carry no Test field.

   3. Your CRM

   Step 3: HubSpot Create or Update Contact (Pipedrive Find or Create Person, Jobber Find or Create Client, JobTread Create Customer, Salesforce Create Lead, Zoho CRM Create Module Entry with Module = Leads, Google Sheets Create Spreadsheet Row after typing the column headings in row 1).

   4. Map

   Email ← Data Email, First name ← Data First Name, Last name ← Data Last Name, Phone ← Data Phone. Create custom properties in your CRM first (Sport, Court size, Hoop, Design link), press Refresh fields in the Zapier step, then map Data Sport, Data Size, Data Hoop, Data Design Url to them.

   5. Optional: the money

   Step 4: Create Deal (HubSpot, Pipedrive) or Create Request (Jobber). Amount ← Data Estimated Value Amount, link it to the contact from step 3 (Associated contact / person), and put Data Design Url in the note.

   6. On

   Testing the CRM step really creates Sample Customer in your CRM: delete that contact afterwards. Then Publish. Done.
6. 6

   Check the Delivery log any time

   The last 40 messages we sent, with what their server answered. If Zapier is down we retry after 1 hour, 6 hours, 1 day and 3 days on our own.
   Tap to enlarge

What arrives, and where it goes

This is the sample, with the fields a CRM maps marked. The lead is under data. Zapier shows the fields as Data Email and so on; Make and GoHighLevel show them as data.email.

{
1  "id": "b3c1…",
2  "event": "lead.created",
  "created_at": "2026-09-15T01:12:09Z",
  "api_version": "2026-09-14",
3  "test": true,
  "data": {
4    "id": "aaaaaaaa-0000-4000-8000-000000000001",
    "name": "Sample Customer",
5    "first_name": "Sample",
5    "last_name": "Customer",
6    "email": "[email protected]",
6    "phone": "+1 555 010 0199",
7    "sport": "Basketball",
    "sport_key": "basketball",
7    "size": "26 × 31 ft",
    "width_m": 7.92,
    "length_m": 9.45,
7    "hoop": "72″ adjustable",
    "estimated_value": "$24,500",
    "estimated_value_cents": 2450000,
8    "estimated_value_amount": 24500,
8    "currency": "USD",
9    "design_url": "https://…/design?tenant=you&d=…",
    "ar_url": "https://…/ar?tenant=you&d=…",
10    "reason": "quote",
    "status": "new",
    "note": "",
    "created_at": "2026-09-15T01:12:09Z",
    "updated_at": "2026-09-15T01:12:09Z"
  }
}

Leads into GoHighLevel

GoHighLevel has its own Inbound Webhook trigger, so nothing sits in the middle. It is one of GHL’s premium workflow features: about a cent a run after the first hundred each month, so cost is not a concern. If you cannot find the trigger, whoever set up your GoHighLevel switches it on: Agency view → Settings → Company → Workflow Premium Features (and rebilling under Accounts → your sub-account). Your agency may run GHL under their own name and logo; the menus are the same, and the webhook URL always starts with services.leadconnectorhq.com.

1. 1

   In GoHighLevel: custom fields, then a workflow with an Inbound Webhook trigger

   1. Custom fields, once

   Settings → Custom Fields → Add Field, object Contact: Sport, Court size, Hoop, Design link as Single line. Two minutes.

   2. Workflow

   Automation → Workflows → Create workflow → Start from scratch.

   3. Trigger

   Add New Trigger → Inbound Webhook. Copy the URL it gives you. Leave the trigger panel open.
2. 2

   In CourtBuildr: add the URL as an endpoint

   Then press Copy on the signing secret (I’ve saved it stays grey until you do), keep it somewhere safe, and press I’ve saved it. GoHighLevel never asks for it.
   Tap to enlarge
3. 3

   Press “Send sample lead”

   A realistic fake lead (Sample Customer) goes to GHL right now.
   Tap to enlarge
4. 4

   In GoHighLevel: pick the sample as the Mapping Reference

   1. Trigger panel

   Press Test Trigger (some accounts say Fetch sample requests). Under Mapping Reference pick the request at the top of the list: it is the sample you just sent. Press Save Trigger. GHL then drops a Create Update Contact action under the trigger on its own: delete it, the If/Else below goes first.

   2. How mapping works

   In any action, press the tag icon inside a field and pick the webhook field. GHL inserts a token such as {{inboundWebhookRequest.data.email}}. Every field of the sample is under inboundWebhookRequest.data.
5. 5

   In GoHighLevel: the guard, the contact, the opportunity, publish

   1. Guard

   If/Else first, testing the webhook values (there is no contact yet). Its left side is a field picker, not a typed token: open the Inbound Webhook group and pick data.email → Is not empty; add a segment (AND) test → Is empty. Real leads carry no test field; only samples do. Everything below goes on the Yes branch.

   2. Create Contact

   Create Contact (older accounts: Create Update Contact; it updates a contact with the same email rather than duplicating). First name …data.first_name, last name …data.last_name, email …data.email, phone …data.phone, and your custom fields from …data.sport, …data.size, …data.hoop, …data.design_url. Then Add Contact Tag: court-designer.

   3. Opportunity

   Create/Update Opportunity (or Create Opportunity): your pipeline’s first stage, lead value {{inboundWebhookRequest.data.estimated_value_amount}} (a plain number, no maths needed), name …data.sport court.

   4. Publish

   Save each action, then flip the toggle top right from Draft to Publish: in Draft the URL accepts messages but nothing runs. Your existing follow-up (SMS, missed-call text back, email) takes it from there.

Keep your CRM in step as jobs progress

A job is a court you are building for a customer. Each stage you move it to lands on the customer’s own page and emails them; the same moment, your CRM can hear about it too. Open the Jobs tab once before you start (that is what creates your pipeline), and if you are on the supply-only pipeline pick it under the ⚙ Portal button on the Jobs tab first.

1. 1

   Make a second hook, and add it as a second endpoint

   A Catch Hook URL belongs to one Zap, so make a second Zap (Webhooks by Zapier, Catch Hook, exactly as before) and paste its new URL here; in GoHighLevel, a second workflow with its own Inbound Webhook. Tick job.created and job.stage_changed. (job.updated is notes and photos, job.message.created is the customer writing to you, job.document.added is a quote or plan you attached.)
   Tap to enlarge
2. 2

   Press “Sample stage change”

   Your tool learns the job shape before any real job moves. Samples carry test: true here too, so filter it out the same way. GoHighLevel: back in the second workflow’s trigger panel, Test Trigger, pick this request as the Mapping Reference, Save Trigger, exactly as in the leads workflow.
   Tap to enlarge
3. 3

   Now a real one: Jobs, open the job
   Tap to enlarge
4. 4

   Pick the new stage, write the note, Move stage & post

   The customer gets the email and their page updates, and job.stage_changed goes to your endpoint the same moment. Nothing shows in your CRM yet: the Zap or workflow that turns it into a deal update comes next, and this real move is the record you will test it with.
   Tap to enlarge
5. 5

   Map the stages to your pipeline, once

   1. Zapier: the shape

   In the second Zap: Filter (Test → Does not exist), then Paths by Zapier on Data Event: one path for job.created, one for job.stage_changed.

   2. Zapier: job.created path

   Find Contact by Data Job Customer Email, then Create Deal associated to it, with a “Job number” deal property ← Data Job Number (create that property once: HubSpot Settings → Objects → Deals → Manage deal properties).

   3. Zapier: job.stage_changed path

   Formatter → Utilities → Lookup Table: key Data Job Stage Key, one row per stage from the table below, value = your CRM’s stage id (HubSpot: Settings → Objects → Deals → Pipelines, the </> icon beside each stage; Pipedrive: Settings → Pipelines, the number in the URL). Then Find Deal by Job number ← Data Job Number, and Update Deal with Deal Stage set to Custom ← the Lookup output. Jobber has no stages: Find or Create Client then Add Tags to Client ← Data Job Stage Label.

   4. Zapier: test and publish

   Test trigger → pick the real move from step 4 (not Sample Customer) → test each step → Publish.

   5. Make

   A Router on event, then on data.job.stage.key, one route per stage, each updating the deal.

   6. GoHighLevel

   In the second workflow: Find Contact by email {{inboundWebhookRequest.data.job.customer.email}} → on its Contact Found branch, Find Opportunity (your pipeline, latest) → on its found branch, If/Else on {{inboundWebhookRequest.data.job.stage.key}}, one branch per stage, each an Update Opportunity to the matching pipeline stage. Without Find Opportunity the update has nothing to act on and is skipped. Then Draft → Publish.

   Your stage keys

   Construction pipeline (the default)
   Job confirmed	received
   Design locked in	design_locked
   Scheduled	scheduled
   Site prep	site_prep
   Base / slab	base
   Base curing	curing
   Surface install	surface
   Line marking	lines
   Hoops, fencing & extras	fit_out
   Handover	handover
   Canceled	cancelled

   Supply-only pipeline
   Order confirmed	received
   Design locked in	design_locked
   In production	in_production
   Ready to dispatch	ready
   Dispatched	shipped
   Delivered	delivered
   Complete	complete
   Canceled	cancelled

What a stage change looks like (the sample, as “Sample stage change” sends it)

{
1  "event": "job.stage_changed",
2  "test": true,
  "data": {
    "job": {
3      "number": "SMP-TEST1",
3      "external_ref": "CRM-12345",
      "stage": {
4        "key": "site_prep",
        "label": "Site prep",
        "customer_label": "Site prep under way"
      },
      "customer": {
        "name": "Sample Customer",
5        "email": "[email protected]",
        "phone": "+1 555 010 0199"
      },
      "price": {
6        "amount_cents": 2450000,
        "paid_cents": 1225000,
        "currency": "USD"
      },
      "key_dates": {
        "start": "2026-10-01",
        "install": "2026-10-15",
        "handover": "2026-10-24"
      },
7      "portal_url": "https://…/portal/jobs/…",
      …
    },
4    "previous_stage": "scheduled",
    "update": {
8      "note": "Slab poured this morning, curing for a week.",
      "photo_count": 2
    }
  }
}

Give a developer access

If you have someone technical, or a CRM that can call APIs itself, they get an API key and the reference at /developers. With it they can create and move jobs from your CRM, pull leads on a schedule, and verify every message’s signature.

1. 1

   Integrations → API keys → name it → Create key

   Name it after the system that will use it, so you know what to revoke later.
   Tap to enlarge
2. 2

   Press Copy on the key, then “I’ve saved it”

   It is shown once. Paste it into a password manager or straight into the other system. I’ve saved it stays grey until you press Copy.
   Tap to enlarge
3. 3

   It appears in the list; revoke it if it ever leaks

   Up to five keys at a time. “Last used” tells you whether the integration is alive.
   Tap to enlarge
4. 4

   Send them to the docs

   courtbuildr.com/developers has every endpoint and the exact JSON; courtbuildr.com/api/v1/openapi.json imports into Postman or a code generator.
   Tap to enlarge

If something is off