Skip to content
  • There are no suggestions because the search field is empty.

How does the Jobber integration work?

Setup, custom fields, budget sources, and what's unique about Jobber.

Purpose

Jobber's integration with Protiv is one of the more flexible ones. You get to choose how budgets come in (custom field vs contract price percentage) and how time data formats. This article walks through it.

When To Use This

Use this when:

  • You're connecting Jobber to Protiv
  • You're trying to figure out which budget source to use
  • A worker's bonus calculation looks off and you suspect time format

Setup at a Glance

  1. Click Connect on Jobber in Settings → Integrations
  2. Authorize Protiv via Jobber OAuth
  3. Discover and map custom fields
  4. Choose your budget source
  5. Pick your time format
  6. Configure jobber-wages
  7. First sync runs

What Syncs From Jobber

Sync is automatic and on-demand.

Jobber-Specific: Custom Field Discovery

Jobber lets you create custom fields on jobs, clients, and properties. Protiv discovers them automatically.

Auto-mapping picks up obvious matches. Manual mapping fills the rest. Use this to bring custom data (e.g. a "Production Estimate" field) into Protiv as a budget value.

Jobber-Specific: Two Budget Sources

This is the big choice with Jobber.

Option A: Custom Field

Pull the budget from a Jobber custom field. Best when:

  • You already track labor budget in Jobber
  • The field has consistent values per job

Configuration:

  • Budget source: custom_field
  • Custom field: Pick which one
  • Budget field type: hours_budget or labor_budget

Option B: Contract Price Percentage

Calculate budget as % of contract price. Best when:

  • You don't have a labor budget field in Jobber
  • You bill flat-rate and labor is a known % of contract value

Configuration:

  • Budget source: contract_price_percentage
  • Labor budget %: e.g. 30%

Jobber-Specific: Three Time Formats

Jobber returns time data in different formats depending on the customer setup. Pick which one yours uses:

  • Hours — Decimal hours (e.g. 1.5 = 90 minutes)
  • Minutes — Total minutes (e.g. 90)
  • HH:MM — Time string (e.g. "1:30")

If your bonus calculations are way off, this is often the cause. Time being read as hours when it's actually minutes will undercount labor 60x.

Jobber-Specific: Wages Setup

Jobber doesn't track per-worker wages the same way as some other systems. Protiv has a custom jobber-wages signup step where you configure base wage and burden wage per worker.

Jobber-Specific: Visit-Based Budgets

Jobber visits are separate work events on a job. Protiv can sync visits as separate budget units, so a multi-visit job has visit-level ProPays.

This is enabled per-customer in setup. Most landscaping / maintenance customers benefit from it.

Common Mistakes & How To Fix Them

  • "Bonus calculations are 60x too small" Almost certainly time format mismatch. Hours read as minutes. Switch the format.

  • "Custom field budget didn't pull through" Verify the custom field exists on the job. Some Jobber custom fields are scoped to specific job types.

  • "My contract price percentage produces too-small bonuses" Tighten the labor budget %. If 30% is generating tiny bonuses, your actual labor probably runs higher than 30%.

  • Connecting Jobber to Protiv
  • How does the Aspire integration work, end to end?
  • What integrations does Protiv support?