New here? This page is a configuration reference for teams implementing the Jobber integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
This document describes the known limitations of the iPaaS.com integration with Jobber, as they stand at the time this documentation was written. They come from the integration's design and from what the Jobber GraphQL API offers apps, and they apply to all subscribers using this integration.
Platform Scope and Tested Versions
Remote Platform: Jobber, the field service management platform.
API: the Jobber GraphQL API at https://api.getjobber.com/api/graphql. Every Jobber read and write goes to this one address, and the API Url setting accepts only an https address on Jobber's own domain. The subscription is connected to a Jobber account through Jobber's own sign-in and Allow Access page (OAuth, with PKCE); the access it grants refreshes automatically.
API Version: Jobber GraphQL schema version 2026-09-25. The integration asks for this version on every call, so a newer Jobber schema version does not change how it behaves.
Test Date: 2026-11-10, integration version 1.0.0, against the 2026-09-25 schema version.
Not built for: Jobber's Client Hub (the portal Jobber gives your clients), or a connection made through any Jobber app other than iPaaS.com's own. This integration connects only to a Jobber account through the Jobber GraphQL API. If Jobber launches a separate product line or a materially different API, this integration will not automatically support it.
1. Clients, Items, Invoices and Work Requests Are the Records That Move
TO iPaaS.com, the integration sends Jobber clients (with their billing address), products and services, and issued invoices (with their lines, payments, tax, billing address and discount). FROM iPaaS.com, it writes iPaaS.com customers as Jobber clients, iPaaS.com products as Jobber products and services, and iPaaS.com orders as Jobber work requests. Jobber quotes, jobs, visits, timesheets, expenses, client contacts and the team roster stay in Jobber.
What this means for you: use invoices TO iPaaS.com to send billed work to your accounting and other systems. An order sent FROM iPaaS.com arrives in Jobber as a work request, which your team converts to a quote or job in Jobber. If your workflow needs another Jobber record type, submit a feature request through your iPaaS.com partner channel describing the records you need; input like this informs future enhancement releases.
2. Existing Records Are Loaded by the Polls
Initialization is not available for this integration. Existing clients and invoices are loaded by the first run of the CLIENT_POLL and INVOICE_POLL polling events, which looks back the number of days in Customer Poll Days and Transaction Poll Days. Each later run continues from where the last one stopped. Existing products and services are loaded by PRODUCT_OR_SERVICE_POLL, which sends every visible item each time it runs (see section 5).
What this means for you: set the Poll Days settings before creating the polling events, to cover the history you want in iPaaS.com. To bring in older records later, raise Poll Days: the next run looks back that far once, then continues from where it stopped. To bring in one record, run a Manual Sync in iPaaS.com with the number at the end of the record's Jobber web address (for example 156768107 from …/clients/156768107). For very large histories, subscribers or their MiSP can use a bulk sync using Postman.
3. Poll Days Use 7 When Blank, Zero or Negative
Customer Poll Days and Transaction Poll Days are number settings with a default of 7. iPaaS.com saves a blank value as the default, 7, and does not save text in these settings. A value of 0 or below also acts as 7. A changed value applies once, on the next run, and only ever widens that run: a smaller number never makes a poll skip changes since the last run.
What this means for you: enter a whole number of days greater than 0. If a poll seems to look back only a week, check that the setting holds the number you intended.
4. Page Size Values Above 100 Act as 100
Customer Page Size, Transaction Page Size and Product Page Size set how many records each poll reads from Jobber per page (defaults 50, 50 and 100). Jobber returns at most 100 records per page, so a value above 100 acts as 100, and a blank value or a value of 0 or below uses the default.
What this means for you: leave the page sizes at their defaults unless your MiSP or iPaaS.com Support recommends otherwise. A larger value does not make a poll faster.
5. The Product Poll Sends Every Item Each Time
Jobber products and services carry no last-changed date, so PRODUCT_OR_SERVICE_POLL cannot pick out changed items: it sends every visible item each time it runs. Hidden items are not sent by the poll.
What this means for you: run PRODUCT_OR_SERVICE_POLL once, to load your existing items before the first invoice, then delete or turn off its polling event. Item changes after that arrive through the Jobber events PRODUCT_OR_SERVICE_CREATE and PRODUCT_OR_SERVICE_UPDATE.
6. Deletes Are Not Sent in Either Direction
Deleting a client, item or invoice in Jobber does not delete the matching iPaaS.com record. The integration never deletes anything in Jobber: a delete requested FROM iPaaS.com stops with JOBR-VALD-1004, and the templates include no delete mappings.
What this means for you: void an invoice in Jobber instead of deleting it; the void reaches iPaaS.com as Cancelled. Hide an item in Jobber; its iPaaS.com product becomes Disabled. To hide a Jobber item FROM iPaaS.com, set the iPaaS.com product's status to Disabled or Discontinued (see section 19). Archive Jobber clients and work requests by hand in Jobber, and deactivate iPaaS.com records by hand when needed.
7. Updates TO iPaaS.com Replace the Whole Record
Each time a Jobber client, item or invoice is sent TO iPaaS.com, it replaces the whole iPaaS.com record. A field the collection does not map is emptied on every update, even if another system filled it, and so is a field whose mapping you remove.
The default templates leave these iPaaS.com fields unmapped:
Add/Update Jobber Client TO iPaaS.com: none; every customer field is mapped.
Add/Update Jobber Client Billing Address TO iPaaS.com: Address3, Company, FirstName, LastName and Type.
Add/Update Jobber Product or Service TO iPaaS.com: AllowBackorders, AllowDiscounts and InStockThreshold.
Add/Update Jobber Invoice TO iPaaS.com: ShippingAmount and TotalQty.
Add/Update Jobber Invoice Line TO iPaaS.com: DiscountAmount, DiscountPercent, EstimatedTaxAmount, OriginalUnitPrice, QtyShipped, TaxPercent and Weight.
Add/Update Jobber Invoice Payment TO iPaaS.com: none.
Add/Update Jobber Invoice Tax TO iPaaS.com: OriginalAmount.
Add/Update Jobber Invoice Address TO iPaaS.com: Address3, Company, FirstName, LastName, IsPrimaryShipping, ShipDate, ShippingAmount, ShippingMethod and ShippingMethodDescription.
Add/Update Jobber Invoice Discount TO iPaaS.com: CouponCode and DiscountMethod.
The templates already keep the values Jobber does not hold for several fields (for example Comment on the customer, IsPrimaryShipping on the billing address, and Barcode, MSRP, TaxClass and Weight on the product). Their mapping descriptions say Keep.
What this means for you: do not remove the mappings marked Keep. If another system fills one of the unmapped fields above, subscribers or their MiSP should keep its value with a Dynamic Formula mapping that reads the current iPaaS.com value, using that field's name in place of ShippingAmount:
return DestinationValue != null ? DestinationValue.ShippingAmount : null;
Add these mappings before the first load, and validate them in a staging subscription before relying on them in production.
8. Updates FROM iPaaS.com Follow iPaaS.com for Every Mapped Field
FROM iPaaS.com, an update to a Jobber client or item changes only the fields the collection maps; Jobber fields with no mapping are left alone. Each mapped field follows iPaaS.com on every transfer: an empty name or company in iPaaS.com clears it in Jobber, and a price or taxable setting changed by hand in Jobber is replaced by the product's next update. An empty email or phone leaves the client's email or phone as it is, and a changed email or phone replaces the client's primary one instead of adding a second.
What this means for you: decide which system owns each field. Keep mapped fields complete in iPaaS.com, or remove the mapping for a field Jobber staff maintain by hand. Billing address parts behave differently (see section 9).
9. Empty or Unmapped Billing Address Parts FROM iPaaS.com Clear Jobber's Value
Each update from Add/Update Jobber Client Billing Address FROM iPaaS.com 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 address line that staff entered in Jobber is cleared when the iPaaS.com address has none. Removing a mapping does not hand that part over to Jobber.
What this means for you: when Jobber staff also edit client addresses, keep a part's current Jobber value by changing its mapping to a Dynamic Formula, using that part's Jobber field name in place of Street2:
return DestinationValue != null ? DestinationValue.Street2 : null;
Validate the formula in a staging subscription before relying on it in production.
10. The Jobber Billing Address Is the First Address With a Street or City
A Jobber client has one billing address. Without a filter on Add/Update Jobber Client Billing Address FROM iPaaS.com, 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. The IsPrimaryBilling mapping does not choose the address on its own, because Jobber has no primary-billing flag. For a new client, the same address also becomes its first service property; other addresses are not added.
What this means for you: to send the customer's primary billing address instead, subscribers or their MiSP add this filter to the child collection:
return IsPrimaryBilling == true;
With the filter, a customer with no primary billing address (or one with neither a first street line nor a city) is written with no billing address and, on create, no service property. Add further service properties in Jobber by hand.
11. Only the Client's Billing Address Is Sent TO iPaaS.com
TO iPaaS.com, a client's billing address is sent; Jobber service properties and client contacts stay in Jobber. 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, because iPaaS.com keeps phone numbers on addresses. Invoices carry their billing address only, so a transaction from Jobber has no shipping or service address.
What this means for you: keep service sites and contacts in Jobber. If your workflow needs Jobber service properties or contacts in iPaaS.com, submit a feature request through your iPaaS.com partner channel describing the requirement; input like this informs future enhancement releases.
12. Jobber Details the Integration Does Not Write
FROM iPaaS.com, the integration writes the client's name, company, primary email, primary phone (always as the main number), billing address and mapped custom fields, and the item and work request fields its collections map. It does not write:
On clients: tags, a mobile or second phone number, extra email addresses, contacts, service properties after the client is created, the lead source, and the client's reminder, follow-up and review-request settings.
On products and services: quantity ranges.
On work requests: an assessment visit, the request form, the referring client, the salesperson, and the line category and cost.
Custom fields: Jobber area (length by width) custom fields.
What this means for you: manage these details in Jobber. Because the client's reminder, follow-up and review-request settings are never changed by the integration, set them in Jobber. If your workflow needs one of these written from iPaaS.com, submit a feature request through your iPaaS.com partner channel; input like this informs future enhancement releases.
13. Order Custom Fields Are Not Written to Work Requests
Jobber's work requests accept no custom fields from apps, so iPaaS.com order custom fields are not written to Jobber work requests. Custom fields are supported on clients and on products and services in both directions, and on invoices TO iPaaS.com.
What this means for you: carry the values your team needs in the work request's title or note, which the Title and Note mappings on Add/Update Jobber Request FROM iPaaS.com build from the order.
14. Work Requests Are Written Once, Then Updated by Title Only
An order sent FROM iPaaS.com creates one Jobber work request, with its lines, property and note. With the transaction/updated event turned on, a later change to the order updates only the request's title: lines added or changed afterwards, address changes and the note are not sent again, and cancelling or deleting the order does not archive the request. The property is chosen only when the request is created.
What this means for you: edit or archive the work request in Jobber by hand after it is created.
15. Payments Are Recorded in Jobber
Payments recorded on a Jobber invoice are sent TO iPaaS.com with the invoice, with their amount and the payment method your translation names (see section 17). Payments recorded in another system are not written to Jobber and do not mark the Jobber invoice paid, because Jobber does not let apps record invoice payments. Jobber's bookkeeping entries on an invoice (a void, a bad-debt write-off, a correction) are not payments and are not sent; the invoice's status carries them. A refund, and a Jobber Payments bank payment that failed, are sent as negative payments, and a deposit applied to the invoice is sent as a payment.
What this means for you: record each payment in Jobber; it then reaches iPaaS.com with the invoice. Validate refunds, failed bank payments and deposits on one invoice in a staging subscription before relying on them in production. If your workflow needs payments written back to Jobber, submit a feature request through your iPaaS.com partner channel; input like this informs future enhancement releases.
16. Payment Dates Do Not Reach iPaaS.com
iPaaS.com transaction payments have no date field, so the date a payment was recorded in Jobber does not reach iPaaS.com.
What this means for you: use the invoice's dates in iPaaS.com, or look up the payment date in Jobber, when a receiving system needs it.
17. The Payment Method Translation Must Name Your Payment Methods
The Jobber Payment Type TO iPaaS.com translation turns each Jobber payment type (cash, check, credit card, Jobber Payments, bank transfer and others) into an iPaaS.com Payment Method. The template ships example values, which may not match the Payment Methods your iPaaS.com company uses.
What this means for you: before the first invoice with a payment is sent, subscribers or their MiSP open the translation under Mappings → Translations and set every entry to one of your own iPaaS.com Payment Methods (see Placeholder Values to Replace Before Go-Live).
18. Jobber Items Have No SKU
Jobber products and services have no SKU field. When an item is first sent TO iPaaS.com, its name becomes the product's SKU, and the SKU stays the same if the item is renamed later. FROM iPaaS.com, the SKU stays on the iPaaS.com product and is not written to Jobber. iPaaS.com allows one product per SKU, so an item whose name is already another iPaaS.com product's SKU is refused as a duplicate SKU in Dashboard / Integration Monitoring / Error Logs.
What this means for you: to use a different SKU scheme, change the Sku formula on Add/Update Jobber Product or Service TO iPaaS.com before the first item is sent. Invoice lines find their products by these SKUs. If an item is refused as a duplicate SKU, rename the item in Jobber or change the other product's SKU, then send the item again.
19. Product Status Follows Jobber Visibility
TO iPaaS.com, an item shown in Jobber makes its product Active, and hiding it makes the product Disabled. 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. An item hidden before it was ever sent is not sent at all.
FROM iPaaS.com, a Jobber item is shown while its product's status is Active or Preorder and hidden otherwise. A new item for a product with another status is created and then hidden straight away, so it never appears on quotes.
What this means for you: set product status in the system that owns your products. To keep an item off Jobber's lists, set its iPaaS.com product's status to Disabled or Discontinued.
Note: if Jobber refuses to hide a new item, the transfer stops with JOBR-VALD-1001 after the item was already created. Set the Collision Handling Method on Add/Update Jobber Product or Service FROM iPaaS.com to Update and Link and resend the product: the item is then linked.
20. Item Cost and Stock Are Not Sent
iPaaS.com products have no cost field, so a Jobber item's internal cost is not sent TO iPaaS.com and no cost is written to Jobber FROM iPaaS.com. Jobber holds no inventory and its items have no variants, so no stock levels or variants move in either direction. Prices are sent in both directions.
What this means for you: keep costs, markups and inventory in your ERP, point of sale or Jobber.
21. Invoice Lines Use the Fallback Line SKU When Their Item Is Not in iPaaS.com
Every line on an iPaaS.com transaction needs a product. A one-off line (typed on the invoice, with no saved Jobber item) always uses the product named in the Fallback Line SKU setting. A line whose Jobber item is not in iPaaS.com is sent first through Add/Update Jobber Product or Service TO iPaaS.com; when that item cannot be sent (it was hidden before it was ever sent, the collection's filter leaves it out, or its own transfer failed), the line arrives under the Fallback Line SKU product. If Fallback Line SKU is empty, such an invoice stops with JOBR-VALD-1013.
What this means for you: before sending invoices, create or pick an iPaaS.com product for one-off lines (for example one with SKU MISC-SERVICE) and enter its SKU in Fallback Line SKU. If a line shows the fallback product although it has a Jobber item, check that Add/Update Jobber Product or Service TO iPaaS.com 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 its own transfer failed, fix that error. Then resend the invoice.
22. Tax Group Amounts Are Calculated
Jobber gives apps an invoice's total tax, not the amount for each rate in a tax group, so the amount on each tax record of a group is calculated from the rates. It can differ by a cent from the per-rate figure Jobber shows; the total always matches.
What this means for you: reconcile tax by the invoice total. If a receiving system needs the exact per-rate amounts, take them from Jobber.
23. Invoice Numbers Must Be Unique Across Your iPaaS.com Company
iPaaS.com transaction numbers must be unique across your whole company, and Jobber numbers each account's invoices 1, 2, 3 and so on. An invoice whose number another iPaaS.com transaction already holds, for example one another system sent, is refused with "Duplicate transaction found!" in Dashboard / Integration Monitoring / Error Logs, is not linked, and each retry is refused the same way.
What this means for you: if another system also sends plain numbers, change the TransactionNumber mapping on Add/Update Jobber Invoice TO iPaaS.com to a Dynamic Formula that adds a prefix no other system uses, before the first invoice is sent:
return "JOB-" + InvoiceNumber;
Choose the formula before the first invoice and keep it afterwards. iPaaS.com checks that a transaction number is unique only when the transaction is created, not when it is updated. A later change renumbers each transaction the next time its invoice is sent, so old and new numbers are mixed in iPaaS.com, and a renumbered transaction can end up with the same number as another transaction.
24. Clients TO iPaaS.com Are Matched to Existing Customers by Email
iPaaS.com allows one customer per email address. A Jobber client (or a lead that has an invoice) with no link to an iPaaS.com customer is linked automatically to the existing iPaaS.com customer with the same email, and that customer and its primary billing address (or its first address when none is marked primary billing) are then updated with the client's values from Jobber. This matching is built in and does not depend on a Collision Handling Method.
What this means for you: if another system owns the customer record, check the mappings on Add/Update Jobber Client TO iPaaS.com before the first load, and keep the values that system fills (see section 7). If two Jobber clients share an email, keep only one of them in Jobber, or give each its own email, before they are sent.
25. Leads Are Sent Once They Have an Invoice
Jobber leads (prospects who have not bought yet) are skipped by the default filter on Add/Update Jobber Client TO iPaaS.com until they have an invoice, so accounting, point-of-sale and payment systems receive no prospects. A lead with an invoice is sent, because its invoices need their customer in iPaaS.com.
What this means for you: keep the default filter. A lead is sent as soon as it has an invoice, since the invoice sends its client first.
26. Clients Without an Email Address Are Not Sent
iPaaS.com customers need an email address. A Jobber client with no email is not sent, and neither are its invoices: both stop with JOBR-VALD-1016, naming the client. The client's own error is raised before the collection filter, so editing the Client TO iPaaS.com filter cannot silence it. A lead with no invoice is skipped by the default filter instead and raises no error.
What this means for you: add an email address to the client in Jobber; the client's next change sends it, or run a Manual Sync for the client. Invoices that already stopped with JOBR-VALD-1016 are not retried on their own: resend each one with a Manual Sync, using the number at the end of the invoice's Jobber web address.
27. Customers FROM iPaaS.com Need a Name
Jobber needs a first name, last name or company name to create a client. The default filter on Add/Update Jobber Client FROM iPaaS.com sends only customers with both a first and a last name, or a company name; others are skipped with no error. A customer that reaches Jobber with no name and no company stops with JOBR-VALD-1006.
What this means for you: give the customer a name or a company in the source system. Keep the name-or-company condition if you edit the filter.
28. The FROM iPaaS.com Collections Start With No Collision Handling Method
Templates cannot carry a Collision Handling Method, so Add/Update Jobber Client FROM iPaaS.com and Add/Update Jobber Product or Service FROM iPaaS.com start with none set. With no method, or with Error, the integration does not look for an existing Jobber record. Jobber accepts two clients with the same email, so a customer whose email a Jobber client already has creates a second client; Jobber refuses a second item with the same name, so a product named like an existing item stops with JOBR-VALD-1001.
What this means for you: set the Collision Handling Method on both collections to Update and Link after subscribing. The existing Jobber client (matched by email) or item (matched by name) is then linked and updated instead of duplicated.
29. Custom Fields FROM iPaaS.com That Jobber Doesn't Have Are Created as Text Fields
When an iPaaS.com custom field is mapped FROM iPaaS.com and Jobber has no custom field with that name for clients or for products and services, the integration creates one in Jobber as a text field, the first time a non-empty value arrives. Fields on products and services are created read-only (the integration still writes them), and an item custom field the integration created cannot be archived in Jobber afterwards. A value Jobber refuses for its field (for example text in a number field) is skipped with no error, and the record's other values are still written.
What this means for you: check each mapped custom field name before the first transfer. If the field should be a number, true/false or dropdown in Jobber, create it there first with exactly the mapped name.
30. A Product Named Like a Hidden Jobber Item Is Refused
Jobber item names are unique, hidden items included, but Jobber's search does not return hidden items. An iPaaS.com product sent to Jobber with the name of a hidden item can't be matched to it, and Jobber refuses a second item with that name: the transfer stops with JOBR-VALD-1001, "A product or service already exists with that name".
What this means for you: show the item again in Jobber (it is then matched and linked), or rename one of them, then resend the product.
31. Large Invoices Are Not Sent
An invoice with more than 100 lines stops with JOBR-VALD-1009, and one with more than 50 payment records stops with JOBR-VALD-1014. Jobber's bookkeeping entries on the invoice count towards the 50.
What this means for you: enter that invoice in the receiving system by hand.
32. Addresses, Lines, Payments, Taxes and Discounts Move With Their Parent
A client's billing address moves with its client, and an invoice's lines, payments, taxes, address and discount move with their invoice. None of them can be sent on its own, and a collection that tries to send one on its own stops with JOBR-VALD-1017.
What this means for you: to resend a child record, resend its client or invoice with a Manual Sync. Keep the default child collections in place.
33. Collections of One Type Need Filters With No Record in Common
When you add a second collection of the same type and direction, every collection whose filter matches a record runs. TO iPaaS.com each one replaces the whole record, and FROM iPaaS.com two Request collections would each create their own work request for the same order.
What this means for you: give every collection of one type and direction a filter that matches none of the records the others match, and test each filter in a staging subscription before relying on it in production.
34. Records Written FROM iPaaS.com Come Back Once, and Other Integrations Can Loop
A client or item written FROM iPaaS.com is sent back TO iPaaS.com once by the Jobber events, as an ordinary update that repeats the same values: one extra transfer per write, which does not repeat within the Jobber subscription. Work requests are not sent back. Another integration on your company that passes its own changes back the same way, and that shares the same customers or products through open filters and active events, can pass a change back and forth with Jobber repeatedly.
What this means for you: before turning on automatic transfers in more than one integration, give each system a clear role for each kind of record, and use the collection filters so each system sends only the records it owns. Watch Dashboard / Integration Monitoring / Error Logs and the transfer counts during the first days after go-live.
35. One Side per Sale
The integration does not know whether a sale already reached your ERP or accounting system from an online store or point of sale. If it did, sending the matching Jobber invoice there too records the sale twice.
What this means for you: decide which system sends each kind of sale to the ERP, and send it from that side only.
36. Several Jobber Accounts and Franchises
Each Jobber account needs its own subscription: connect each Jobber account to only one iPaaS.com subscription. There are two ways to set up several Jobber accounts, for example franchise territories:
Each account in its own iPaaS.com company. Nothing is shared between companies: records, email matching and FROM iPaaS.com collections stay inside each company. If several companies send invoices to one head-office ERP, every Jobber account numbers its invoices from 1, so give each one's invoice numbers their own prefix.
Several Jobber subscriptions in one iPaaS.com company (a roll-up). iPaaS.com shares customers and products across the company. A client who uses the same email in two territories becomes one iPaaS.com customer, and a new customer from one territory reaches every subscription that has Add/Update Jobber Client FROM iPaaS.com on, and becomes a client in that territory's Jobber too. Invoice numbers from different accounts clash. An item whose name another territory's item already holds as a product SKU is refused as a duplicate SKU, and that territory's invoice lines for it then use the Fallback Line SKU product.
What this means for you: for a roll-up in one company, keep the FROM iPaaS.com collections off on territory subscriptions that should not receive every customer, and before the first load give each territory's invoice numbers their own prefix (for example "T1-" + InvoiceNumber) and each territory's new item SKUs their own prefix with the Sku formula on Add/Update Jobber Product or Service TO iPaaS.com.
37. Turn On Jobber Events One at a Time
When several Jobber events are turned on or off together, the integration can lose track of some of the registrations it makes in your Jobber account. A lost registration keeps delivering its event to iPaaS.com after the event is turned off, and turning that event on or off again can fail with JOBR-VALD-1001 (for example "Should only have one hook of that topic per account per url" or "Could not delete webhook").
What this means for you: under Inbound Data Flows, turn the Jobber events (CLIENT_CREATE, CLIENT_UPDATE, INVOICE_CREATE, INVOICE_UPDATE, PRODUCT_OR_SERVICE_CREATE, PRODUCT_OR_SERVICE_UPDATE) on, or off, one at a time rather than together. If an event keeps arriving after you turned it off, or turning one on or off fails with JOBR-VALD-1001, contact your MiSP or iPaaS.com Support.
38. A Transfer Can Fail Once Around the Hourly Sign-In Renewal
The integration's access to your Jobber account is renewed automatically about once an hour. When two transfers need that renewal at the same moment, Jobber can turn the second one away, and that transfer stops with JOBR-AUTH-1005 ("Jobber's token endpoint answered HTTP 503"). iPaaS.com retries the transfer automatically, the retry completes, and the connection keeps working.
What this means for you: no action is needed when a single JOBR-AUTH-1005 appears in Dashboard / Integration Monitoring / Error Logs and the record's retry completed. If JOBR-AUTH-1005 keeps appearing for the same record, check Jobber's status page and click Authenticate on the subscription again.
Placeholder Values to Replace Before Go-Live
The default templates ship these values, which subscribers or their MiSP must replace during implementation.
Defaults in Add/Update Jobber Product or Service FROM iPaaS.com
Mapping filter (service SKU prefix)
Collection: Add/Update Jobber Product or Service FROM iPaaS.com
Shipped default: the filter compares each product's SKU with the text REPLACE with your service SKU prefix.
Why it's a placeholder: only you know which SKU prefix marks the service and labor products that belong in Jobber. Until the text is replaced, no product matches, so nothing is sent to Jobber.
Suggested action: open Mappings → Mapping Collections, open this collection, and replace the text with the prefix your service and labor products share, for example SVC-, keeping the quotation marks.
Defaults in Add/Update Jobber Request FROM iPaaS.com
Mapping filter (service SKU prefix)
Collection: Add/Update Jobber Request FROM iPaaS.com
Shipped default: the filter sends an order only when one of its lines has a SKU that starts with REPLACE with your service SKU prefix.
Why it's a placeholder: the prefix marks the orders that include service work. Until the text is replaced, no order is sent.
Suggested action: replace the text with the same service SKU prefix, for example SVC-, keeping the quotation marks. The comparison is case-sensitive and checks the start of the SKU only.
Defaults in Add/Update Jobber Invoice Payment TO iPaaS.com
Jobber Payment Type TO iPaaS.com (Lookup Translation)
Collection: Add/Update Jobber Invoice Payment TO iPaaS.com
Shipped default: example Payment Method names, such as CASH, CHECK, CRCARD, Online payment and Other, for the 15 Jobber payment types.
Why it's a placeholder: each iPaaS.com company names its own Payment Methods, so the example names may not exist in yours, and the systems that receive the transaction need a method they recognize.
Suggested action: before the first invoice with a payment is sent, open the translation under Mappings → Translations and set every entry to one of your own iPaaS.com Payment Methods. Check one invoice with a payment in a staging subscription before relying on it in production.
This document covers the thirty-eight known limitations of this integration plus the three pre-go-live placeholder values above. For detailed technical documentation on individual mapping collections, refer to the Jobber mapping collection descriptions and the Jobber mapping documentation articles.
