Connect Claude & ChatGPT to Limble CMMS

29 tools for Limble CMMS

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_asset_logChanges dataAdd a log entry (`log_entry` text) to an asset by `asset_id`.
• add_purchase_order_itemChanges dataAdd a line item to a purchase order by `po_id`: a part_id or asset_id, quantity, rate, tax, discount and shipping.
• add_task_commentChanges dataAdd a `comment` to a task by `task_id`. Set show_external_users to true to make it visible to external users and requesters.
• approve_work_requestVisible to othersApprove a submitted work request by `work_request_submission_id`, turning it into a work order.
• create_purchase_orderChanges dataCreate a purchase order with location_id, vendor_id, request_description, expected date (Unix timestamp), budget_id and custom fields.
• create_work_orderChanges dataCreate a task/work order. Pass the title in `body_name`, the location in `body_location_id`, the task type in `body_type`, the due date (Unix timestamp) in `body_due`, plus priority and scheduled start/end. Search first to avoid duplicates.
• create_work_requestChanges dataSubmit a work request for a `location_id` with request_title, request_description, requester_name, optional asset_id and priority_id, and `due_date_unit`.
• decline_work_requestVisible to othersDecline a submitted work request by `work_request_submission_id`, with an optional decline_reason and notes.
• delete_taskDeletesPermanently delete a task by `task_id`. This cannot be undone.
• get_current_userGet the Limble user and customer linked to the connected API keys.
• list_asset_logsList the log entries for an asset by `asset_id`, filtered by users, text or date range.
• list_labor_entriesList logged labor time, filtered by tasks, users, locations and date range, with cursor paging.
• list_locationsList locations (sites), filtered by name, regions or location IDs. Use to find a location ID.
• list_part_usageList part usage on tasks, filtered by parts, tasks, name or date range.
• list_prioritiesList the task priority levels. Use to get a priority ID.
• list_purchase_order_itemsList purchase order line items, filtered by PO IDs, item IDs, numbers or last-edited date range.
• list_purchase_ordersList purchase orders, filtered by PO IDs, numbers, status, vendors, locations or last-edited date range.
• list_statusesList the task statuses, optionally filtered by name.
• list_task_commentsList the comments on a task by `task_id`.
• list_task_instructionsList the checklist instructions of a task by `task_id`.
• list_task_partsList the parts attached to a task by `task_id`.
• list_teamsList teams, optionally filtered by name or team IDs.
• list_work_requestsList submitted work requests, filtered by `search` text, statuses, location IDs or created date range.
• search_assetsSearch assets by name, locations, parent_asset_id or asset IDs, with cursor paging. Use to find an asset ID.
• search_partsSearch spare parts by name, part numbers, part IDs or locations, with cursor paging. Shows stock information.
• search_tasksSearch tasks (work orders and preventive maintenance) by name, type, status, assets, locations, users, teams, tag or due/scheduled/completed date range (Unix timestamps), with cursor paging. To get one task, pass its ID in `tasks`.
• search_usersSearch users by name, roles, teams or user IDs. Use to find someone to assign work to.
• search_vendorsSearch vendors by name, vendor IDs or locations, with cursor paging.
• update_purchase_orderChanges dataUpdate a purchase order by `order_id` (the PO ID): vendor, budget, assigned user, request description or custom fields.

Questions