Skip to main content

Jobber to iPaaS.com Client Mapping Documentation

How Jobber clients and their billing addresses are sent to iPaaS.com as customers.

Summary

iPaaS.com Customers can be transferred from Jobber clients through Jobber events, a scheduled poll, or Manual Sync. Each transfer sends the client's name, company, primary email address and customer number, and the child collection sends the client's billing address with its primary phone number. Most other Jobber flows depend on this collection: an invoice needs its client in iPaaS.com, and the other systems you connect (accounting, point of sale, CRM, email marketing) receive the customer from here through their own collections.

ID Format

Manual Sync ID Format

Enter the number at the end of the client's web address in Jobber. For the client at secure.getjobber.com/clients/156768107, enter 156768107. The client's Jobber API id (for example Z2lkOi8vSm9iYmVyL0NsaWVudC8xNTY3NjgxMDc=) is accepted too, and both update the same linked customer.

External ID Format

  • Customer: after a successful transfer, iPaaS.com saves the client's Jobber API id (for example Z2lkOi8vSm9iYmVyL0NsaWVudC8xNTY3NjgxMDc=) as the external ID on a dedicated external-ID record for the customer. Later transfers of the same client find the customer through that link and update it instead of creating a second one.

  • Billing address: the address is linked separately, as the client's Jobber API id followed by |BILL (for example Z2lkOi8vSm9iYmVyL0NsaWVudC8xNTY3NjgxMDc=|BILL). Later transfers of the same client update that address instead of adding a second one.

The customer number (for example JOBBER-156768107) is a field on the customer, not the link: the external-ID record is what matches a client to its customer.

Deleted Record Support

Deleting or archiving a client in Jobber does not delete or deactivate the iPaaS.com customer. No delete mappings are included in the templates, and deletions do not propagate from Jobber to iPaaS.com.

Custom Field Support

Jobber client custom fields can be sent to iPaaS.com customer custom fields. None are mapped by default. To send one:

  1. In iPaaS.com, create the customer custom field that should receive the value.

  2. In the subscription's custom fields for Jobber clients, add a custom field whose name is the Jobber custom field's label exactly as Jobber shows it (for example Gate Code).

  3. In Add/Update Jobber Client TO iPaaS.com, add a Field mapping from that Jobber custom field to the iPaaS.com customer custom field, and save.

Every Jobber custom field type arrives as text: a true/false field as true or false, a link field as its web address, and an area field as length by width (for example 10x12). A custom field with no value in Jobber is sent empty. The billing address collection does not support custom fields.

Mapping Collection Status

  • Status: Enabled.

  • Trigger Events: the Jobber events CLIENT_CREATE and CLIENT_UPDATE, and the poll scope CLIENT_POLL. The billing address has no trigger of its own; it is sent in the same transfer as its client.

Duplicate or Conflicting Mappings

  • Add/Update Jobber Client FROM iPaaS.com: writes the same customers from iPaaS.com to Jobber.

  • Add/Update Jobber Client Billing Address FROM iPaaS.com: writes customer addresses from iPaaS.com to the Jobber client's billing address.

Before turning on automatic transfers in both directions, review both filters and decide which system is the source of truth for each field. The integration recognizes its own changes, so a client it has just written is not sent straight back, but two systems that both edit the same field will overwrite each other's values. If you add a second collection of the same type, give the two filters no record in common: every collection whose filter matches a client runs, and each one replaces the whole customer or address.

Record Matching

A Jobber client that is not linked to an iPaaS.com customer yet is linked to the existing customer with the same email address, and updates it instead of creating a second customer. Its billing address then updates that customer's primary billing address (or its first address when none is marked) instead of being added as a second address. This matching is built into the integration and runs automatically; neither collection has a Collision Handling Method to set. A client with no email address cannot be matched or sent (see Jobber Caveats).

Unmapped Field Overwrite Risk

Warning: iPaaS.com replaces the whole record on each update, so any field these collections do not map is emptied every time a client is sent.

  • Customer: the default template maps every customer field. Two of those mappings keep values Jobber does not hold: Comment keeps the comment the customer already has, and Company keeps its value when the Jobber client has no company name. Their notes say Keep: do not remove them.

  • Billing address: the collection does not map Address3, Company, FirstName, LastName or Type. The IsPrimaryShipping mapping keeps the address's primary-shipping flag, a value Jobber does not hold; its note says Keep: do not remove it. The PreventDuplicate mapping says Keep too: do not remove it.

