Skip to main content

Jobber to iPaaS.com Product or Service Mapping Documentation

How Jobber products and services are sent to iPaaS.com as products.

Summary

iPaaS.com Products can be transferred from Jobber products and services through Jobber events, a poll, a Manual Sync, or automatically before an invoice. Each transfer sends the item's name, description, default price, category (as the product type) and visibility (as the product status). The collection serves two needs: the other systems you connect (accounting, point of sale, an online store) receive your Jobber items, and every Jobber invoice line finds its item in iPaaS.com. Turn it on, and load your existing items, before Add/Update Jobber Invoice TO iPaaS.com.

ID Format

Manual Sync ID Format

Enter either of these on the iPaaS.com Manual Sync page. Both forms update the same linked product.

  • Jobber web address number: the number at the end of the item's web address in Jobber (digits only), for example 55252311.

  • Jobber API id: the item's encoded Jobber API id, a string of letters and digits that usually ends in =, for example Z2lkOi8vSm9iYmVyL1Byb2R1Y3RPclNlcnZpY2UvNTUyNTIzMTE=.

External ID Format

After a successful transfer, iPaaS.com saves the item's encoded Jobber 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 item find the product through that link and update it instead of creating a second one, even after the item is renamed in Jobber.

Deleted Record Support

Deleting an item in Jobber does not delete the iPaaS.com product, and the default template includes no delete mapping. Hide the item in Jobber instead: its product is sent as Disabled.

Custom Field Support

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

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

  2. In the subscription's custom fields for Jobber products and services, add a custom field whose name is the Jobber custom field's label exactly as Jobber shows it.

  3. In this collection, add a Field mapping from that Jobber custom field to the iPaaS.com product custom field, and save.

Item custom fields that the integration creates in Jobber (when Add/Update Jobber Product or Service FROM iPaaS.com sends a custom field Jobber does not have) are read-only in Jobber. They are still sent back to iPaaS.com when mapped here. Values arrive as text, and a custom field with no value in Jobber is sent empty.

Mapping Collection Status

  • Status: Enabled.

  • Trigger Events: the Jobber events PRODUCT_OR_SERVICE_CREATE and PRODUCT_OR_SERVICE_UPDATE, turned on in the subscription configuration's Inbound Data Flows section, and the poll scope PRODUCT_OR_SERVICE_POLL for a first load (see Setup Requirements). Whether an item is added or updated depends on whether it is already linked to an iPaaS.com product, not on which event arrived.

Duplicate or Conflicting Mappings

  • Add/Update Jobber Product or Service FROM iPaaS.com

Important: that collection writes products from iPaaS.com to Jobber. Before turning on automatic transfers in both directions, review both filters and decide which system is the source of truth for each field: an item that both systems edit will take whichever change was sent last. If you add a second collection of this type, give the two filters no record in common: every collection whose filter matches an item runs, and each one replaces the whole product.

Record Matching

There is no Collision Handling Method on this collection, and an unlinked Jobber item is not matched to an existing iPaaS.com product. A SKU can belong to only one iPaaS.com product: when a new item's name is already the SKU of another iPaaS.com product, iPaaS.com refuses the new product as a duplicate SKU, shown in Dashboard / Integration Monitoring / Error Logs, and nothing is linked or changed. Rename the item in Jobber, or change the other product's SKU, then send the item again by changing it in Jobber or running a Manual Sync. To use a different SKU scheme, change the Sku formula before the first item is sent.

Unmapped Field Overwrite Risk

Warning: iPaaS.com replaces the whole product record on each update, so any product field this collection does not map is emptied every time an item is sent. The default template leaves three product fields unmapped: AllowBackorders, AllowDiscounts and InStockThreshold. A value another system set on them is emptied by the next Jobber update. To keep them, add a Dynamic Formula mapping for each, using that field's name in place of AllowBackorders:

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

The template already keeps the fields Jobber does not hold (Barcode, Depth, Height, MSRP, SalePrice, TaxClass, Unit, Weight and Width) the same way; their descriptions below say Keep: do not remove them.

Supported Child Collections

None: this collection has no child collections. It is itself a prerequisite of Add/Update Jobber Invoice TO iPaaS.com (see Integration Flow).

System Caveats

Jobber Caveats

  • Categories: Jobber items have one of three categories, PRODUCT, SERVICE or LABOUR. The translation ships with a pair for each (see Lookup Translation Tables). To send a category as a different product type, edit its pair in the translation.

  • No SKU, no variants, no last-changed date: Jobber items have no SKU, so the template builds one from the item name; they have no variants, so a new product tracks on the product; and they carry no last-changed date, so the poll cannot pick out changed items and sends every item each time it runs.

  • Status from visibility: a status another system set is kept where it still fits: Discontinued stays while the item is hidden, and Preorder stays while it is shown. Showing a hidden item again makes the product Active.

  • Hidden items never sent: an item that is hidden in Jobber before it was ever sent is not sent at all; hiding an item that is already linked sends its product as Disabled.

  • 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 product per SKU: iPaaS.com allows only one product per SKU, so two Jobber items cannot share a name when the name becomes the SKU (see Record Matching). Jobber itself keeps item names unique.

  • Whole-record update: each update replaces the whole iPaaS.com product (see Unmapped Field Overwrite Risk).

