Repairshopr Search

• query (string, optional) - Search term. The documentation shows query as integer but that's likely a mistake; use string.

Example call:

const result = await skill({ name: "repairshopr-search" }, {
  query: "John Doe"
})

// Or with partial info
const result2 = await skill({ name: "repairshopr-search" }, {
  query: "555-123"
})

Response includes:

{
  "quick_result": null,
  "results": [
    {
      "table": {
        "_id": 1,
        "_type": "customer",
        "_index": "customers",
        "_source": {
          "table": {
            "firstname": "Walkin",
            "lastname": "Customer",
            "email": "[email protected]",
            "phones": [...]
          }
        }
      }
    },
    {
      "table": {
        "_type": "ticket",
        // ticket data
      }
    }
    // various types
  ]
}

The results array contains heterogeneous objects; each has a _type field indicating the entity type ("customer", "contact", "asset", "lead", "ticket", "invoice", "estimate", "product", "purchase_order", "vendor", "report", "wiki", etc.). The actual data is nested under _source.

Important

• The search returns mixed types; you must check _type to interpret each result
• Pagination? Not documented; likely returns top results only
• Permissions filter what you can see; you won't see entities you lack access to
• Search likely uses Elasticsearch or similar; supports partial matching

Related skills

• repairshopr-customer-search - Customer-specific search
• repairshopr-ticket - For detailed ticket lookups after finding via search