Work snippet
HubSpot to Jobber: one deal per customer enquiry, with lead source kept
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Enquiries reach this home-services business from the website, paid ads and the phone, and the original Zaps opened a fresh HubSpot deal each time one touched the system. The rebuilt Zapier flow searches before it writes, so an enquiry stays one deal, the Jobber client and quote point back to it, and the owner can judge ad spend by paid jobs.
The problemEvery form, call and quote creates a new deal, so the pipeline looks twice as full.
What changesOne deal per enquiry, linked to Jobber, with the lead source kept.
- Area
- CRM to job system
- Tools
- HubSpot · Jobber · Zapier · Slack
- Typical scope
- US$400-900
- Timeline
- About 4 weeks · fixed milestones
The situation and what was breaking
One customer could leave three deals behind: a form, a call and a quote. Pipeline value read nearly double, and the source of the lead rarely sat on the deal that closed.
Five Zaps had been added over two years, one per form and one per quote event. None of them looked up an existing contact or deal first, so a customer who filled a form and then called had two deals, and a third appeared when the quote was sent from Jobber.
Lead source was set on the first deal and lost on the others, so won revenue could not be traced to the ads that produced it.
- 1.8 deals per genuine enquiry
- Lead source lost on the deal that was won
- Quotes in Jobber with no link to a deal
- Sales calling the same customer twice
- Ad spend decisions made without won revenue by source
What good looks likeOne deal per enquiry, and a report that shows which lead sources turn into paid jobs.
Discovery findings
What a read-only review checks first: six months of HubSpot deals and contacts, the Jobber requests and quotes, and the history of the five existing Zaps.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | No lookup before create in any Zap | 5 of 5 Zaps | Duplicates on every repeat contact |
| F2 | Deals per enquiry | 1.8 on average across 640 enquiries | Pipeline overstated |
| F3 | Lead source set only on create | 62% of won deals had no source | Ad decisions blind |
| F4 | Jobber quotes with no deal id | 118 quotes | Won and lost not visible in HubSpot |
| F5 | Phone enquiries entered by hand | No source captured | Phone leads undercounted |
| F6 | Zap errors emailed to an old address | 41 unread errors | Silent failures |
Architecture: HubSpot Jobber integration
Three Zaps replace five. Every one looks up before it creates, the deal id travels to Jobber, and errors go to a channel someone reads.
Scroll sideways to see the full drawing
The screens your team will use
Sales work the pipeline in HubSpot. The Zap steps are documented so the next change does not reintroduce duplicates.
Each card is one enquiry. The source shown is the one captured at first contact.
- Trigger: new form entryWebsite form, with UTM fieldsTrigger
- Find contact by email or phoneHubSpot search, create only if none
- Find open deal for contactOpen pipeline stages only
- PathsExisting deal or new dealPath A
Add note, keep sourcePath B
Create deal with source - Create Jobber requestDeal id in a custom field
- !On error: post to #opsZap name, step, record linkAlert
The same lookup steps are used in all three Zaps.
Won value by lead source
Only possible once source survives from first contact to the won deal.
How it is built
Turn the old Zaps off one at a time, each replaced and tested before the next.
- Module AInventory
The five old Zaps listed with trigger, actions, errors and what each was meant to do.
- Module BLookup pattern
Find contact, then find open deal, then create only if none; written once, reused in every Zap.
- Module CSource capture
UTM fields and a phone log form set source once; updates never overwrite it.
- Module DJobber link
Requests carry the HubSpot deal id; quote and job events write status back to the deal.
- Module EMerge backlog
Duplicate deals from six months merged, keeping the earliest source.
- Module FErrors and report
Errors to Slack with the owner, and a won-by-source report the owner can read.
Field mapping and rules
The lookup and the source rule are what stop the duplicates. Everything else is ordinary mapping.
| Source | HubSpot | Jobber | Rule |
|---|---|---|---|
| Form email / phone | Contact lookup keys | Client email / phone | Lookup before create |
| utm_source, utm_campaign | Original source, campaign | None | Written once |
| Service type | Deal name prefix | Request title | Fixed list |
| Deal id | Record id | Custom field: HubSpot deal | Required on every request |
| Quote total | Deal amount | Quote total | Jobber owns the amount |
| Job status | Deal stage | Job status | Status map |
| Jobber | HubSpot stage |
|---|---|
| Request | New |
| Quote sent | Quoted |
| Quote approved | Won |
| Quote archived | Lost |
| Job complete | Won, delivered |
Worked figures
Walkthrough arithmetic: six months of enquiries, before and after the rebuild and the merge.
Deals per enquiry
QA and testing checklist
Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.
- T1Repeat contactA second form from the same email adds a note, not a deal.
- T2Phone then formA phone log then a form keeps one deal and the phone source.
- T3Source keptAn update never changes the original source.
- T4Deal idEvery Jobber request created has the deal id.
- T5Write-backQuote approved moves the deal to Won.
- T6ErrorA forced HubSpot error posts to #ops with the step.
- T7Old Zaps offEach old Zap is off before its replacement goes live.
- T8MergeMerged deals keep the earliest source and all notes.
Scope
| Area | Included |
|---|---|
| Review | Six months of deals, quotes and Zap history, with findings |
| Zaps | Three Zaps with the lookup pattern, replacing five |
| Source capture | UTM fields and a phone log form |
| Jobber link | Deal id on requests, status written back |
| Merge | Duplicate deals merged, earliest source kept |
| Errors and report | Slack alerts and a won-by-source report |
| Not included | Ad account changes, website changes beyond hidden fields, or Zapier plan costs |
Milestones, week by week
- Week 1
Review and design
- Zap inventory
- Lookup pattern
- Status map
- Week 2
Rebuild
- Three Zaps on test records
- Old Zaps off one by one
- Week 3
Merge and link
- Backlog merged
- Jobber write-back
- Week 4
Report and handover
- Won by source
- SOP
- 14 days of fixes
Handover and keeping it running
Handover pack
- Zap map each Zap, its steps and why
- Lookup pattern note for anyone adding a new form
- Status map Jobber to HubSpot
- Recorded walkthrough pipeline, Zaps and report
- Ownership list Zapier, HubSpot and Jobber connections in the business's name
- 14 days of fixes for defects in the agreed scope
Keep it running
Duplicates come back when someone adds a new form with its own quick Zap. The note says every new entry point uses the lookup steps, and a weekly count of deals per enquiry shows it early.
- Weekly: deals per enquiry close to 1.0
- Weekly: #ops errors cleared
- Monthly: won by source reviewed before ad budgets
- Optional support hours at US$35 per hour, agreed in writing
Typical scope for this kind of project: US$400-900
About 4 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.