What makes Jobber easy or hard to automate
Jobber publishes a GraphQL API through its Developer Center, open to anyone who signs up. Clients, properties, requests, quotes, jobs, visits, invoices and payments are all reachable, and webhooks fire on events such as a new request or an approved quote. For a business automating its own account, Jobber explicitly supports custom integrations that never go to the App Marketplace and skip app review. A Zapier app covers the most common triggers and actions for people who prefer no-code.
The harder parts come from GraphQL itself. Every query has a cost in points, charged against a budget per app and account that refills gradually, and there is a separate cap on total requests in a five-minute window. Queries that ask for nested lists of visits, line items and notes add up fast. Teams used to REST also need to learn cursor pagination and how to request exactly the fields they need.
The AI layer
Jobber runs the schedule and the money. AI handles the conversations and drafting:
- Intake, where an assistant answers the first message within seconds, asks the questions your office would ask and creates a clean request.
- Quoting help, where notes and photos become draft line items from your own price list.
- Follow-up, where unanswered quotes, unpaid invoices and finished jobs each get a timely, specific message.
Owners and office staff approve prices and anything a client will see for the first time.
Limits to plan around
- Query cost. Design small queries. Fetch IDs first, then details only for records you need.
- Draft app ceiling. Custom apps are for your own account. Selling to others means publishing and review.
- OAuth tokens. A person authorizes the app once. Store and refresh tokens securely so a workflow does not quietly disconnect.
- Data you do not own. Client phone numbers and addresses carry texting consent and privacy duties. Respect opt-outs in every message workflow.
How Lumeor typically connects it
We usually run n8n with a Jobber OAuth credential, webhook triggers for requests, quotes and invoices, an LLM step for replies and drafts, and the owner approving prices in Slack or by text. Phone and text handling runs on Twilio. The home services booking agent guide and quote generation guide cover the two builds we see most. If you are comparing platforms, see Housecall Pro, and our n8n vs Zapier comparison helps decide when Zapier’s Jobber app is enough.