If you remove a mapping, or another system fills a field these collections do not map, keep its value with a Dynamic Formula mapping that reads DestinationValue, such as return DestinationValue != null ? DestinationValue.Comment : null;, using that field's name in place of Comment.

Supported Child Collections

Parent Collection: Add/Update Jobber Client TO iPaaS.com

  • Add/Update Jobber Client Billing Address TO iPaaS.com: the client's billing address and primary phone number, linked as the client's Jobber API id followed by |BILL. It runs only as the child of the client, in the same transfer.

System Caveats

Jobber Caveats

  • A client needs an email address: a Jobber client with no email is not sent, and the transfer stops with JOBR-VALD-1016, shown in Dashboard / Integration Monitoring / Error Logs. Add an email to the client in Jobber; the client's next change sends it, or run a Manual Sync for the client. A lead with no invoice is skipped by the filter instead and raises no error.

  • Leads: a Jobber lead is a prospect who has not bought yet. Leads with no invoice are not sent. A client that Jobber still marks as a lead after invoicing it is sent, because its invoices need their customer in iPaaS.com.

  • Several emails and phones: a Jobber client can have several emails and phone numbers. The one marked primary is sent, or the first when none is marked.

  • Only the billing address is sent: Jobber service properties stay in Jobber and are not sent as addresses. A billing address with neither a street nor a city is not sent, and the client then arrives without an address and without a phone number.

  • Country as text: the country is sent as the text Jobber holds, with no conversion to a country code.

  • Rate limiting: Jobber limits how much an app can request from its API in a short time. When the limit is reached, the transfer is rescheduled automatically to run once the limit resets; no action is required.

iPaaS.com Caveats

  • One customer per email address: iPaaS.com requires an email on every customer and allows only one customer per email address. If two Jobber clients share an email, keep only one of them in Jobber, or give each its own email, before they are sent.

  • A name or a company: iPaaS.com requires at least one of FirstName, LastName or Company on every customer. Every Jobber client has a first name, a last name or a company name, so keep all three mapped.

  • Phone numbers live on addresses: iPaaS.com keeps phone numbers on customer addresses, so the client's phone number travels with its billing address.

  • Other addresses are kept: addresses that other systems added to the customer are not changed or removed by these collections.

Integration-Specific Caveats

  • Other integrations editing customers: another integration on your company that writes customers back to its own system, and receives them back through its own collections, can pass the same change back and forth with Jobber. Give each system a clear role before turning on automatic transfers in more than one integration.

  • Clients sent before an invoice: when a Jobber invoice is sent to iPaaS.com and its client is not linked to a customer yet, the client is sent first through this collection, with its filter and mappings.

Setup Requirements

iPaaS.com Configuration

  • In the subscription configuration's Inbound Data Flows section, turn on the Jobber events CLIENT_CREATE and CLIENT_UPDATE. When you turn them on, iPaaS.com registers them with your Jobber account, and clients created or changed in Jobber are sent within moments. No automatic transfers occur until these events are turned on.

  • Optionally, create a scheduled Webhook Poll Request event for this subscription with the poll scope CLIENT_POLL and the Filter left empty (see Jobber Installation Instructions). Once a day is a sensible safety net with the Jobber events on, or use it to load existing clients the first time. The Customer Poll Days setting controls how far back the first poll looks.

  • Keep both collections enabled: the billing address is sent only with its client.

The Inbound Data Flows section with CLIENT_CREATE and CLIENT_UPDATE turned on

Jobber Configuration

No Jobber-side setup is needed beyond authorizing the subscription: the events are registered with your Jobber account when you turn them on in iPaaS.com. Authorization is covered in the Jobber Installation Instructions, and the settings in Jobber Connections and Settings.

Integration Flow

  1. A client is created or changed in Jobber and the Jobber event arrives, the poll finds the client changed since the last poll, an invoice for an unlinked client is being sent, or you run a Manual Sync with the client's number.

  2. The integration reads the client from Jobber, with its emails, phones, billing address and custom fields. A client that no longer exists in Jobber is not sent.

  3. If the client has no email address and is not a lead without an invoice, the transfer stops with JOBR-VALD-1016.

  4. If the client is not linked to an iPaaS.com customer yet, the integration looks for the iPaaS.com customer with the client's email address and links the client to it, and links the client's billing address to that customer's primary billing address (see Record Matching).

  5. The collection's filter runs: a lead with no invoice is skipped.

  6. The mappings run, and the customer is created, or the linked customer is updated. Whether a client is added or updated depends on whether it is already linked, not on which event arrived.

  7. The child collection Add/Update Jobber Client Billing Address TO iPaaS.com runs in the same transfer to add or update the billing address, linked as the client's Jobber API id followed by |BILL.