Setup Requirements

iPaaS.com Configuration

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

  • First load with the poll: the poll scope PRODUCT_OR_SERVICE_POLL sends every Jobber product and service each time it runs, because Jobber items carry no last-changed date. Use it once, for a first load: create a scheduled Webhook Poll Request event for this subscription with this poll scope and the Filter left empty (see Jobber Installation Instructions), run it, wait until your items appear in iPaaS.com under Products, then delete or turn off the event. Item changes after that arrive through the Jobber events.

  • Leave the Product Page Size setting at its default of 100; the poll reads items in pages of up to 100, and a larger value acts as 100.

  • Enter a Fallback Line SKU in the subscription settings if invoices may carry items this collection leaves out (see Integration Flow).

  • Review the Jobber Product Category TO iPaaS.com translation.

The Inbound Data Flows section with PRODUCT_OR_SERVICE_CREATE and PRODUCT_OR_SERVICE_UPDATE turned on

Jobber Configuration

No Jobber-side setup is needed beyond connecting the Jobber account, covered in Jobber Installation Instructions.

Integration Flow

  1. A Jobber item reaches the integration from a Jobber event, the poll, a Manual Sync, or an invoice that needs it.

  2. The integration reads the item from Jobber. If the item is hidden in Jobber and has never been linked to an iPaaS.com product, it is skipped and nothing is sent.

  3. The mapping filter runs; the default filter accepts every item.

  4. If the item is already linked to an iPaaS.com product, that product is updated; otherwise a new product is created and the item's Jobber API id is saved as its external ID.

  5. Before an invoice: when Add/Update Jobber Invoice TO iPaaS.com sends an invoice whose line item is not linked to an iPaaS.com product yet, the integration sends that item through this collection first, then gives the line the item's SKU. An item this collection leaves out (hidden before it was ever sent, or whose own transfer failed) arrives on the invoice under the product named in the Fallback Line SKU setting.

This collection has no prerequisites of its own.

A product transferred from Jobber, shown in iPaaS.com

Mappings

Add/Update Jobber Product or Service TO iPaaS.com

iPaaS.com data type: Product

Mapping Filter

// Sends every Jobber product and service, so every invoice line finds its item in iPaaS.com.
return true;

Filter Description: the filter returns true for every item, so every Jobber product and service is sent and every invoice line finds its item in iPaaS.com. Separately from the filter, an item that is hidden in Jobber before it was ever sent is not sent at all.

Description: creates and updates iPaaS.com Product records from Jobber products and services.

Mapping Type

Source Field (Jobber)

Destination Field (iPaaS.com)

Description

Dynamic Formula

return DestinationValue != null && !string.IsNullOrEmpty(DestinationValue.Sku) ? DestinationValue.Sku : Name;

Sku

Required. Jobber items have no SKU, so a new product gets the item's name as its SKU. A product that already has a SKU keeps it, so renaming the item in Jobber does not change it and invoice lines keep the same SKU. Do not remove this mapping.

Field

Name

Name

Required. The item's name as shown on Jobber quotes and invoices. Renaming the item in Jobber updates the product's name; its SKU stays the same.

Field

Description

Description

Optional. The item's description in Jobber. An item without one is sent without one.

Field

Price

DefaultPrice

Required. The item's default unit price in Jobber. iPaaS.com requires a default price on every product; an item priced at 0 gets 0.

Lookup Translation

Lookup Translation: Jobber Product Category TO iPaaS.com

Type

Required. The product type, translated from the item's Jobber category (see Lookup Translation Tables).

Dynamic Formula

Multi-line formula: see Status below the table

Status

Required. Active when the item is shown in Jobber, Disabled when it is hidden. Discontinued set by another system stays while the item is hidden, and Preorder stays while it is shown, so a Jobber edit never re-activates a product another system retired.

Dynamic Formula

return DestinationValue != null && DestinationValue.TrackingMethod != null ? DestinationValue.TrackingMethod : "Product";

TrackingMethod

Required. A new product gets Product, because Jobber items have no variants. A product that already has a tracking method keeps it.

Dynamic Formula

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

Barcode

Keep. Do not remove this mapping. Jobber has no barcode; this keeps the barcode the product already has. A new product gets none.

Dynamic Formula

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

Depth

Keep. Do not remove this mapping. Jobber has no depth; this keeps the value the product already has.

Dynamic Formula

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

Height

Keep. Do not remove this mapping. Jobber has no height; this keeps the value the product already has.

Dynamic Formula

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

MSRP

