Jobber AI Integration
Jobber AI agents run on Bonfire Terminal, driving your field service management software via its API. From Slack or Telegram, tell on-device agents to schedule jobs, send quotes, and update clients, keeping your operations local-first and under your control.
What Bonfire can do in Jobber
Real actions from the Jobber API that a Bonfire agent can run on your behalf, on-device.
| Action | Resource | Method · Endpoint |
|---|---|---|
| List clients | Clients | POST /api/graphql |
| Create client | Clients | POST /api/graphql |
| List jobs | Jobs | POST /api/graphql |
| Create job | Jobs | POST /api/graphql |
| List quotes | Quotes | POST /api/graphql |
| List invoices | Invoices | POST /api/graphql |
| Create invoice | Invoices | POST /api/graphql |
| List requests | Requests | POST /api/graphql |
Jobber agents in action
On your machine, not a SaaS
Bonfire Terminal
- Your keys & data stay on your device
- Perpetual license — no per-seat SaaS fee
- Any connected model — Claude, GPT, Gemini or Grok
- Offline Llama for local, private reasoning
- Driven from chat you already use
Cloud AI middleman
- Keys & data pass through a third-party server
- Recurring subscription, usage caps
- Model locked to the vendor
- Yet another dashboard to log into
Jobber — questions
Can Bonfire automate Jobber?
Yes. Bonfire runs on your machine, holds your Jobber credentials locally, and a connected model (Claude, GPT, Gemini or Grok) drives the Jobber API to run the actions you ask for in chat.
Does my Jobber data go to the cloud?
Bonfire runs on your desktop and keeps your keys local — it isn't a SaaS holding your data. Only the specific request you approve is sent to your chosen AI model.
Which AI models can I use?
Any connected model — Claude, GPT, Gemini or Grok. A fully offline Llama model runs locally for private reasoning but can't reach live APIs.