A customer transferred from Jobber, shown in iPaaS.com

Mappings

Add/Update Jobber Client TO iPaaS.com

iPaaS.com data type: Customer

Mapping Filter

// Sends Jobber clients, and leads that have an invoice. Leads with no invoice (prospects) are skipped,
// so accounting, point-of-sale and payment systems receive no prospects.
return IsLead != true || HasInvoices == true;

Filter Description: every Jobber client is sent when it is not a lead (IsLead is not true). A lead is sent only when it has at least one invoice (HasInvoices is true), because its invoices need their customer in iPaaS.com. A lead with no invoice, a prospect who has not bought yet, is skipped without an error, so accounting, point-of-sale and payment systems receive no prospects.

Description: creates and updates the iPaaS.com customer from the Jobber client.

Mapping Type

Source Field (Jobber)

Destination Field (iPaaS.com)

Description

Dynamic Formula

return DestinationValue != null && !string.IsNullOrEmpty(DestinationValue.CustomerNumber) ? DestinationValue.CustomerNumber : "JOBBER-" + ClientNumber;

CustomerNumber

Required. A new customer gets JOBBER- followed by the number at the end of the client's Jobber web address (for example JOBBER-156768107). A customer that already has a number keeps it, so a number another system set is never overwritten. To use a different numbering scheme, change the formula before the first client is sent.

Field

Email

EmailAddress

Required. The client's primary email address in Jobber, or its first email when none is marked primary. iPaaS.com requires an email and allows one customer per email address. A client without an email stops with JOBR-VALD-1016.

Field

FirstName

FirstName

Recommended. The client's first name in Jobber. A client entered only as a company has no first name, and the customer then has none either.

Field

LastName

LastName

Recommended. The client's last name in Jobber. A client entered only as a company has no last name, and the customer then has none either.

Dynamic Formula

return !string.IsNullOrEmpty(CompanyName) ? CompanyName : (DestinationValue != null && DestinationValue.Company != null ? DestinationValue.Company : "");

Company

Recommended. The client's company name in Jobber. When the client has none, the customer keeps the company it already has, and a new customer gets an empty company.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Comment : null;

Comment

Keep. Do not remove this mapping. Jobber has no comment field, so this keeps the comment the customer already has, for example one another system set. Without it, the comment is emptied on the next update. A new customer gets no comment.

Full formulas. The Source Field cells above show each formula's return line. The complete live formulas, comments included, are:

CustomerNumber (Source Field):

// Keeps the customer number the iPaaS.com customer already has; a new customer gets JOBBER- and the client number
// Jobber shows in its web address (e.g. JOBBER-156768107).
return DestinationValue != null && !string.IsNullOrEmpty(DestinationValue.CustomerNumber) ? DestinationValue.CustomerNumber : "JOBBER-" + ClientNumber;

Company (Source Field):

// The Jobber company name; when the client has none, keep the company the iPaaS.com customer already has.
return !string.IsNullOrEmpty(CompanyName) ? CompanyName : (DestinationValue != null && DestinationValue.Company != null ? DestinationValue.Company : "");

Comment (Source Field):

// Jobber has no comment: keep the value the iPaaS.com record already has.
return DestinationValue != null ? DestinationValue.Comment : null;

FirstName, LastName and Company: iPaaS.com requires at least one of the three on every customer, so keep all three mapped.

Add/Update Jobber Client Billing Address TO iPaaS.com

iPaaS.com data type: Customer Address

Description: adds or updates the client's billing address on the iPaaS.com customer, with the client's primary phone number, and marks it as the customer's primary billing address. A street or a city is needed for the address to be sent.

Mapping Type

Source Field (Jobber)

Destination Field (iPaaS.com)

Description

Static

"true"

PreventDuplicate

Keep. Do not remove this mapping. Turns on iPaaS.com's duplicate-address check, so repeated updates of the same client do not add the same address to the customer again.

Field

Street1

Address1

