Case study · Automation

Appointments that create their own JobNimbus tasks.

Sales ran in GoHighLevel, production in JobNimbus. Every confirmed estimate meant someone retyping it as a task. I closed that gap.

ClientTX Gutter Expert
My roleScoped, built & tested
StackGHL · Zapier · JobNimbus
ShippedNovember 2026

The flow

  1. 01 GHL Appointment confirmed An estimate appointment is confirmed in GoHighLevel.
  2. 02 GHL Workflow fires webhook Sends the contact, job number and sales agent.
  3. 03 Zapier Find the job Looks up the JobNimbus job by its job number.
  4. 04 Zapier Pick the owner Routes the task by the lead’s sales agent.
  5. 05 JobNimbus Task created Lands on the right job with the appointment details.

The problem

Estimate appointments were booked and confirmed in GoHighLevel, but production lived in JobNimbus. Tasks were created by hand, or not at all, and the field team didn't always know an estimate was coming.

Decisions

I weighed a GHL "Note added" trigger but kept the original design: the appointment-confirmed workflow sends a webhook to Zapier. It fires at the right moment and is easier for the team to reason about. Tasks go to the lead's sales agent when they own that stage, otherwise to the default operations owner.

Constraints I designed around

  • The job number arrives lateIt reaches GHL about 15 minutes after a lead comes in, so it may not exist when an appointment is confirmed.
  • Reschedules are messyLeft out of version one on purpose, to ship something reliable for estimates first.
  • Repeat customers mean new jobsA new booking becomes its own job, so the match is by job number, not by contact.

What's next

A historical Job ID backfill now links older JobNimbus jobs to their GHL contacts, which opens the door to handling reschedules and more appointment types.

See more systems
WhatsApp me