Jobber connector
Your Silux Chat bot verifies customers against Jobber, then answers questions about their appointments and bookings and invoices from your live data.
What your bot can do with Jobber
Appointments and bookings
Reads upcoming and recent appointments or reservations from Jobber — date and time, service and status.
Customers ask: “When is my next appointment?” · “Is my booking confirmed?”
Recognise and verify customers
Finds the customer in Jobber by the email address or mobile number they give, checks their name and one more detail, then sends a one-time code to the contact details Jobber holds. Nothing personal is shared until the code is entered.
Customers ask: “I want to check my account — it’s Jane Smith, jane@example.com”
Invoices
Reads a verified customer’s invoices from Jobber — number, date, amount and whether it is paid.
Customers ask: “Is my latest invoice paid?” · “How much was my last bill?”
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Jobber as an administrator.
Step 1 — in Jobber
Connect with Jobber (OAuth) — Silux Chat asks for read access to clients, invoices and jobs.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where Jobber lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Jobber”.
- 2Press Sign in with Jobber. The platform makes a real, read-only call to Jobber with a made-up customer and shows a tick or a cross for each capability, with Jobber’s exact error if something is refused.
- 3If this is your first way of verifying customers it is switched on automatically; otherwise press Use to verify customers. The platform then runs its chained test (verify → code → account → orders → invoices) with the built-in test customer — no real person is contacted.
There is no key to copy. You press “Sign in with Jobber”, approve read-only access on Jobber’s own page, and are returned to your dashboard. The access token is stored encrypted and refreshed automatically before it expires.
How customer verification works
- STEP 1
Customer asks
They ask about their own account. The bot asks for their full name and their email or mobile, plus one more detail such as their postcode.
- STEP 2
Found in Jobber
The customer is looked up in Jobber by email, then mobile. The surname must match exactly and the first name must match or start with the same letter, plus one more detail.
- STEP 3
Code sent
A 6-digit code goes to the mobile Jobber holds (by text, when your plan has SMS) or otherwise to the email it holds. The chat never chooses where it goes.
- STEP 4
Verified
The customer types the code. It is valid for 10 minutes and five wrong attempts cancel it. The verified session lasts 30 minutes.
If the details don’t match, the customer is told only that they couldn’t be matched — never which detail was wrong. If Jobber can’t be reached, the bot says it can’t check accounts right now rather than “no account found”. The bot is blocked in code from reading orders, invoices or bookings until verification succeeds. Full details: Customer identity verification & OTP.
What the bot can and cannot see
Can see (after verification)
- Record ID
- Name
- Email address
- Phone / mobile
- Postcode
- Balance
- Invoice number
- Date
- Amount
- Status
- Due date
- Due date
- Start time
- Service
Only these standard fields are mapped from Jobber’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Sign-in tokens encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Jobber.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Jobber’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Jobber endpoints this connector reads, relative to https://api.getjobber.com/api. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Recognise and verify customers | POST/graphql(GraphQL query) | id, name, email, phone, postcode, balance |
| Invoices | POST/graphql(GraphQL query) | invoice, date, amount, status, due, due_date |
| Appointments and bookings | POST/graphql(GraphQL query) | id, start, service, status |
Test level: Documented-API tested. Each capability is run automatically against Jobber’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The sign-in was revoked or has expired, or it lacks a read permission this connector needs. Sign in with Jobber again. |
| “Silux Chat’s Jobber app is not registered yet” | Our sign-in app with Jobber isn’t available yet; our team is notified automatically. Email support@siluxcall.co.uk for timing or alternatives. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Jobber record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Jobber, or your Jobber plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Jobber returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Jobber asks); if it persists, ask Jobber about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Jobber, or none are recent. Check the customer’s record in Jobber directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Jobber connection read-only?
Yes. Every request Silux Chat makes to Jobber is a look-up (a few vendors use POST for searches); none creates, changes or deletes anything in Jobber. Give the key or sign-in read-only permissions wherever Jobber offers them.
Do I need a developer to connect Jobber?
No. You sign in with Jobber in Dashboard → Integrations → Connectors and press “Sign in with Jobber”. The platform makes a real call to Jobber straight away and shows exactly which features work.
How does the bot know it is really my customer?
It finds the customer in Jobber by the email or mobile they give, checks their name and one more detail, then sends a one-time code to the mobile or email held in Jobber — never to one typed in the chat. The code lasts 10 minutes, five wrong attempts cancel it, and a verified session lasts 30 minutes.
What happens if my Jobber key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Jobber connector been tested?
It is Documented-API tested: every capability is run automatically against Jobber’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Jobber account before your bot uses it.
Other field service connectors
Housecall Pro
Appointments and bookings · Recognise and verify customers · Invoices
ServiceM8
Appointments and bookings · Recognise and verify customers · Invoices
ServiceTitan
Recognise and verify customers · Invoices · Support tickets and cases
simPRO
Account balance · Recognise and verify customers · Invoices · Support tickets and cases
Workiz
Appointments and bookings
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.