Recommended. The first line of the client's billing address in Jobber.

Field

Street2

Address2

Optional. The second line of the client's billing address in Jobber.

Field

City

City

Recommended. The city of the client's billing address in Jobber.

Field

Province

Region

Recommended. The state or province of the client's billing address in Jobber.

Field

PostalCode

PostalCode

Recommended. The ZIP or postal code of the client's billing address in Jobber.

Field

Country

Country

Recommended. The country of the client's billing address, sent as the text Jobber holds, with no conversion to a country code.

Field

IsPrimaryBilling

IsPrimaryBilling

Recommended. Marks the address as the customer's primary billing address. Only the Jobber billing address is sent, so this is always true.

Dynamic Formula

return DestinationValue != null && DestinationValue.IsPrimaryShipping;

IsPrimaryShipping

Keep. Do not remove this mapping. Jobber has no shipping flag, so this keeps the primary-shipping flag the address already has (false for a new address). Without it, the flag is cleared on the next update.

Field

Phone

PhoneNumber

Optional. The client's primary phone number in Jobber, or its first phone number when none is marked primary. A client sent without an address is sent without a phone number.

Full formula. The Source Field cell above shows the formula's return line. The complete live formula, comment included, is:

IsPrimaryShipping (Source Field):

// Jobber has no shipping flag: keep the value the iPaaS.com address already has (false for a new address).
return DestinationValue != null && DestinationValue.IsPrimaryShipping;

Error Handling

The full list of codes is in the Jobber Error Messages article. Errors appear in Dashboard / Integration Monitoring / Error Logs.

  • JOBR-VALD-1016: "Jobber client {name} (clients/{number}) has no email address, and iPaaS.com customers need one. Add an email to the client in Jobber; its next change sends it, or run a Manual Sync for the client." The client has no email, and iPaaS.com customers need one. Resolution: add an email to the client in Jobber; its next change sends it, or run a Manual Sync for the client. Invoices that already stopped with this error are not retried: resend each one after the email is added.

  • JOBR-EXTN-1003: "Jobber request limit / query cost limit reached while {action}: retry after {n}s." Jobber's request limit was reached during the transfer. Resolution: no action; iPaaS.com retries automatically after the limit resets.

  • JOBR-VALD-1017: "A client address moves with its client; transfer the client, and remove any collection that sends addresses on their own." A billing address was sent on its own. Resolution: run a Manual Sync of the client instead. Never remove the default billing address collection.

  • JOBR-AUTH-1003: "Jobber no longer accepts this subscription's authorization (it was disconnected, re-authorized elsewhere, or the app changed). Open the subscription and click Authorize again." Resolution: click Authorize on the subscription again. If it keeps happening, check that iPaaS.com is still connected in Jobber's App Marketplace.

  • JOBR-AUTH-1004: "Jobber refused the authorization while {action}. Open the subscription and click Authorize again." Resolution: click Authorize on the subscription again, then resend the client.

Testing & Validation

Test Scenarios

  1. Create a client with an email and a billing address in Jobber, and confirm that a customer with that address appears in iPaaS.com, with a customer number of JOBBER- followed by the client's number.

  2. Change the client's name and billing address in Jobber, and confirm that the same customer and address are updated, with no second customer or address.

  3. Create a client with no email address, and confirm that it stops with JOBR-VALD-1016 in Dashboard / Integration Monitoring / Error Logs. Add an email and confirm that the client is then sent.

  4. Run a Manual Sync with the number at the end of a client's Jobber web address, and confirm that the customer is updated.

  5. Create an iPaaS.com customer with an email address, then create a Jobber client with the same email, and confirm that the client updates that customer instead of creating a second one.

  6. Create a lead with no invoice in Jobber, and confirm that it is not sent.

Validation Checklist

  • CLIENT_CREATE and CLIENT_UPDATE are turned on under Inbound Data Flows, or a polling event exists for CLIENT_POLL.

  • Every client you expect to send has an email address in Jobber.

  • The Comment, Company, IsPrimaryShipping and PreventDuplicate mappings are still in place.

  • No two collections of the same type have filters that match the same client.

Additional Notes

  • Changes in Jobber to a client's service properties are not sent: only the billing address is.

  • A client deleted or archived in Jobber stays active in iPaaS.com; deactivate the customer by hand if needed.

Related Documents

Related Mapping Documentation

Did this answer your question?