Skip to main content

​
What does the Jobber integration do?

Hatch offers a native integration with Jobber that you can activate within the App Marketplace (located in your Hatch workspace). This integration syncs contact data from Jobber to Hatch, and can also sync Hatch events to Jobber. While active, the Jobber integration will sync new and updated Jobber data every 15 minutes. It will also sync Hatch events back to Jobber as soon as they occur (if you have enabled this feature). To get started, open the App Marketplace in your Hatch workspace and follow the setup instructions below.

​
How do you set up the integration?

​
Requirements

You will need the following to set up the integration:
  • Hatch account with manager privileges
  • Jobber account

​
Setup Steps

The following is the set of steps required to activate the integration:
  1. In Hatch, open the App Marketplace.
  2. Under the CRMs tab, click the Jobber Connect button.
  3. In the window that appears, click the Start Setup button.
  4. Follow the steps of the setup, clicking the Next button after each screen is completed.
    1. The setup will open a new browser tab to connect your Jobber account. You will need to approve the connection in this new tab.
  5. In the final screen of the setup, click the Finish button.

​
When does Hatch sync data to/from Jobber?

​
Jobber→ Hatch

Jobber data can be sync’d to Hatch in the following scenarios. These options are configured during the integration setup.
Keep in mind that syncs occur every 15 minutes.
  • If a work request record is created or updated in Jobber, Hatch syncs the work request record along with any associated data (see below for specific fields)
  • If a quote record is created or updated in Jobber, Hatch syncs the quote record along with any associated data (see below for specific fields)

​
Hatch → Jobber

Hatch events and/or communications can be sync’d to Jobber in the following scenarios. These options are configured during the integration setup. If enabled, Hatch will log the communications in the Notes & Attachments of the associated Jobber Work Request, Quote, or Client record (with options to link to additional objects).
Keep in mind that push communications occur instantaneously. There must be a Jobber record in Hatch at the time of the communication event in order for it to succeed.
  • When a Hatch campaign sends a text/email/voicemail to a contact,
  • When a contact calls or sends a text/email/voicemail to a Hatch workspace
  • When a Hatch user calls or sends a text/email to a contact
  • When events occur within a Hatch campaign
    • A contact is launched (added) to a Hatch campaign
    • A contact is sent the first message of a Hatch campaign
    • A contact is removed from a Hatch campaign before it has ended
    • A contact completed a Hatch campaign

​
How is Jobber data stored in Hatch?

​
Opportunity Models

There are two types of Hatch opportunities that the Jobber integration creates:
  • Work Request Opportunity — Created from Jobber Work Request**** records. Additional related data is also included (see below).
  • Quote Opportunity — These opportunities are created from Jobber Quote records. Additional related data is also included (see below).

​
Opportunity Creation & Update

When an opportunity is generated that doesn’t match an existing contact , a new contact will be created. A new opportunity will be added to an existing contact if a match is found.
The integration will replace an existing Hatch opportunity when:
  • The sync’d Hatch External ID matches the existing opportunity’s Hatch External ID (see below for how the External ID is mapped)
The integration will create an additional (new) Hatch opportunity when:
  • The sync’d Hatch External ID does not match the existing opportunity’s Hatch External ID (see below for how the External ID is mapped)

​
What Jobber data is available in Hatch?

​
Detail Field Lists

