Integrate iPaaS.com with Jobber to enable seamless data synchronization for clients and their billing addresses, products and services, invoices (with their lines, payments, taxes, addresses and discounts), and work requests. This article is the ongoing reference for how the subscription connects to Jobber and what each setting does: use it when you review a setting, authorize again, or move the subscription to another Jobber account. First-time setup is covered step by step in the Jobber Installation Instructions.
How to Connect
Prerequisites
A Jobber account, and a Jobber login with admin access to it. Authenticate with the account owner's login or another admin login. If you are not sure which login is an admin, ask your Jobber account owner.
No app or keys to create in Jobber. iPaaS.com's own Jobber app is used for every subscription. You only allow it access to your Jobber account.
One Jobber account per subscription. 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.
For invoices: an iPaaS.com product to stand for invoice lines that are not saved products in Jobber. Its SKU goes in the Fallback Line SKU setting below.
Configuration Details
The connection needs no credentials typed into iPaaS.com. You provide:
Jobber admin login: the Jobber login you sign in with when you click Authenticate. It must be an admin of the Jobber account you want to connect. Example: the login of your Jobber account owner.
Allow Access: the button on Jobber's consent page that grants the iPaaS.com app access to your Jobber account. Check that the page names the iPaaS.com app before you click it.
API Url: the address of Jobber's API. A new subscription's box starts empty: type the address below. Example: https://api.getjobber.com/api/graphql
Configure Subscription Settings
Open the Jobber subscription in iPaaS.com and open its Settings. After you change a value, click Apply. A change can take about a minute to reach the next transfer or poll.
Field | Description | Required | Example |
API Url | The address of Jobber's API. Enter | Yes | |
Fallback Line SKU | The SKU of the iPaaS.com product used for invoice lines that have no iPaaS.com product of their own, such as one-off lines typed on a Jobber invoice. When it is empty, an invoice with such a line stops with JOBR-VALD-1013. The integration does not check that the SKU exists: an unknown SKU is refused by iPaaS.com with an error naming the SKU. | Conditional: required if you send invoices TO iPaaS.com | MISC-SERVICE |
Customer Poll Days | How many days back the first client poll (CLIENT_POLL) looks. Default 7. Zero or a negative number also uses 7. | No | 7 |
Customer Page Size | How many clients each client poll asks Jobber for at a time. Default 50. A value over 100 acts as 100. | No | 50 |
Transaction Poll Days | How many days back the first invoice poll (INVOICE_POLL) looks. Default 7. Zero or a negative number also uses 7. | No | 7 |
Transaction Page Size | How many invoices each invoice poll asks Jobber for at a time. Default 50. A value over 100 acts as 100. | No | 50 |
Product Page Size | How many products and services each product poll (PRODUCT_OR_SERVICE_POLL) asks Jobber for at a time. Default 100. A value over 100 acts as 100. | No | 100 |
Poll Days settings. Each poll after the first carries on from where the last one stopped. If you change a Poll Days setting after the first poll has run, the next poll looks back the new number of days once, then carries on from where it stopped. A change only ever widens a poll: a smaller number never makes it skip changes. To load older history on the first poll, raise the value before the first poll runs. iPaaS.com saves an empty Poll Days box as the default 7 and refuses text.
Page Size settings. These only set how many records each poll asks Jobber for at a time; every page is read, so they do not limit how many records a poll sends. Leave the defaults.
Authentication Methods
The integration signs in to Jobber with Jobber's OAuth 2.0 authorization, using iPaaS.com's Jobber app. You never handle a password, key or token for it.
Authenticate the subscription
Error messages call this action Authorize; it is the Authenticate action on the subscription.
Open the Jobber subscription's Subscription Settings page in iPaaS.com and click the Authenticate action (the lock icon at the top right).
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. The integration exchanges Jobber's one-time authorization code for the subscription's sign-in and records which Jobber account was authorized.
Start authorization from iPaaS.com. Opening the iPaaS.com app from Connected apps in your Jobber account does not connect a subscription.
If Jobber shows an error instead of Allow Access, or you decline access, the authorization stops with an error asking you to click Authenticate again (JOBR-AUTH-1008). If Jobber refuses the authorization code, for example because the return to iPaaS.com was delayed, click Authenticate again and complete it within 10 minutes (JOBR-AUTH-1010).
How the sign-in stays current
The integration uses a short-lived access token for every call to Jobber and renews it automatically a few minutes before it expires. No action is needed from subscribers or their MiSP.
Jobber issues a new renewal token each time the sign-in is renewed, and the old one stops working (Jobber refresh token rotation). If two transfers renew at the same moment, one of them can fail briefly with JOBR-AUTH-1005 and is retried automatically. If Jobber refuses a renewal once, the transfer is retried automatically (JOBR-AUTH-1011); if it is refused again within 10 minutes, the error asks you to authorize again (JOBR-AUTH-1003).
When to click Authenticate again
Click Authenticate again (steps above), then resend the failed records, when any of these happens:
Transfers fail with JOBR-AUTH-1002, JOBR-AUTH-1003, JOBR-AUTH-1004 or JOBR-AUTH-1006 in Dashboard / Integration Monitoring / Error Logs (the subscription is not, or no longer, connected to Jobber).
iPaaS.com was disconnected from your Jobber account in Jobber's settings for connected apps.
The same Jobber account was authorized on another iPaaS.com subscription.
If transfers fail with JOBR-AUTH-1001 or JOBR-AUTH-1007, the problem is with iPaaS.com's Jobber app and authorizing again does not help: contact iPaaS.com Support. JOBR-AUTH-1005 means Jobber's sign-in service is having trouble: the records are retried, and no action is needed unless it persists.
When every transfer fails with only "Unable to connect to subscription", the coded reason (for example JOBR-VALD-1015 or one of the codes above) is in the iPaaS.com Logs entry with the same time and reference id. The Jobber Error Messages article lists every code and its resolution.
Switching to another Jobber account
To connect the subscription to a different Jobber account:
In the subscription configuration's Inbound Data Flows section, turn off the Jobber events (CLIENT_CREATE, CLIENT_UPDATE, INVOICE_CREATE, INVOICE_UPDATE, PRODUCT_OR_SERVICE_CREATE, PRODUCT_OR_SERVICE_UPDATE), one at a time. This removes the subscription's registrations from the old Jobber account.
Click Authenticate and sign in with an admin login of the new Jobber account.
Turn the Jobber events back on, one at a time. Each is registered with the new account.
After the switch, check that changes made in the new Jobber account arrive in iPaaS.com, and send any existing records you need with a Manual Sync. Validate the switch in a staging subscription before relying on it in production.
Jobber events and the Webhook API Key
When you turn on a Jobber event, iPaaS.com registers it with your Jobber account at an address unique to this subscription, which carries the subscription's Webhook API Key. Jobber sends each change to that address, and iPaaS.com refuses any delivery without the right key. Turn Jobber events on or off one at a time, letting each finish before the next: turning several on at once can lose a registration.
If the subscription's Webhook API Key is regenerated in iPaaS.com, the registrations made with the old key stop reaching iPaaS.com. Turning each Jobber event off and on again, one at a time, registers it again with the new key. Validate this in a staging subscription before relying on it in production.
Initialization Support
Currently, initialization is not supported for Jobber in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Load existing Jobber records with the poll scopes instead:
Clients and invoices: CLIENT_POLL and INVOICE_POLL send the records changed within Customer Poll Days and Transaction Poll Days on their first run. Set those values wide enough before the first poll runs.
Products and services: PRODUCT_OR_SERVICE_POLL sends every visible product and service each time it runs, not only the ones that changed. Run it once to load your items, then turn it off.
To send a large set of iPaaS.com records to Jobber, use bulk sync using Postman.
Throttling
Throttling keeps the integration within the limits Jobber sets on how many requests, and how much query cost, an app can use on a Jobber account over time. For Jobber's current figures, see Jobber API rate limits.
The throttle fields on the subscription are pre-populated when the subscription is created and do not normally need to be changed. For what each field does, see Subscription Configuration – Edit.
Field | Default |
API Throttle Limit | 500 |
API Throttle Seconds | 60 |
API Throttle Limit (To iPaaS) | 500 |
API Throttle Seconds (To iPaaS) | 60 |
Concurrent Connections | 2 |
Concurrent Batch Executions | 10 |
The integration also asks Jobber for records a page at a time (see the Page Size settings above: 50 clients, 50 invoices and 100 products and services by default) to keep each request's cost small. When Jobber reports a limit reached, the transfer is handed back to iPaaS.com and retried later (JOBR-EXTN-1003); no records are lost and no action is needed. If these retries appear often, subscribers or their MiSP can lower API Throttle Limit or Concurrent Connections.
Related Documents