Keep. Do not remove this mapping. Jobber has no MSRP; this keeps the value the product already has.

Dynamic Formula

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

SalePrice

Keep. Do not remove this mapping. Jobber has no sale price; this keeps the value the product already has.

Dynamic Formula

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

TaxClass

Keep. Do not remove this mapping. Jobber has no tax class; this keeps the value the product already has.

Dynamic Formula

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

Unit

Keep. Do not remove this mapping. Jobber has no unit; this keeps the value the product already has.

Dynamic Formula

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

Weight

Keep. Do not remove this mapping. Jobber has no weight; this keeps the value the product already has.

Dynamic Formula

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

Width

Keep. Do not remove this mapping. Jobber has no width; this keeps the value the product already has.

The Dynamic Formula mappings in full, with their comments, exactly as the template ships them (the Status formula spans several lines, so it is shown only here):

Sku

// Keeps the SKU the iPaaS.com product already has; a new product gets the Jobber item name.
return DestinationValue != null && !string.IsNullOrEmpty(DestinationValue.Sku) ? DestinationValue.Sku : Name;

Status

// Hidden in Jobber: Disabled, unless another system already set Discontinued.
// Shown in Jobber: Active, unless another system already set Preorder.
// So a Jobber edit or the product poll never re-activates a product another system retired.
var current = DestinationValue != null ? DestinationValue.Status : null;
if (Visible == false) return current == "Discontinued" ? current : "Disabled";
return current == "Preorder" ? current : "Active";

TrackingMethod

// Keeps the tracking method the iPaaS.com product already has; a new product tracks on the product.
return DestinationValue != null && DestinationValue.TrackingMethod != null ? DestinationValue.TrackingMethod : "Product";

Barcode

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

Depth

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

Height

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

MSRP

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

SalePrice

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

TaxClass

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

Unit

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

Weight

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

Width

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

Lookup Translation Tables

Jobber Product Category TO iPaaS.com

Source Value (Jobber)

Destination Value (iPaaS.com)

Notes

PRODUCT

Physical

Jobber products become physical products.

SERVICE

Virtual

Jobber services become virtual products.

LABOUR

Virtual

Jobber labor items become virtual products.

Every Jobber category has a pair. To send a category as a different product type, edit its pair in the translation.

Error Handling

The full list of codes and resolutions is in Jobber Error Messages. Errors are shown in Dashboard / Integration Monitoring / Error Logs.

  • Duplicate SKU: iPaaS.com refuses a new product whose SKU (the new item's name) already belongs to another product. Nothing is linked or changed. Resolution: rename the item in Jobber, or change the other product's SKU, then send the item again.

  • JOBR-EXTN-1003 (Jobber rate limit): Jobber's request limit was reached. Resolution: none needed; the transfer is rescheduled automatically once the limit resets.

  • JOBR-VALD-1013 (invoice line has no iPaaS.com SKU): shown on the invoice, not on this collection, when an invoice line's item is not in iPaaS.com and the Fallback Line SKU setting is empty. Resolution: check that this collection is on and its filter accepts the item; if the item is hidden in Jobber and was never sent, show it in Jobber with the product events on; if the item's own transfer failed, fix that error; or enter a Fallback Line SKU. Then resend the invoice.

Testing & Validation

Test Scenarios

  1. Create a product or service in Jobber and confirm a product with the same name, description, default price, type and Active status appears in iPaaS.com under Products.

  2. Rename the item and change its price in Jobber; confirm the same product updates its name and default price and keeps its SKU.

  3. Hide the item in Jobber; confirm the product becomes Disabled. Show it again; confirm it becomes Active.

  4. Run a Manual Sync with the item's web address number, and again with its Jobber API id; confirm both update the same product.

  5. Create a Jobber item whose name is already the SKU of another iPaaS.com product; confirm the duplicate SKU error appears and nothing is changed.

  6. Send a Jobber invoice with an item that is not in iPaaS.com yet; confirm the item is sent first and the invoice line carries its SKU.

  7. If you added the keep formula for AllowBackorders (see Unmapped Field Overwrite Risk), set that field on the product from another system, update the item in Jobber, and confirm the value is kept.

Validation Checklist

  • The Jobber product events are turned on in Inbound Data Flows.

  • The poll event was used once for the first load, then deleted or turned off.

  • The category translation has a pair for every category you use.

  • No mapping marked Keep was removed.

  • Fallback Line SKU is set if invoices may carry items that are not sent.

Additional Notes

  • Cost and inventory: iPaaS.com products have no cost field, so the item's internal cost is not sent, and Jobber holds no inventory, so no stock is sent.

  • Items written from iPaaS.com come back: an item that Add/Update Jobber Product or Service FROM iPaaS.com writes to Jobber is sent back through this collection by the Jobber events as an ordinary transfer. The product is left unchanged by that return, but it is one extra transfer per write.

Related Documents

Related Mapping Documentation

Did this answer your question?