Summary
Jobber clients can be created and updated from iPaaS.com Customers through iPaaS.com's outbound events or a Manual Sync, so customers from your store, accounting system, CRM or forms are ready in Jobber for requests, quotes and jobs. The parent collection Add/Update Jobber Client FROM iPaaS.com writes the client's first and last name, company name, email address and phone number, and its child Add/Update Jobber Client Billing Address FROM iPaaS.com writes the client's billing address. Orders sent to Jobber as work requests depend on it: an order's customer is sent through this collection first.
ID Format
Manual Sync ID Format
Enter the iPaaS.com customer id on the iPaaS.com Manual Sync page, for example 165619. The billing address has no Manual Sync entry of its own: it is sent with its customer.
External ID Format
Client: after a successful transfer, iPaaS.com saves the Jobber client's API id (for example Z2lkOi8vSm9iYmVyL0NsaWVudC8xNTY3NjgxMDc=) as the external ID on a dedicated external-ID record for the customer. Later transfers of the same customer find the client through that link and update it instead of creating a second one.
Billing address: the address that became the billing address is linked separately, as the client's Jobber API id followed by |BILL (for example Z2lkOi8vSm9iYmVyL0NsaWVudC8xNTY3NjgxMDc=|BILL). When the client comes back to iPaaS.com, its billing address updates that address instead of adding a second one.
Deleted Record Support
Deleting is not supported. Deleting or deactivating a customer in iPaaS.com does not delete or archive the Jobber client, and the templates include no delete mappings. Archive the client in Jobber by hand when it is no longer needed.
Custom Field Support
iPaaS.com customer custom fields can be written to Jobber client custom fields. None are mapped by default. Add a Field mapping from the iPaaS.com customer custom field to a destination custom field named exactly like the Jobber custom field.
New Jobber custom fields: when Jobber has no client custom field with that name, the integration creates one as a text field the first time a non-empty value arrives.
Other field types: to have a number, true/false or dropdown field, create it in Jobber first with exactly the mapped name.
Refused values: a value Jobber refuses for its field (for example text in a number field) is skipped with no error.
Validate a new custom field mapping in a staging subscription before relying on it in production.
Mapping Collection Status
Status: Enabled (parent and child).
Trigger Events: the iPaaS.com events customer/created and customer/updated, turned on under Outbound Data Flows. The billing address has no trigger of its own; it runs in the same transfer as its parent.
Duplicate or Conflicting Mappings
Add/Update Jobber Client TO iPaaS.com: writes the same customers from Jobber to iPaaS.com.
Add/Update Jobber Client Billing Address TO iPaaS.com: writes the Jobber billing address back to the iPaaS.com customer.
Important: before turning on automatic transfers in both directions, review both filters and decide which system is the source of truth for each field. A client written by this collection is sent back to iPaaS.com once by Jobber's events, which repeats the same values. If you add a second collection of either type, give the two filters no record in common: every collection whose filter matches a record runs.
Collision Handling
This collection supports the Collision Handling Method, set on the collection under Mappings, and matches by the customer's email address. Templates do not carry a collision handling method, so set it after subscribing. Update and Link is recommended: a new customer whose email a Jobber client already has is linked to that client and updates it, instead of creating a second client. The other methods behave as follows:
Remap and Link: links the existing Jobber client and updates it.
Update and No Link: updates the existing Jobber client without saving a link to it.
Error: not recommended for this collection; use Update and Link.
When the search finds several Jobber clients with the email, the transfer stops with JOBR-VALD-1005, shown in Dashboard / Integration Monitoring / Error Logs. Merge the duplicate clients in Jobber, or link the customer to one of them by hand, then resend the customer. A customer with no email address cannot be matched to an existing Jobber client.
The billing address child has no Collision Handling Method of its own: it is written to the client the parent creates, links or updates.
Unmapped Field Overwrite Risk
Client fields: each update writes every mapped client field. An empty name or company in iPaaS.com clears it in Jobber, while an empty email or phone leaves the client's email or phone as it is. Client fields with no mapping are left alone in Jobber.
Billing address parts: each update sends every part of the billing address (Street1, Street2, City, Province, PostalCode and Country). A part that is empty in iPaaS.com, or whose mapping is removed, clears that part on the client's billing address in Jobber. For example, a second line that staff entered in Jobber is cleared when the iPaaS.com address has none. See Keeping an address part that Jobber staff edit under Mappings.
Supported Child Collections
Parent: Add/Update Jobber Client FROM iPaaS.com
Add/Update Jobber Client Billing Address FROM iPaaS.com: the customer's address that becomes the client's billing address and, on create, its first service property.
System Caveats
Jobber Caveats
Client needs a name: a customer that reaches Jobber with no first name, last name or company name stops with JOBR-VALD-1006, shown in Dashboard / Integration Monitoring / Error Logs. Give the customer a name or a company in the source system, or map one.
Linked client deleted in Jobber: if the linked client no longer exists in Jobber, the update stops with JOBR-VALD-1003. Remove the customer's Jobber link in iPaaS.com to create the client again.
One billing address: a Jobber client has one billing address, so only one of the customer's addresses is written. Later addresses on the customer are not sent, and service properties beyond the first are not added; add further properties in Jobber by hand.
Country as text: the country is written as the text iPaaS.com holds, with no conversion.
No primary-billing flag: Jobber has no primary-billing flag, so IsPrimaryBilling is not written to Jobber.
Notification settings unchanged: Jobber's reminder, follow-up and review-request settings on the client are never changed, so nothing in these collections messages your clients.
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
Phone from the first address: iPaaS.com keeps phone numbers on addresses, so the phone written to Jobber is the phone number of the customer's first address, written by the parent collection. A customer with no address, or whose first address has no phone number, leaves the client's phone as it is.
No email: a customer with no email address leaves the client's email as it is, and cannot be matched to an existing Jobber client.
Several subscriptions in one company: iPaaS.com shares customers across the company, so a new customer reaches every Jobber subscription that has this collection on, and becomes a client in each of those Jobber accounts. Keep this collection off on subscriptions that should not receive every customer.
Integration-Specific Caveats
Which address is used: without a filter on the child, the billing address is the first of the customer's addresses with a first street line or a city, whether or not it is marked primary billing in iPaaS.com. A customer with no such address creates a client with no billing address and no service property. See Choosing the billing address under Mappings to send the primary billing address instead.
Other integrations editing customers: another integration on your company that writes customers back to its own system 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.
Setup Requirements
iPaaS.com Configuration
Enable Add/Update Jobber Client FROM iPaaS.com and its child Add/Update Jobber Client Billing Address FROM iPaaS.com.
In the subscription configuration's Outbound Data Flows section, turn on the iPaaS.com events customer/created and customer/updated. No automatic transfers occur until these events are turned on.
Set the Collision Handling Method on the parent collection under Mappings; Update and Link is recommended.
Turn this collection on when you use Add/Update Jobber Request FROM iPaaS.com, since a work request sends its customer through this collection first.
Jobber Configuration
The subscription must be authorized with Jobber; see the Jobber Installation Instructions and Jobber Connections and Settings articles. No Jobber-side setup is needed for these collections. To write to a number, true/false or dropdown custom field, create that client custom field in Jobber first.
Integration Flow
A customer is created or changed in iPaaS.com and the customer/created or customer/updated event fires, or the customer is sent from the Manual Sync page, or a work request sends it first.
The parent filter is checked. A customer without both a first and last name, and without a company name, is skipped with no error.
The integration checks whether the customer is already linked to a Jobber client.
If it is not linked and a Collision Handling Method that matches is set (Update and Link recommended), the integration looks for a Jobber client with the customer's email address, and links and updates that client instead of creating one. Several clients with the email stop the transfer with JOBR-VALD-1005.
Otherwise a new client is created with the mapped values. The billing address from the child collection (the first address with a first street line or a city) becomes the client's billing address and its first service property.
A linked customer updates its client: a changed email or phone replaces the client's primary email or phone instead of adding a second one, and the billing address is replaced (a customer with no address that has a first street line or a city leaves it as it is). The service property is not changed.
iPaaS.com saves the client's Jobber API id as the customer's external ID, and the client's id followed by |BILL as the billing address's external ID.
Mappings
Add/Update Jobber Client FROM iPaaS.com
iPaaS.com data type: Customer
Mapping Filter
// Sends customers Jobber can create: a first and last name, or a company name. return (!string.IsNullOrEmpty(FirstName) && !string.IsNullOrEmpty(LastName)) || !string.IsNullOrEmpty(Company);
Filter Description: a customer is sent only when it has both a FirstName and a LastName, or a Company. Other customers are skipped with no error, and nothing appears in the error logs. Keep the name-or-company condition if you edit the filter, because Jobber needs a name or a company on every client.
Description: creates and updates the Jobber client's names, company name, primary email and primary phone from the iPaaS.com customer.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Jobber) | Description |
Field | FirstName | FirstName | Recommended. The customer's first name, written to the Jobber client's first name. A person customer without a first name and without a company name is not sent. |
Field | LastName | LastName | Recommended. The customer's last name, written to the Jobber client's last name. A person customer without a last name and without a company name is not sent. |
Field | Company | CompanyName | Optional. The customer's company name, written to the Jobber client's company name. A customer with only a company name creates a client with that company name and no person name. |
Field | EmailAddress | Recommended. Written as the client's primary email. A changed email replaces the primary email instead of adding a second one; no email leaves the client's email as it is. The email is also how an existing client is matched (see Collision Handling). | |
Dynamic Formula |
| Phone | Optional. The phone number of the customer's first address, written as the client's primary phone. A changed number replaces the primary phone; no address or no phone leaves the client's phone as it is. |
Add/Update Jobber Client Billing Address FROM iPaaS.com
iPaaS.com data type: Customer Address
Description: writes one of the customer's addresses to the Jobber client's billing address. On create it also becomes the client's first service property, which work requests sent to Jobber use; on an update it replaces the billing address and the service property is not changed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Jobber) | Description |
Field | Address1 | Street1 | Recommended. The first street line. An address with a first street line (or, without one, a city) is the one sent. |
Field | Address2 | Street2 | Optional. The second street line. When the iPaaS.com address has none, a second line entered in Jobber is cleared. |
Field | City | City | Recommended. The city. Only the first address with a first street line or a city is used. |
Field | Region | Province | Recommended. The state or province. An empty region clears the state or province in Jobber. |
Field | PostalCode | PostalCode | Recommended. The ZIP or postal code. An empty postal code clears it in Jobber. |
Field | Country | Country | Recommended. The country, written as the text iPaaS.com holds, with no conversion. An empty country clears it in Jobber. |
Field | IsPrimaryBilling | IsPrimaryBilling | Optional. Not written to Jobber, which has no primary-billing flag. It does not choose the billing address unless you add the filter described below. |
Choosing the billing address
This collection ships without a mapping filter. Every address of the customer is offered, and the integration uses the first one with a first street line or a city as the Jobber billing address, whether or not it is marked primary billing in iPaaS.com.
To send the customer's primary billing address instead, add this filter to the child collection:
return IsPrimaryBilling == true;
With the filter, only the address marked primary billing in iPaaS.com is offered. If that address has neither a first street line nor a city, or the customer has no primary billing address, the client is written with no billing address (and, on create, no service property).
Keeping an address part that Jobber staff edit
Each update sends every part of the billing address, so an unmapped or empty part clears Jobber's value. When Jobber staff also edit client addresses, keep a part's current Jobber value by changing its mapping to a Dynamic Formula such as:
return DestinationValue != null ? DestinationValue.Street2 : null;
Use that part's Jobber field name (Street1, Street2, City, Province, PostalCode or Country) in place of Street2. Validate the formula in a staging subscription before relying on it in production.
Error Handling
Errors appear in Dashboard / Integration Monitoring / Error Logs. The full list is in the Jobber Error Messages article.
JOBR-VALD-1006: "Jobber needs a first name, last name or company name to create a client." The customer reached Jobber with no name and no company. Give the customer a name or a company in the source system, or map one, then resend it.
JOBR-VALD-1005: "{n} Jobber clients share the email {email}; merge them in Jobber, or link the customer by hand." The collision search found several Jobber clients with the customer's email. Merge the duplicate clients in Jobber, or link the customer to one of them by hand, then resend the customer.
JOBR-VALD-1003: "Jobber client {id} no longer exists. Remove the customer's Jobber link in iPaaS.com to create it again." The linked client was deleted in Jobber. Remove the customer's Jobber link in iPaaS.com and resend the customer to create the client again.
JOBR-VALD-1002: "The customer has no Jobber id to update." An update arrived for a customer with no Jobber link. Resend the customer as a create, or link it to its Jobber client.
JOBR-VALD-1004: "Deleting clients in Jobber is not supported by this integration." A delete was requested. Archive the client in Jobber by hand.
JOBR-VALD-1017: "A client address moves with its client; transfer the client, and remove any collection that sends addresses on their own." An address was sent on its own. Send the customer instead, and remove any collection that sends addresses by themselves.
JOBR-EXTN-1003: "Jobber request limit / query cost limit reached while {action}: retry after {n}s." Jobber's rate limit was reached. No action is required: the transfer is rescheduled automatically once the limit resets.
Testing & Validation
Test Scenarios
Create an iPaaS.com customer with a first and last name, email, phone and a full address, and confirm a Jobber client is created with those values, the address as its billing address and as its first service property.
Change the customer's email, phone and street, and confirm the client's primary email and phone are replaced (not added) and the billing address is updated.
Create a customer with only a company name and confirm the client is created with that company name.
Create a customer with only a first name and no company, and confirm it is skipped with no error.
Manually sync a customer by its iPaaS.com customer id and confirm the client is created or updated.
With Update and Link set, create a customer whose email an existing Jobber client has, and confirm that client is linked and updated instead of a second client being created.
Add the filter return IsPrimaryBilling == true; to the child, give a customer two addresses with the second marked primary billing, and confirm the second address becomes the Jobber billing address.
Validation Checklist
The customer's external ID for Jobber is saved after the first transfer, and a second transfer updates the same client.
The billing address is linked as the client's id followed by |BILL.
No second email or phone is added to the client on update.
Address parts you keep in Jobber with the keep formula are not cleared on update.
No errors appear in Dashboard / Integration Monitoring / Error Logs for the test customers.
Additional Notes
Client details beyond the mapped fields (title, the company-name-as-main-name option, mobile phone) are not mapped by default and are left alone in Jobber on update.
Additional service properties, and notification settings on the client, are managed in Jobber.
Limitations that apply at the time this documentation was written are listed in the Jobber Known Limitations article.
Related Documents
Related Mapping Documentation


