Jobber

**Verdict:** This is a strong, production-ready integration for Jobber via Maton’s managed OAuth gateway. It is well-documented, covers the main Jobber entities, and is appropriate for serious business workflows in field service operations. **What it’s good for** - End-to-end Jobber operations from an agent: creating and managing clients, jobs, invoices, quotes, properties, requests, and users. - Building assistant flows for field service businesses (lawn care, cleaning, maintenance, etc.) that live entirely inside Jobber. - Multi-account scenarios where the assistant must select or switch Jobber connections using the `Maton-Connection` header. - Reporting-style queries, dashboards, or summaries using GraphQL list and detail queries with pagination. **Key strengths** - Comprehensive coverage of critical Jobber objects and workflows (client, job, invoice, quote, property, request, user, custom fields). - Maton gateway handles OAuth, API version headers, and connection management, reducing complexity in the skill itself. - Good example payloads for all core operations and patterns for pagination and error handling. **Risks & limitations** - Requires a valid `MATON_API_KEY` and at least one active Jobber OAuth connection; without that, all calls will fail (400/401/403). - GraphQL queries and mutations must be constructed correctly; deeply nested or overly expensive queries risk hitting Jobber’s query cost limits (10,000-point bucket). - Operations are powerful (create/update entities), so mis-specified inputs can cause unwanted data changes; the agent must validate user intent and parameters carefully. - Webhooks are described but not directly managed by this skill; setting them up and consuming them would require separate infrastructure. **When to use this skill** - When the user explicitly mentions Jobber or is clearly managing a field service business already using Jobber. - When the user wants to manage jobs, clients, invoices, quotes, or schedules in an existing Jobber account. - When building automations that connect Jobber to other third-party tools, using this skill for Jobber and `api-gateway` for the other app. **When not to use it** - If the user asks for non-Jobber third-party integrations only (use `api-gateway` instead). - If the environment does not have network access or a valid Maton API key; the agent should then fall back to planning or mock data rather than attempting real calls.