Summary
Jobber products and services can be created and updated from iPaaS.com Product records through iPaaS.com events or a Manual Sync, so the service and labor items your accounting or product system manages are ready to use on Jobber quotes, jobs and invoices. Each transfer sends the product's name, description, default price, category (translated from the product type), a taxable flag and visibility (from the product status). Physical stock items usually do not belong in Jobber, so the default filter sends only the products you mark with a service SKU prefix.
ID Format
Manual Sync ID Format
Enter the iPaaS.com product id on the iPaaS.com Manual Sync page, for example 221577.
External ID Format
After a successful transfer, iPaaS.com saves the Jobber item's encoded API id (a string of letters and digits that usually ends in =, for example Z2lkOi8vSm9iYmVyL1Byb2R1Y3RPclNlcnZpY2UvNTUyNTIzMTE=) as the external ID on a dedicated external-ID record for the product. Later transfers of the same product find the item through that link and update it instead of creating a second one. The product's SKU is not sent: Jobber items have no SKU, and the SKU stays on the iPaaS.com product.
Deleted Record Support
This integration never deletes Jobber items, and the default template includes no delete mapping. A delete request stops with JOBR-VALD-1004. To retire an item, set the iPaaS.com product's status to Disabled or Discontinued, and the item is hidden in Jobber.
Custom Field Support
iPaaS.com product custom fields can be sent to Jobber item custom fields. None are mapped by default. To send one:
In iPaaS.com, make sure the product custom field holds the value to send.
In the subscription's custom fields for Jobber products and services, add a custom field whose name is the name the Jobber item custom field should have.
In this collection, add a Field mapping from the iPaaS.com product custom field to that Jobber custom field, and save.
When Jobber has no item custom field with that name, the integration creates one as a text field the first time a non-empty value arrives. The field is created read-only, so it can't be edited by hand in Jobber, but the integration still writes it. A field created by the integration can't be archived in Jobber afterwards, so check the name before the first transfer.
Mapping Collection Status
Status: Disabled by default. The default filter matches no product until you replace its placeholder value with your service SKU prefix, so nothing is sent to Jobber (see Mappings).
Trigger Events: the iPaaS.com events product/created and product/updated, turned on in the subscription configuration's Outbound Data Flows section. Whether an item is added or updated depends on whether the product is already linked to a Jobber item, not on which event arrived.
Duplicate or Conflicting Mappings
Add/Update Jobber Product or Service TO iPaaS.com
Important: that collection writes the same products from Jobber to iPaaS.com. Before turning on automatic transfers in both directions, review both filters and decide which system is the source of truth for each field. Each update from this collection sends the current price and taxable flag, so a price or taxable setting changed by hand in Jobber is replaced on the product's next update. If you add a second collection of this type, give the two filters no record in common: every collection whose filter matches a product runs.
Collision Handling
A collision happens when a product that is not linked to a Jobber item yet has the same name as a Jobber item. Jobber keeps item names unique, so it would refuse a second item with that name. The integration matches by name, with letter case ignored, against the items shown in Jobber.
Set the Collision Handling Method in this mapping collection's settings to Update and Link. A collection created from the default template starts with no method set. The options are:
Update and Link (recommended): the existing Jobber item is linked and updated instead of creating a second item.
Remap and Link: the existing Jobber item is linked and updated, as with Update and Link.
Update and No Link: the existing Jobber item is updated but not linked, so the next transfer matches it by name again.
Error, or no method set (not recommended; use Update and Link): no match is looked for. Jobber refuses the new item and the transfer stops with JOBR-VALD-1001 ("A product or service already exists with that name"), shown in Dashboard / Integration Monitoring / Error Logs. Nothing is linked or changed.
Jobber keeps item names unique, so more than one shown item with the product's name is not expected; if the integration ever finds several, it cannot choose one and the transfer stops with JOBR-VALD-1008. A hidden Jobber item can't be matched by name (see Jobber Caveats).
Supported Child Collections
None: this collection has no child collections.
System Caveats
Jobber Caveats
Categories: Jobber accepts three item categories: PRODUCT, SERVICE and LABOUR. The Jobber Product Category FROM iPaaS.com translation ships with two pairs and no pair for LABOUR (see Lookup Translation Tables). When a product's type has no pair, or the translated value is not one of the three categories, no category is sent and an existing item keeps the category it has.
Hidden items are not found by name: Jobber's search skips hidden items, but their names still count as taken. A product named like a hidden Jobber item can't be matched, and Jobber refuses the new item with JOBR-VALD-1001. Show the item again in Jobber (it is then matched and linked) or rename one of them, then resend the product.
Taxable flag only: Jobber items carry only a taxable flag, so the item is taxable when the product has a tax class, and the tax class name itself is not sent.
No SKU, variants or stock: Jobber items have no SKU, no variants and no stock, so none of these are sent.
Name required: Jobber needs a name to create an item; a product without a name is not sent and the transfer stops with JOBR-VALD-1007.
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
No cost field: iPaaS.com products have no cost field, so no cost is sent to Jobber.
Setup Requirements
iPaaS.com Configuration
Replace the placeholder value in this collection's filter with your service SKU prefix (see Mappings).
Set the Collision Handling Method on this collection to Update and Link (see Collision Handling).
Review the Jobber Product Category FROM iPaaS.com translation and add a pair for each product type you send to Jobber.
In the subscription configuration's Outbound Data Flows section, turn on the iPaaS.com events product/created and product/updated. No automatic transfers occur until these events are turned on.
Jobber Configuration
No Jobber-side setup is needed beyond connecting the Jobber account, covered in Jobber Installation Instructions.
Integration Flow
An iPaaS.com product reaches the integration from an iPaaS.com event or a Manual Sync, and the mapping filter runs. A product whose SKU does not start with your service SKU prefix is skipped.
If the product is already linked to a Jobber item, the integration updates that item, and the transfer ends there.
If it is not linked, the product must have a name, or the transfer stops with JOBR-VALD-1007.
If a Collision Handling Method other than Error is set, the integration looks for a shown Jobber item with the same name, letter case ignored, and links or updates it as the method says (see Collision Handling).
Otherwise the integration creates the item in Jobber, with its mapped custom fields, and saves the item's Jobber API id as the product's external ID.
If the product's status is not Active or Preorder, the new item is hidden in Jobber straight after it is created, so it never appears on quotes.
This collection has no prerequisites: a product has no records it depends on in Jobber, so nothing is sent before it.
Mappings
Add/Update Jobber Product or Service FROM iPaaS.com
iPaaS.com data type: Product
Mapping Filter
// Sends only the iPaaS.com products that are service or labor work in Jobber.
// (Required.) Replace the text in quotes with the SKU prefix that marks those items, for example "SVC-".
// Until it is replaced, this filter matches nothing, so no product is sent to Jobber.
return Sku != null && Sku.StartsWith("REPLACE with your service SKU prefix");Filter Description: only products whose Sku starts with your service SKU prefix are sent, so only the service and labor work you sell through Jobber reaches it. A product with no SKU (Sku != null fails) is skipped. A product whose SKU does not start with the prefix is skipped. Skipped products log no error.
Placeholder value — replace during implementation: the filter compares the SKU with the text REPLACE with your service SKU prefix. Until you replace it, no product matches and nothing is sent to Jobber. Open Mappings → Mapping Collections, open this collection, and replace that text with the prefix your service and labor products share, for example SVC-, keeping the quotation marks: Sku.StartsWith("SVC-"). To select products another way, edit the filter's formula instead.
Description: creates and updates Jobber products and services from iPaaS.com Product records.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Jobber) | Description |
Field | Name | Name | Required. The item's name on Jobber quotes, jobs and invoices (leading and trailing spaces are removed). A product without one is not sent and stops with JOBR-VALD-1007. Jobber keeps item names unique, hidden items included (see Collision Handling). |
Field | Description | Description | Optional. When the product has no description, none is sent, so a new item has none and an existing item keeps its own. |
Field | DefaultPrice | Price | Required. The item's default unit price. If this mapping is removed, new items are created at a price of 0. Each update sends the current price, so a price changed by hand in Jobber is replaced. |
Lookup Translation | Lookup Translation: Jobber Product Category FROM iPaaS.com | Category | Recommended. The Jobber item category, translated from the product type (see Lookup Translation Tables). Without a pair for the product's type, no category is sent. |
Dynamic Formula |
| Taxable | Recommended. Taxable when the product has a tax class, not taxable when it has none. Each update sends the flag, so a taxable setting changed by hand in Jobber is replaced. |
Dynamic Formula | Formula with an or-operator: see Visible below the table | Visible | Recommended. Shows the item in Jobber while the product's status is Active or Preorder, and hides it for any other status, such as Disabled or Discontinued. A new product that is not sellable is created and hidden right after. |
The Dynamic Formula mappings in full, with their comments, exactly as the template ships them (the Visible formula's or-operator cannot sit inside a table cell, so it is shown only here):
Taxable
// Taxable when the product has a tax class. return !string.IsNullOrEmpty(TaxClass);
Visible
// Shown on Jobber quotes and invoices only while the product is sellable (Active or Preorder). return Status == "Active" || Status == "Preorder";
Lookup Translation Tables
Jobber Product Category FROM iPaaS.com
Source Value (iPaaS.com) | Destination Value (Jobber) | Notes |
Physical | PRODUCT | Physical products become Jobber products. |
Virtual | SERVICE | Virtual products become Jobber services. |
The translation ships with no pair for LABOUR. To send labor items as LABOUR, change the Jobber value of the matching pair (for example Virtual to LABOUR) in the translation. Add a pair for each product type you send to Jobber.
Error Handling
The full list of codes and resolutions is in Jobber Error Messages. Errors are shown in Dashboard / Integration Monitoring / Error Logs.
JOBR-VALD-1001 ("A product or service already exists with that name"): Jobber already has an item with the product's name. Resolution: set the Collision Handling Method to Update and Link, show the hidden item in Jobber or rename one of them, then resend the product. If the message says it happened while hiding the new product or service, the item was already created in Jobber: resend the product with Update and Link set, and it is linked.
JOBR-VALD-1007 ("Jobber needs a name to create a product or service."): the product has no name. Resolution: map the product's name to Name, then resend.
JOBR-VALD-1008 (several Jobber items share the name): not expected, because Jobber keeps item names unique; raised if more than one Jobber item has the product's name, so the integration cannot choose one to link. Resolution: rename the duplicate items in Jobber, or set the product's Jobber link by hand, then resend.
JOBR-VALD-1002 ("The product has no Jobber id to update."): an update arrived for a product with no Jobber link. Resolution: resend the product as a create, or link it to its Jobber item.
JOBR-VALD-1004 (delete not supported): this integration never deletes Jobber items. Resolution: set the product's status to Disabled or Discontinued, and the item is hidden.
JOBR-EXTN-1003 (Jobber rate limit): Jobber's request limit was reached. Resolution: none needed; the transfer is rescheduled automatically once the limit resets.
Testing & Validation
Test Scenarios
Replace the filter placeholder with your prefix (for example SVC-), create an iPaaS.com product with SKU SVC-WINDOW-CLEAN, and confirm a Jobber item with the same name, description, price, category and taxable flag appears.
Change the product's name and default price; confirm the same Jobber item updates.
Set the product's status to Disabled; confirm the Jobber item is hidden. Set it to Active; confirm it is shown again.
Create a product whose SKU does not start with the prefix; confirm nothing is sent.
Create a product without a name; confirm JOBR-VALD-1007.
With Update and Link set, create an unlinked product named like an existing shown Jobber item (in different letter case); confirm the existing item is linked and updated instead of a second one being created. With no method set, confirm JOBR-VALD-1001.
Run a Manual Sync with the iPaaS.com product id and confirm the linked item updates.
Validation Checklist
The filter placeholder is replaced with your service SKU prefix.
The Collision Handling Method is set to Update and Link.
The category translation has a pair for every product type you send, including a LABOUR pair if you use labor items.
product/created and product/updated are turned on in Outbound Data Flows.
Custom field names are checked before the first transfer.
Additional Notes
Items come back TO iPaaS.com: with the Jobber product events on, an item this collection writes is sent back through Add/Update Jobber Product or Service TO iPaaS.com as an ordinary transfer. The product is left unchanged by that return, but it is one extra transfer per write. When the item comes back, a hidden item returns as Disabled unless the product is already Discontinued, and a shown item returns as Active unless the product is already Preorder. Another integration on your company that writes products back to its own system can pass the same change back and forth; give each system a clear role before turning on automatic transfers in more than one integration.
A refused hide step: if Jobber refuses to hide a new item that is not sellable, the transfer stops with JOBR-VALD-1001 after the item was already created. Set the Collision Handling Method to Update and Link and resend the product: the item is then linked.
Out of scope: SKU, variants, cost and inventory are not sent.
Related Documents
Related Mapping Documentation


