repairshopr_* — RepairShopr
The RepairShopr tool namespace — the system of record for tickets and customers. CRUD by entity type, ticket comments, and cross-entity search.
RepairShopr (RS) is the system of record for tickets, customers, and invoices.
Every tool here is entity-typed: you pass an entity_type string
(ticket, customer, invoice, …) plus the operation. The shape is a thin,
uniform CRUD wrapper over the RS API.
Reading
repairshopr_get
Get a single record by ID, or list/filter records of a type.
repairshopr_get(entity_type, id=None, filters=None)| Param | Type | Notes |
|---|---|---|
entity_type | string | Required — ticket, customer, invoice, etc. |
id | int | Fetch one record; omit to list |
filters | object | Field filters when listing |
repairshopr_search
Cross-entity search by free-text query. Use this when you don’t know the ID and want RS to find the match.
repairshopr_search(query, search_type="all")search_type defaults to "all"; narrow it (e.g. to a single entity) when
you know what you’re looking for.
Writing
repairshopr_create
repairshopr_create(entity_type, data)data is the full record payload as an object. Shape depends on the entity —
when in doubt, repairshopr_get an existing record of the same type to see
the field names.
repairshopr_update
repairshopr_update(entity_type, id, data)All three are required. data carries only the fields you’re changing.
repairshopr_delete
repairshopr_delete(entity_type, id)Destructive. RS is the system of record — confirm before deleting anything that downstream syncs (the RS ticket sync) read from.
Ticket comments
repairshopr_comment
Add a comment to a ticket, with control over customer-visibility and email.
repairshopr_comment(ticket_id, comment, hidden=False, do_not_email=False)| Param | Default | Effect |
|---|---|---|
hidden | False | True keeps the comment internal (not customer-visible) |
do_not_email | False | True suppresses the customer notification email |
For an automated/internal note you don’t want the customer to see or be
emailed about, set both hidden=True and do_not_email=True.
How this feeds the rest of the system
RS is upstream of the order pipeline:
- The RS ticket sync pulls ticket/invoice data hourly into the master order list.
- ESA order processing buckets that list on RS customer ID.
create_task_from_ticket(in the tasks namespace) seeds a Leif task straight from an RS ticket.
Related pages
- RepairShopr Ticket Workflows — the workflows around these tools
- Customer ID Mapping — program → RS customer ID
- RS Ticket Sync — the hourly sync that consumes RS data
- ESA Order Processing — the downstream bucketing
- QuickBooks — the accounting side of the same invoices