This guide is for the person who sets up the Jobber integration for a business. Allow about 30 to 45 minutes: most of it is naming your payment methods, editing two filters and setting collision handling.
Before You Begin
A Jobber account, and a Jobber login with admin access to it. Jobber asks an admin to allow an app to access the account. If you are not sure which login is an admin, ask your Jobber account owner.
An iPaaS.com company where you can add subscriptions.
For invoices: one iPaaS.com product to stand for one-off invoice lines. Jobber invoices can carry lines that aren't saved products, and iPaaS.com needs a product on every line. In iPaaS.com, open Products and add a product (for example name "Miscellaneous Service", SKU "MISC-SERVICE"). Note its SKU: you enter it as the Fallback Line SKU setting below.
Every Jobber client you send needs an email address. iPaaS.com customers need one, so a Jobber client without an email is not sent, and neither are its invoices (JOBR-VALD-1016). Add the email in Jobber: the client is then sent on its next change. Invoices that already stopped are not retried, so resend each one (see Additional Notes).
One Jobber account, one subscription. Connect each Jobber account to only one iPaaS.com subscription.
You don't create any app or keys in Jobber yourself: iPaaS.com's Jobber app does that work. You only allow it access to your account.
Installation Instructions for Integration Setup
In the left navigation, expand Subscriptions Management and click Subscriptions, then click Search Certified Integration Marketplace & Subscribe. (You can also click Marketplace under Subscriptions Management.)
Click the Jobber tile, then click Subscribe.
The Subscription Settings page opens. Fill in the fields:
Name: a unique subscription name.
Format: [Product Name] - [Environment/Purpose]
Example: Jobber - Production
Versions: leave the version selected.
Create Default Mappings: leave it checked. It creates the Jobber mapping collections, which you switch on or off later. If you uncheck it, no mapping collections are created and you must build them yourself.
API Url: enter
https://api.getjobber.com/api/graphql. The box starts empty and is required. Jobber uses this one address for every account; there is no separate test address.Fallback Line SKU: required if you send invoices. The SKU of the iPaaS.com product for one-off invoice lines (see Before You Begin).
Customer Poll Days and Transaction Poll Days: how many days back the first client and invoice checks look. Enter 7, or more for a first load of older records.
Customer Page Size and Transaction Page Size: enter 50. Product Page Size: enter 100.
API Throttle Limit (500), API Throttle Limit (to iPaaS) (500), API Throttle Seconds (60), API Throttle Seconds (to iPaaS) (60), Concurrent Batch Executions (10) and Concurrent Connections (2): these are filled in for you. Leave them as they are.
NOTE: The throttle and concurrency settings control how often and how much data moves. Lower API Throttle Limit or Concurrent Connections only if you see frequent rate-limit retries. Each setting is described in Jobber Connections and Settings.
Click Apply.
Authentication Configuration
Jobber uses OAuth 2.0: you sign in to Jobber once and allow the iPaaS.com app access. You never type a password, key or token into iPaaS.com.
Credential: your Jobber admin login.
Location: the Jobber sign-in page that opens from the subscription's Authenticate action.
Description: grants the iPaaS.com Jobber app access to your Jobber account.
Open the Jobber subscription's Subscription Settings page and click the Authenticate action (the lock icon at the top right). Save any changes with Apply first.
A Jobber page opens. Sign in with your Jobber admin login if asked.
Check that the page names the iPaaS.com app, then click Allow Access.
You return to iPaaS.com. Refresh the subscription's Subscription Settings page: below the settings, the saved values now include Jobber Account Name, showing your Jobber account's name.
Important Notes
If Jobber shows an error instead of Allow Access, note its exact words and contact your MiSP, or iPaaS.com Support (support@ipaas.com).
If iPaaS.com is later disconnected from your Jobber account (in Jobber's settings for connected apps), click Authenticate again to reconnect.
Connect each Jobber account to only one iPaaS.com subscription. Authorizing the same Jobber account on a second subscription (for example a test one) can disconnect the first, which then fails with JOBR-AUTH-1003. To move to a new subscription, turn the old one's Jobber events off first (see Turn on the triggers).
Error messages call this step Authorize; it is the Authenticate action.
Operational Configuration
You set these in step 3 of the setup. Each is described in Jobber Connections and Settings.
Setting | What to enter |
API Url |
|
Fallback Line SKU | Required if you send invoices. The SKU of the iPaaS.com product used for one-off invoice lines. |
Customer Poll Days | How many days back the first client check looks (default 7). Raise it for a first load of older clients. |
Customer Page Size | 50 (the default). |
Transaction Poll Days | How many days back the first invoice check looks (default 7). Raise it for a first load of older invoices. |
Transaction Page Size | 50 (the default). |
Product Page Size | 100 (the default). |
If you change a Poll Days setting after the first check has run, the next check looks back the new number of days once, then carries on from where it stopped. A change only ever widens a check: a smaller number never makes it skip changes.
Additional Configuration Options
Choose what moves
Each mapping collection is one kind of record moving one way. To use one, open it under Mappings → Mapping Collections and make sure it is active (as the portal shows it); records then move once its triggers are on (see Turn on the triggers). Switch on the ones your business needs:
Collection | What it does |
Add/Update Jobber Client TO iPaaS.com | New and changed Jobber clients become iPaaS.com customers. Leads (prospects) are left out until they have an invoice. A client with no email address is not sent (JOBR-VALD-1016). |
Add/Update Jobber Product or Service TO iPaaS.com | Jobber's products and services become iPaaS.com products. Turn this on before invoices, so invoice lines find their products. |
Add/Update Jobber Invoice TO iPaaS.com | Issued Jobber invoices, with their lines, tax, discount and the payments recorded on them in Jobber, become iPaaS.com transactions. |
Add/Update Jobber Client FROM iPaaS.com | Customers from your other systems become Jobber clients. Set its collision handling first (below). |
Add/Update Jobber Product or Service FROM iPaaS.com | Service and labor items from your other systems become Jobber products and services. Edit its filter first (see "Editing a filter" below). Until you do, no product is sent. |
Add/Update Jobber Request FROM iPaaS.com | Orders from your other systems that need work become Jobber work requests. Edit its filter first (see "Editing a filter" below): only orders with a line whose SKU starts with your prefix become requests; until you edit it, no order is sent. An order's customer is sent to Jobber first, so also turn on Add/Update Jobber Client FROM iPaaS.com, with collision handling set to Update and Link (below); without it the order stops with JOBR-VALD-1011. |
Updates replace the whole record on iPaaS.com. Each time a Jobber client, item or invoice is sent TO iPaaS.com, it replaces the whole iPaaS.com record. If you remove a mapping from a TO iPaaS.com collection, that field is emptied on iPaaS.com at the record's next update. Mappings marked Keep in their description protect values your other systems set; don't remove them.
Editing a filter (Product or Service FROM and Request FROM).
Open Mappings → Mapping Collections, then Add/Update Jobber Product or Service FROM iPaaS.com (or Add/Update Jobber Request FROM iPaaS.com), and open its Filter (as the portal shows it). The filter is a short line of code.
Find the words
REPLACE with your service SKU prefixbetween quotation marks. Replace only those words with the start your service items' SKUs share, keep the quotation marks, and match capital letters exactly (the match is case-sensitive). For example:StartsWith("SVC-"). Save.If your service items don't share a SKU start, don't delete the filter (that sends everything). Ask your MiSP, or iPaaS.com Support (support@ipaas.com), for help.
You can check the filter only once its iPaaS.com events are on: see "Check an edited filter" under Turn on the triggers.
Name your payment methods (invoices with payments). Open the Jobber Payment Type TO iPaaS.com translation under Mappings → Translations. Each row turns a Jobber payment type (cash, check, credit card, Jobber Payments and so on) into one of your iPaaS.com Payment Methods. Replace every "REPLACE with your iPaaS.com … Payment Method name" value with the exact name of one of your iPaaS.com Payment Methods. If a method you need doesn't exist in iPaaS.com yet, create it there first. Do this before any invoice with a payment is sent.
Invoice numbers must be unique in your iPaaS.com company. Jobber numbers invoices 1, 2, 3 and so on. If another system also sends plain numbers TO iPaaS.com, give Jobber's numbers a prefix before the first invoice is sent: open Add/Update Jobber Invoice TO iPaaS.com, open the TransactionNumber mapping, change its type to a formula (Dynamic Formula, as the portal shows it), enter return "JOB-" + InvoiceNumber; and save. Otherwise an invoice whose number is already taken is refused. Don't change the prefix after invoices have been sent: iPaaS.com checks that a number is unique only when a transaction is created, so renumbering on update can give two transactions the same number.
If the same sale reaches your accounting or ERP system from your online store or point of sale, don't also send the matching Jobber invoice there. Let the books take each sale from one side.
Set collision handling on the two FROM collections you use. Collision handling is not copied from the templates, so it starts at Error. Open each collection below under Mappings, set Collision Handling to Update and Link, and save:
Collection | Set collision handling to | What it matches on | Why |
Add/Update Jobber Client FROM iPaaS.com | Update and Link | The customer's email address | At Error, the integration does not look for an existing Jobber client by email, and Jobber accepts two clients with the same email: a customer who is already a Jobber client gets a second client. With Update and Link, that customer is linked to the existing client and updates it. |
Add/Update Jobber Product or Service FROM iPaaS.com | Update and Link | The item's exact name | At Error, Jobber refuses a second item with the same name, so the transfer fails. With Update and Link, the existing Jobber item with that name is linked and updated. |
Turn on the triggers
In the subscription configuration's Inbound Data Flows section, turn on the Jobber events for the collections you use:
Clients: CLIENT_CREATE, CLIENT_UPDATE
Invoices: INVOICE_CREATE, INVOICE_UPDATE (a payment recorded on an invoice updates it)
Products and services: PRODUCT_OR_SERVICE_CREATE, PRODUCT_OR_SERVICE_UPDATE
Once you turn on the Jobber events, iPaaS.com registers them with your Jobber account, and changes made in Jobber reach iPaaS.com within moments.
For the FROM iPaaS.com collections you use, turn on the iPaaS.com events that send records to Jobber, in the Outbound Data Flows section:
Customers: customer/created, customer/updated
Products: product/created, product/updated
Orders (work requests): transaction/created, and transaction/updated if a changed order should update the request's title
Without these events nothing is sent to Jobber, and nothing errors.
Check an edited filter (Product or Service FROM and Request FROM). With the events above on, change one product whose SKU starts with your prefix in iPaaS.com (or create an order with such a line). Within a minute it appears in Jobber, under Products & Services (or Requests).
For a first load, or if events stop arriving: the poll scopes CLIENT_POLL and INVOICE_POLL send the clients and invoices changed since the last poll. For each one you need, create a scheduled event of type Webhook Poll Request for this subscription, with the poll scope (for example CLIENT_POLL), the Filter left empty (the Jobber polls don't read it), and a schedule; once a day is a sensible safety net with the Jobber events on. For a first load of history, set a larger Poll Days value before the first poll runs.
PRODUCT_OR_SERVICE_POLL sends every visible product and service each time it runs, because Jobber items carry no last-changed date, so run it only once, to load your existing items before the first invoice:
Create a scheduled Webhook Poll Request event for this subscription with the scope PRODUCT_OR_SERVICE_POLL and the Filter left empty.
Run it once, and wait until your Jobber items appear in iPaaS.com under Products.
Delete the event, or turn it off, so it doesn't run again.
Item changes after that arrive through the PRODUCT_OR_SERVICE events.
Post-Installation Verification
These test records also reach your other connected systems. A test item made in Jobber becomes an iPaaS.com product, and a test customer made in iPaaS.com is a new customer there too: every other system you connect to iPaaS.com (an ERP, an online store, a CRM, email marketing) receives it through its own collections, where it may be published or emailed. Give test records a name your other systems' filters leave out (for example starting "TEST - delete me"), use your own email address, run these checks before you switch on the other systems' collections, and delete the test records everywhere afterwards. If you can't do that, run only the Connection Test and skip the FROM iPaaS.com check.
Connection Test
Check that Jobber Account Name, among the saved values on the subscription's Subscription Settings page, shows your Jobber account's name.
In Jobber, create a test product or service (for example "TEST - delete me").
Within a minute it appears in iPaaS.com under Products, with its name as its SKU, and no JOBR-AUTH error appears in Dashboard / Integration Monitoring / Error Logs.
Delete the test item in Jobber and in iPaaS.com afterwards.
Data Sync Test
To check a FROM iPaaS.com collection, create a test customer in iPaaS.com with a first name, last name and your own email address. Within a minute it appears in Jobber under Clients. Delete it in both places afterwards.
A client you create in Jobber to test with is a lead until it has an invoice, so it does not appear in iPaaS.com on its own. That is expected.
Support and Troubleshooting
Click the Help and Support button on any iPaaS.com page to contact iPaaS.com Support at support@ipaas.com or to search our documentation. If an MiSP manages your iPaaS.com company, contact them first.
Documentation: search our documentation at the top of this article.
Support Portal: click the Help and Support button at the lower-right of this window.
Contact Information: email iPaaS.com Support at support@ipaas.com.
Jobber: check Jobber's status page when Jobber itself may be having trouble.
If every transfer fails with only "Unable to connect to subscription": open Logs in the iPaaS.com portal and find the entry with the same time and reference id as the failed transfer (the reference id is shown with the error in the failed transfer's details). It carries the integration's coded reason. Every code is described in Jobber Error Messages.
JOBR-VALD-1015: the API Url setting was changed. Set it back to
https://api.getjobber.com/api/graphql, click Apply, and resend.JOBR-AUTH-1002, 1003, 1004 or 1006: the subscription is not, or no longer, connected to Jobber. Click Authenticate again (see Authentication Configuration), then resend.
JOBR-AUTH-1001 or 1007: the problem is on iPaaS.com's side and you can't fix it yourself. Contact your MiSP, or iPaaS.com Support (support@ipaas.com).
JOBR-AUTH-1005 or JOBR-EXTN-1002: Jobber is having trouble, and the records are retried. Check Jobber's status page and wait.
JOBR-IPAS-1001: a call to iPaaS.com itself failed. It is usually temporary and retried; if it persists, contact your MiSP, or iPaaS.com Support (support@ipaas.com), with the reference id.
Additional Notes
Jobber items have no SKU. When a Jobber product or service first reaches iPaaS.com, its name becomes its SKU, and that SKU stays the same if you rename the item later.
Product status TO iPaaS.com: hiding an item in Jobber (turning off its "visible" setting) marks its iPaaS.com product Disabled, unless the product is already Discontinued; showing it again marks the product Active, unless it is already Preorder. An item hidden before it ever reached iPaaS.com is not sent, and the product poll does not see hidden items.
Product visibility FROM iPaaS.com: a Jobber item is visible while its iPaaS.com product's status is Active or Preorder, and hidden otherwise. A new item for a product with another status is created hidden. To hide an item in Jobber, set the iPaaS.com product's status to Disabled or Discontinued.
Jobber holds no stock, so no inventory moves in either direction.
Nothing this integration does sends emails or texts to your Jobber clients. Jobber sends no "Submitted request" email for the work requests the integration creates.
Jobber clients with no email address can't be sent (JOBR-VALD-1016): iPaaS.com customers need an email. Add an email to the client in Jobber; its next change sends the client. Invoices of that client that already stopped with JOBR-VALD-1016 are not retried: resend each one with a Manual Sync, entering the number at the end of the invoice's Jobber web address (for example 123456 from …/invoices/123456).
The integration never deletes records in Jobber.
Related Documents






