Forbind Claude og ChatGPT med Customers 1st (ServicePOS)

28 værktøjer til Customers 1st (ServicePOS)

Værktøjerne er slået til, når du forbinder. Du kan slå dem fra enkeltvis eller kræve din godkendelse, før de kører.

• add_ticket_commentÆndrer dataAdd a comment to a ticket; put `taskid` (the ticket ID) and `comment` in `content`.
• add_ticket_materialÆndrer dataAdd a material line to a ticket; `content` needs `taskid` (the ticket ID), `title`, `amount` and `price`, optionally `productid`.
• create_customerÆndrer dataCreate a customer; put the fields (name, email, phone, address, zipcode, city, vat, tags, note) in `content`. Search first to avoid duplicates.
• create_customer_articleÆndrer dataRegister an item for a customer; put title, serieno, color, size and customerid in `content`.
• create_productÆndrer dataCreate a product; put title, price, costprice, barcode, productno, brand, stock numbers and tags in `content`.
• create_sales_orderÆndrer dataCreate a sales order; put `customer_id` and an optional `note` in `content`.
• get_customerGet one customer by `customer_id`, with contact details, address, balance, tags and notes.
• get_customer_articleGet one customer article by its ID (`customer_id`), with title, serial number, color, size and owner.
• get_pos_paymentGet one POS payment by `payment_id`, with sold items, amounts, payment types and customer.
• get_productGet one product by `product_id`, with price, cost price, stock, barcode and supplier.
• get_sales_orderGet one sales order by `order_id`.
• get_storeGet the connected store's details and settings.
• get_ticketGet one ticket by `ticket_id`, with status, description, customer, assignee, agreed price and payments.
• list_customer_articlesList customer articles (items a customer owns and brings in, e.g. a bike or device) filtered by `customerid`, `serieno` or `freetext`.
• list_inventory_levelsList stock levels, optionally for one `product_id` or `product_no`; set `exclude_zero` to skip empty stock.
• list_sales_ordersList sales orders, filtered by `search` text or `open`, with `page`/`limit` paging.
• list_ticket_commentsList comments on a ticket by `taskid` (the ticket ID).
• list_ticket_materialsList the materials (parts, products and labour lines) on a ticket by `ticketid`.
• list_ticket_tagsList the ticket tags used in the store, e.g. to filter tickets by `tagids`.
• list_usersList the store's staff users, e.g. to find an assignee.
• search_customersSearch customers by `freetext`, `name`, `email`, `phoneno`, `customerno`, `cvr` or `tags`, with paging via `pagination_start`/`pagination_page_length`. Use this to find a customer ID first.
• search_pos_paymentsSearch POS payments (sales) by date range (`fromdate`/`todate`), `customerid`, `status`, `productid`, amount range or `paymentno`, with paging.
• search_productsSearch products by `freetext`, `barcode`, `product_no`, `brand`, `tag`, `in_stock`, supplier or `needs_ordering`, with paging.
• search_suppliersSearch your suppliers by `filter` text, with paging.
• search_ticketsSearch tickets (repair or sale cases) by `customerid`, `customerarticleid`, `type` (repair or sale), `tagids`, date range or `updated_after`, with paging.
• update_customerÆndrer dataUpdate a customer by `customer_id` with the fields in `content`. This is a full replace (PUT), so get the customer first and send all fields you want to keep.
• update_customer_articleÆndrer dataUpdate a customer article by its ID (`customer_id`) with the fields in `content` (title, serial number, color, size, owner).
• update_productÆndrer dataUpdate selected fields of a product by `product_id`; only the fields you put in `content` change (e.g. price, stockno, title).

Spørgsmål