Yes. Krokul CRM integrates with Jobber. A deal won in Krokul creates the client and the job in Jobber, quotes sent and approved in Jobber move the deal through the pipeline, and payments on Jobber invoices are recorded on the deal. The sales team keeps contracts and receivables in Krokul while crews work from Jobber.
Automation platformsZapierMake
A property management company signs a seasonal contract, and the deal is marked won. Krokul calls the clientCreate mutation with the company name, the billing address and the main contact e-mail, adds the service address as a Property, and creates the Job for the first visit. Jobber names Krokul as the client source. The Jobber client ID goes into an external key on the client company.
Field staff often price extra work on site. When Jobber reports Quote Sent, Krokul moves the matching deal to the proposal stage with the quote total, and Quote Approved moves it to won. A quote for a client without a deal opens a new deal for the account manager.
New Invoice Created adds an invoice document to the deal with the amount and due date. A payment applied in Jobber fires Invoice Updated, and Krokul reads the invoice balance and records the difference as a payment. Jobber can send that update twice, so Krokul ignores a repeat with the same invoice and balance. Unpaid invoices appear in the Krokul debtor list.
Job Closed creates a task for the deal owner to confirm the result with the client and offer the next service period. The task links to the Jobber job number.
| Jobber | Direction | Krokul | When |
|---|---|---|---|
| Client (clientCreate, New Client Created, Client Updated) | Krokul ↔ Jobber | Client company with its main contact | A client is created or edited on either side |
| Property | Krokul → Jobber | Service address of the client company | A deal with a new site is won |
| Job | Krokul → Jobber | Won deal | A deal is won in a service pipeline |
| Request (New Request Created) | Jobber → Krokul | New deal with the request details | A client asks for work in Jobber |
| Quote (Quote Sent, Quote Approved) | Jobber → Krokul | Deal stage and amount | A quote is sent or approved |
| Invoice (New Invoice Created) | Jobber → Krokul | Invoice document on the deal | An invoice is created |
| Invoice payment (Invoice Updated) | Jobber → Krokul | Payment on the deal | A payment is applied to an invoice |
| Job Closed | Jobber → Krokul | Task for the deal owner | The job is closed |
Yes. Krokul integrates with Jobber through the Krokul app in Zapier and Make and through the Krokul API and webhooks together with the Jobber GraphQL API.
The Jobber invoice. When a payment is applied, the invoice update tells Krokul the new balance, and Krokul records the paid amount on the deal.
An admin of the Jobber account. Jobber uses OAuth, so the admin signs in and grants the scopes the app requests.
Yes. A new request in Jobber opens a deal in Krokul for that client company, so larger jobs get a manager and a proposal.
Visits, crew schedules, routes and the client hub stay in Jobber. Jobber connects apps through OAuth, and a private integration in Draft state can serve up to 5 paying Jobber accounts before Jobber has to approve it.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Jobber is a trademark of Octopusapp Inc. Krokul is not affiliated with Jobber.
