Hey Rafa, great question, and I'm glad we can give you a better answer than we could when you first posted.
You mentioned that Claude is your main AI tool and that the missing native Jobber integration was causing friction. That gap is now closed: Jobber has an official Claude Connector. It uses MCP to connect your Jobber account directly to Claude, so you don't need Make, Zapier or n8n just to get your data into Claude.
Once you connect it, you can:
That covers the "analyzing job data" part of your question without a custom build. Drafting client messages works better too, because Claude can see the real job and client details while it writes.
HilltopAdOS, your point about building a context layer still applies. Pairing the connector with a Claude Project that holds your SOPs, pricing logic and tone of voice would get Rafa close to the "digital brain" HUGEHomePros described. Make and webhooks are still a good fit for event-triggered automations that should run in the background.
You can find the details and connect in the Jobber App Marketplace: Claude Connector.
Thanks Ashley, great update. Rafa, one tip if you set this up: start your Claude Project with just three things.
1. Your pricing rules (how you price a typical job and what's extra)
2. Your top 10 customer questions with the answers you actually give
3. Five real texts or emails you've sent customers, so it learns your tone
Then keep one rule: Claude drafts, you send. Let it suggest follow-ups and write messages, but review anything that goes to a customer or creates an invoice.