Some fields below are lists. Data within a list field is sorted by “created date” in descending order. For example, a list of jobs would have the most recently-created job listed first.
When accessing a list, you need to provide the index number of the list item that you want. Because this index number will vary, it is shown in the lists below with the placeholder #.
The following fields are available in the opportunity details: Quote Opportunity
FieldType
approved_atDate
clientObject
client:balanceNumber
client:billing_addressObject
client:billing_address:cityString
client:billing_address:countryString
client:billing_address:pcString
client:billing_address:provinceString
client:billing_address:streetString
client:billing_address:street1String
client:billing_address:street2String
client:company_nameString
client:created_atDate
client:custom_field_valuesObject
client:custom_field_values:<custom_field_name>List OR String
client:custom_field_values:<custom_field_name>:<n>String
client:emailsList
client:emails:#Object
client:emails:#:addressString
client:emails:#:descriptionString
client:emails:#:idString
client:emails:#:primaryIndex 1: Boolean
Index >1: String (Boolean)
client:first_nameString
client:idString
client:is_companyBoolean
client:is_achievedBoolean
client:last_nameString
client:nameString
client:phonesObject
client:phones:Main1
client:phones:Mobile1
client:phones:Home1
client:phones:Work1
client:phones:Other1
client:phones:Fax1Object
client:phones:Main1:id
client:phones:Mobile1:id
client:phones:Home1:id
client:phones:Work1:id
client:phones:Other1:id
client:phones:Fax1:idString
client:phones:Main1:number
client:phones:Mobile1:number
client:phones:Home1:number
client:phones:Work1:number
client:phones:Other1:number
client:phones:Fax1:numberString
client:phones:Main1:primary
client:phones:Mobile1:primary
client:phones:Home1:primary
client:phones:Work1:primary
client:phones:Other1:primary
client:phones:Fax1:primaryString (Boolean)
client:phones:Main1:sms_allowed
client:phones:Mobile1:sms_allowed
client:phones:Home1:sms_allowed
client:phones:Work1:sms_allowed
client:phones:Other1:sms_allowed
client:phones:Fax1:sms_allowedString (Boolean)
client:tagsString
client:updated_atDate
costNumber
created_atDate
custom_field_valuesList
custom_field_values:#Object
custom_field_values:#:created_atString (Date)
custom_field_values:#:nameString
custom_field_values:#:positionString (Number)
custom_field_values:#:unitString
custom_field_values:#:updated_atString (Date)
custom_field_values:#:valueList OR String
custom_field_values:#:value_typeString
custom_field_values:#:value:#String
deposit_amountNumber
discount_amountNumber
idString
job_descriptionString
jobsList
jobs:#Object
jobs:#:automatically_charge_invoiceIndex 1: Boolean
Index >1: String (Boolean)
jobs:#:billing_typeString
jobs:#:clientString
jobs:#:completed_atIndex 1: Date
Index >1: String (Date)
jobs:#:created_atIndex 1: Date
Index >1: String (Date)
jobs:#:custom_field_valuesList
jobs:#:custom_field_values:#Object
jobs:#:custom_field_values:#:created_atIndex 1: Date
Index >1: String (Date)
jobs:#:custom_field_values:#:nameString
jobs:#:custom_field_values:#:positionIndex 1: Number
Index >1: String (Number)
jobs:#:custom_field_values:#:unitString
jobs:#:custom_field_values:#:updated_atIndex 1: Date
Index >1: String (Date)
jobs:#:custom_field_values:#:valueList OR String
jobs:#:custom_field_values:#:value_typeString
jobs:#:custom_field_values:#:value:#String
jobs:#:end_atIndex 1: Date
Index >1: String (Date)
jobs:#:idString
jobs:#:job_numberIndex 1: Number
Index >1: String (Number)
jobs:#:job_typeString
jobs:#:line_itemsList
jobs:#:line_items_costIndex 1: Number
Index >1: String (Number)
jobs:#:line_items_nameString
jobs:#:line_items:#String
jobs:#:propertyString
jobs:#:quoteString
jobs:#:start_atIndex 1: Date
Index >1: String (Date)
jobs:#:statusString
jobs:#:total_valueIndex 1: Number
Index >1: String (Number)
jobs:#:updated_atIndex 1: Date
Index >1: String (Date)
messageString
quote_numberNumber
quote_statusString
sent_atDate
transitioned_atDate
updated_atDate
won_atDate
Request Opportunity
FieldType
clientObject
client:balanceNumber
client:billing_addressObject
client:billing_address:cityString
client:billing_address:countryString
client:billing_address:pcString
client:billing_address:provinceString
client:billing_address:streetString
client:billing_address:street1String
client:billing_address:street2String
client:company_nameString
client:created_atDate
client:custom_field_valuesObject
client:custom_field_values:<custom_field_name>List OR String
client:custom_field_values:<custom_field_name>:<n>String
client:emailsList
client:emails:#Object
client:emails:#:addressString
client:emails:#:descriptionString
client:emails:#:idString
client:emails:#:primaryIndex 1: Boolean
Index >1: String (Boolean)
client:first_nameString
client:idString
client:is_companyBoolean
client:is_achievedBoolean
client:last_nameString
client:nameString
client:phonesObject
client:phones:Main1
client:phones:Mobile1
client:phones:Home1
client:phones:Work1
client:phones:Other1
client:phones:Fax1
client:phones:Main1:id
client:phones:Mobile1:id
client:phones:Home1:id
client:phones:Work1:id
client:phones:Other1:id
client:phones:Fax1:idObject
client:phones:Main1:number
client:phones:Mobile1:number
client:phones:Home1:number
client:phones:Work1:number
client:phones:Other1:number
client:phones:Fax1:numberString
client:phones:Main1:primary
client:phones:Mobile1:primary
client:phones:Home1:primary
client:phones:Work1:primary
client:phones:Other1:primary
client:phones:Fax1:primaryString (Boolean)
client:phones:Main1:sms_allowed
client:phones:Mobile1:sms_allowed
client:phones:Home1:sms_allowed
client:phones:Work1:sms_allowed
client:phones:Other1:sms_allowed
client:phones:Fax1:sms_allowedString (Boolean)
client:tagsString
client:updated_atDate
created_atDate
custom_field_valuesList
custom_field_values:#Object
custom_field_values:#:created_atString (Date)
custom_field_values:#:nameString
custom_field_values:#:positionString (Number)
custom_field_values:#:unitString
custom_field_values:#:updated_atString (Date)
custom_field_values:#:valueList OR String
custom_field_values:#:value_typeString
custom_field_values:#:value:#String
idString
propertyString
sourceString
statusString
titleString
updated_atDate

​
Standard Field Mapping

Hatch standard fields are mapped from Jobber detail fields as detailed below. Quote Opportunity
The base object of this opportunity model is the Jobber Quote. Therefore, (as an example) the id field would indicate the ID of the Jobber Quote record.
In Quote opportunities, the following Hatch standard fields are mapped from Jobber detail fields:
Hatch Standard FieldJobber Detail Field
Emailclient:emails:1:address
External IDid
External Contact IDclient:id
External Created Atcreated_at
External Updated At
(used for Hatch opportunity sorting)updated_at
First Nameclient:first_name
Last Nameclient:last_name
Phone Numberclient:phones:Main1:number (or, if missing: client:phones:Mobile1:number, client:phones:Work1:number, client:phones:Home1:number, client:phones:Other1:number, client:phones:Fax1:number)
Request Opportunity
The base object of this opportunity model is the Jobber Request. Therefore, (as an example) the id field would indicate the ID of the Jobber Request record.
In Request opportunities, the following Hatch standard fields are mapped from Jobber detail fields:
Hatch Standard FieldJobber Detail Field
Emailclient:emails:1:address
External IDid
External Contact IDclient:id
External Created Atcreated_at
External Updated At
(used for Hatch opportunity sorting)updated_at
First Nameclient:first_name
Last Nameclient:last_name
Phone Numberclient:phones:Main1:number (or, if missing: client:phones:Mobile1:number, client:phones:Work1:number, client:phones:Home1:number, client:phones:Other1:number, client:phones:Fax1:number)