Limble
App · 20 actions
Run maintenance in Limble CMMS: create, assign and complete work orders, manage assets and spare parts, and review work requests. Start a workflow when a task is created or completed, changes status, a part runs low, or a work request comes in.
Actions
| Action | What it does |
|---|---|
| Add task comment | Add a comment to a task, such as an update for the technician or the person who asked for the work. |
| Adjust part stock | Add to, take from or set a part's stock, such as after a delivery or a count. |
| Approve or decline work request | Approve a waiting work request, which creates its task, or decline it with a reason. |
| Complete task | Mark a task complete. |
| Create asset | Add an asset, such as a machine, vehicle or room, at a location. |
| Create part | Add a spare part to a location's inventory, with its stock, price and the minimum that prompts a reorder. |
| Create task | Create a work order or other task at a location, optionally for an asset, assigned to a person or team, or copied from a template. |
| Delete asset | Delete an asset from Limble. |
| Delete part | Remove a part from Limble's inventory. |
| Delete task | Delete a task from Limble. |
| Get asset | Get one asset: its location, parent asset, running hours and the link people use to report a problem with it. |
| Get task | Get one task: its type, state, status, assignee, asset, dates and requester. |
| List assets | List your equipment and other assets, filtered by location, name or parent asset. |
| List parts | List spare parts with their stock, filtered by location, name or part number, or only those below their minimum stock. |
| List tasks | List work orders, preventive maintenance and other tasks, newest first, filtered by location, asset, type, state, assignee or status. |
| List work requests | List work requests, newest first, such as the ones waiting for review. |
| Reopen task | Reopen a completed task so work can continue on it. |
| Submit work request | Send Limble a work request, as its request portal does. |
| Update asset | Rename an asset, move it under another asset, or change its weekly hours. |
| Update task | Change a task's name, description, due date, type, asset, assignee, priority, status or schedule. |
Add task comment
Add a comment to a task, such as an update for the technician or the person who asked for the work.
Inputs
- Task
task_idtextRequired - The task. Pick an open one, or give its ID from an earlier step.
- Comment
commenttextRequired - What to say.
- Show to requesters
show_to_requesterstrue/false - Whether people outside Limble, such as whoever requested the work, can see it. On unless turned off.Default:
true.
Outputs
addedtrue/false- True once it is added
commenttext- The comment
shown_to_requesterstrue/false- Whether people outside Limble can see it
task_idnumber- The task commented on
Example output
{
"added": true,
"comment": "Parts ordered, back on Thursday.",
"shown_to_requesters": true,
"task_id": 8261
}Adjust part stock
Add to, take from or set a part's stock, such as after a delivery or a count.
Inputs
- Part
part_idtextRequired - The part. Pick one, or give its ID from an earlier step.
- Change
modetext - Add to the stock, take from it, or set it. Defaults to add.One of:
add(Add to the stock),remove(Take from the stock),set(Set the stock to). Default:add. - Quantity
quantitynumberRequired - How many.At least 0.
Outputs
partobject- The part, with its new stock
previous_stocknumber- Stock before
stocknumber- Stock now
Example output
{
"part": {
"category": "Air Filters",
"generalPrice": 5.99,
"generalStock": 12,
"lastEdited": 1794729600,
"location": "Shelf A",
"locationID": 73,
"maxQtyThreshold": 40,
"minQtyStatus": 0,
"minQtyThreshold": 10,
"name": "Air filter",
"number": "25x25x1",
"partID": 2941,
"stockOnHand": 12,
"unitCode": "each"
},
"previous_stock": 10,
"stock": 12
}Approve or decline work request
Approve a waiting work request, which creates its task, or decline it with a reason.
Inputs
- Work request
work_request_idtextRequired - A waiting work request. Pick one, or give its ID.
- Decision
decisiontextRequired - Approve it into a task, or decline it.One of:
approve(Approve (creates a task)),decline. - Reason
decline_reasontext - Why it is declined, such as Duplicate request.Only when Decision is Decline.
- Notes
notestext - Anything else the requester should know.Only when Decision is Decline.
Outputs
task_idnumber- The task approving it created; empty if declined
work_requestobject- The work request
Example output
{
"task_id": 8262,
"work_request": {
"additionalNotes": null,
"assetId": 10836,
"checklistID": 8262,
"createdAt": "2026-11-18 09:30:00",
"locationId": 73,
"priorityId": null,
"requestDescription": "The pump on floor 2 is leaking.",
"requestTitle": "Leaking pump",
"requesterName": "Jo Rivera",
"reviewedAt": null,
"reviewedReason": null,
"status": "Approved",
"workRequestSubmissionId": 512
}
}Complete task
Mark a task complete. Limble completes only tasks with an assignee and with every instruction finished.
Inputs
- Task
task_idtextRequired - The task. Pick an open one, or give its ID from an earlier step.
- Completed by
completed_bytext - Who completed it. Leave blank to keep the task's assignee; a person chosen here becomes its assignee.
Outputs
changedtrue/false- False if the task was already complete, so nothing was sent
taskobject- The task
Example output
{
"changed": true,
"task": {
"assetID": 10836,
"completedByUser": 341,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 1794816000,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 1,
"statusID": 2,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
}
}Create asset
Add an asset, such as a machine, vehicle or room, at a location.
Inputs
- Name
nametextRequired - What the asset is called.
- Location
location_idtextRequired - Where the asset is.
- Parent asset
parent_asset_idtext - The asset it belongs under, such as the line a motor is part of.
- Hours a week
hours_per_weeknumber - How many hours a week it runs. Leave blank to use the location's hours.From 0 to 168.
Outputs
assetobject- The new asset
asset_idnumber- The new asset's ID
Example output
{
"asset": {
"assetID": 10836,
"hoursPerWeek": 40,
"lastEdited": 1794729600,
"locationID": 73,
"name": "Conveyor line 2",
"parentAssetID": 0,
"startedOn": 1632949149,
"workRequestPortal": "https://app.limblecmms.com/#!/problem/fdle6w36/73/10836"
},
"asset_id": 10836
}Create part
Add a spare part to a location's inventory, with its stock, price and the minimum that prompts a reorder.
Inputs
- Name
nametextRequired - What the part is called.
- Location
location_idtextRequired - The location that stocks it.
- Part number
part_numbertext - Its part number.
- Stock
stocknumber - How many are in stock now.
- Price
pricenumber - What one costs.At least 0.
- Minimum stock
minimum_stocknumber - When stock falls under this, Limble prompts a reorder.At least 0.
- Maximum stock
maximum_stocknumber - The stock to reorder up to.At least 0.
- Storage location
storage_locationtext - Where it is kept, such as Shelf A.
Outputs
partobject- The new part
part_idnumber- The new part's ID
Example output
{
"part": {
"category": "Air Filters",
"generalPrice": 5.99,
"generalStock": 12,
"lastEdited": 1794729600,
"location": "Shelf A",
"locationID": 73,
"maxQtyThreshold": 40,
"minQtyStatus": 0,
"minQtyThreshold": 10,
"name": "Air filter",
"number": "25x25x1",
"partID": 2941,
"stockOnHand": 12,
"unitCode": "each"
},
"part_id": 2941
}Create task
Create a work order or other task at a location, optionally for an asset, assigned to a person or team, or copied from a template.
Inputs
- Name
nametextRequired - What the task is called.
- Location
location_idtextRequired - Where the work happens.
- Due
duedate and timeRequired - When the task is due.
- Type
task_typetext - What kind of task. Defaults to an unplanned work order.One of:
2(Unplanned work order),4(Planned work order),1(Preventive maintenance),6(Work request). Default:2. - Assign to user
assigned_usertext - The person to assign the task to. Leave blank to assign a team instead.
- Assign to team
assigned_teamtext - The team to assign the task to, if not a person.
- Description
descriptiontext - What needs doing.
- Asset
asset_idtext - The asset the task is for. Pick one, or give its ID.
- Priority
prioritytext - One of the priorities set up in Limble.
- Estimated time
estimated_minutesnumber - How long the task should take, in minutes.At least 0.
- Scheduled start
scheduled_startdate and time - When work is planned to start.
- Scheduled end
scheduled_enddate and time - When work is planned to finish. Must be after the start.
- Copy steps from template
template_idtext - The ID of a task template in Limble, to copy its instructions into the new task.
- Requester name
requester_nametext - Who asked for the work.
- Requester email
requester_emailtext - Their email address.
- Requester phone
requester_phonetext - Their phone number.
Outputs
taskobject- The new task
task_idnumber- The new task's ID
Example output
{
"task": {
"assetID": 10836,
"completedByUser": 0,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 0,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 0,
"statusID": 1,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
},
"task_id": 8261
}Delete asset
Delete an asset from Limble.
Inputs
- Asset
asset_idtextRequired - The asset. Pick one, or give its ID from an earlier step.
Outputs
asset_idnumber- The asset deleted
deletedtrue/false- True once it is deleted
Example output
{
"asset_id": 10836,
"deleted": true
}Delete part
Remove a part from Limble's inventory.
Inputs
- Part
part_idtextRequired - The part. Pick one, or give its ID from an earlier step.
Outputs
deletedtrue/false- True once it is deleted
part_idnumber- The part deleted
Example output
{
"deleted": true,
"part_id": 2941
}Delete task
Delete a task from Limble.
Inputs
- Task
task_idtextRequired - The task. Pick an open one, or give its ID from an earlier step.
Outputs
deletedtrue/false- True once it is deleted
task_idnumber- The task deleted
Example output
{
"deleted": true,
"task_id": 8261
}Get asset
Get one asset: its location, parent asset, running hours and the link people use to report a problem with it.
Inputs
- Asset
asset_idtextRequired - The asset. Pick one, or give its ID from an earlier step.
Outputs
assetobject- The asset
Example output
{
"asset": {
"assetID": 10836,
"hoursPerWeek": 40,
"lastEdited": 1794729600,
"locationID": 73,
"name": "Conveyor line 2",
"parentAssetID": 0,
"startedOn": 1632949149,
"workRequestPortal": "https://app.limblecmms.com/#!/problem/fdle6w36/73/10836"
}
}Get task
Get one task: its type, state, status, assignee, asset, dates and requester.
Inputs
- Task
task_idtextRequired - The task. Pick an open one, or give its ID from an earlier step.
Outputs
taskobject- The task
Example output
{
"task": {
"assetID": 10836,
"completedByUser": 0,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 0,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 0,
"statusID": 1,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
}
}List assets
List your equipment and other assets, filtered by location, name or parent asset.
Inputs
- Location
location_idtext - Only assets at this location.
- Name contains
nametext - Only assets whose name contains this.
- Parent asset
parent_asset_idtext - Only the assets that sit under this one.
- Changed after
edited_afterdate and time - Only those changed after this time.
- Limit
limitnumber - The most to return. Defaults to 100.From 1 to 10000. Default:
100.
Outputs
assetslist- The assets
countnumber- How many were returned
Example output
{
"assets": [
{
"assetID": 10836,
"hoursPerWeek": 40,
"lastEdited": 1794729600,
"locationID": 73,
"name": "Conveyor line 2",
"parentAssetID": 0,
"startedOn": 1632949149,
"workRequestPortal": "https://app.limblecmms.com/#!/problem/fdle6w36/73/10836"
}
],
"count": 1
}List parts
List spare parts with their stock, filtered by location, name or part number, or only those below their minimum stock.
Inputs
- Location
location_idtext - Only parts stocked at this location.
- Name contains
nametext - Only parts whose name contains this.
- Part number
part_numbertext - Only the part with this number.
- Below minimum only
below_minimumtrue/false - Only parts whose stock is under their minimum.
- Limit
limitnumber - The most to return. Defaults to 100.From 1 to 10000. Default:
100.
Outputs
countnumber- How many were returned
partslist- The parts
Example output
{
"count": 1,
"parts": [
{
"category": "Air Filters",
"generalPrice": 5.99,
"generalStock": 12,
"lastEdited": 1794729600,
"location": "Shelf A",
"locationID": 73,
"maxQtyThreshold": 40,
"minQtyStatus": 0,
"minQtyThreshold": 10,
"name": "Air filter",
"number": "25x25x1",
"partID": 2941,
"stockOnHand": 12,
"unitCode": "each"
}
]
}List tasks
List work orders, preventive maintenance and other tasks, newest first, filtered by location, asset, type, state, assignee or status.
Inputs
- Location
location_idtext - Only tasks at this location.
- Asset
asset_idtext - Only tasks for this asset.
- Type
task_typetext - Only tasks of this type.One of:
2(Unplanned work order),4(Planned work order),1(Preventive maintenance),6(Work request),5(Cycle count),7(Part below minimum),8(Materials request). - Open or complete
statetext - Only open tasks, or only completed ones.One of:
open,complete. - Assigned to user
assigned_usertext - Only tasks this person works on, directly or through a team.
- Assigned to team
assigned_teamtext - Only this team's tasks.
- Status
status_idtext - Only tasks in this status.
- Name contains
nametext - Only tasks whose name contains this.
- Changed after
edited_afterdate and time - Only those changed after this time.
- Limit
limitnumber - The most to return. Defaults to 100.From 1 to 10000. Default:
100.
Outputs
countnumber- How many were returned
taskslist- The tasks
Example output
{
"count": 1,
"tasks": [
{
"assetID": 10836,
"completedByUser": 0,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 0,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 0,
"statusID": 1,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
}
]
}List work requests
List work requests, newest first, such as the ones waiting for review.
Inputs
- Status
statustext - Only those waiting, approved or declined.One of:
pending(Waiting for review),approved,rejected(Declined). - Location
location_idtext - Only requests for this location.
- Search
searchtext - Only requests that mention this.
- Submitted after
created_afterdate and time - Only requests submitted after this time.
- Limit
limitnumber - The most to return. Defaults to 100.From 1 to 10000. Default:
100.
Outputs
countnumber- How many were returned
work_requestslist- The work requests
Example output
{
"count": 1,
"work_requests": [
{
"additionalNotes": null,
"assetId": 10836,
"checklistID": null,
"createdAt": "2026-11-18 09:30:00",
"locationId": 73,
"priorityId": null,
"requestDescription": "The pump on floor 2 is leaking.",
"requestTitle": "Leaking pump",
"requesterName": "Jo Rivera",
"reviewedAt": null,
"reviewedReason": null,
"status": "Pending",
"workRequestSubmissionId": 512
}
]
}Reopen task
Reopen a completed task so work can continue on it.
Inputs
- Task ID
task_idtextRequired - The completed task's ID, from an earlier step or Limble.
Outputs
taskobject- The task
Example output
{
"task": {
"assetID": 10836,
"completedByUser": 0,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 0,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 0,
"statusID": 1,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
}
}Submit work request
Send Limble a work request, as its request portal does. It waits for someone to approve it into a task or decline it.
Inputs
- Location
location_idtextRequired - Where the problem is.
- Title
titletextRequired - The problem in a few words.
- Description
descriptiontext - What is wrong.
- Asset
asset_idtext - The asset with the problem, if known.
- Requester name
requester_nametext - Who asked for the work.
- Requester email
requester_emailtext - Their email address.
- Requester phone
requester_phonetext - Their phone number.
Outputs
work_requestobject- The work request
Example output
{
"work_request": {
"additionalNotes": null,
"assetId": 10836,
"checklistID": null,
"createdAt": "2026-11-18 09:30:00",
"locationId": 73,
"priorityId": null,
"requestDescription": "The pump on floor 2 is leaking.",
"requestTitle": "Leaking pump",
"requesterName": "Jo Rivera",
"reviewedAt": null,
"reviewedReason": null,
"status": "Pending",
"workRequestSubmissionId": 512
}
}Update asset
Rename an asset, move it under another asset, or change its weekly hours. Blank fields are left as they are.
Inputs
- Asset
asset_idtextRequired - The asset. Pick one, or give its ID from an earlier step.
- Name
nametext - A new name.
- Parent asset
parent_asset_idtext - The asset to put it under.
- Hours a week
hours_per_weeknumber - How many hours a week it runs.From 0 to 168.
Outputs
assetobject- The asset
Example output
{
"asset": {
"assetID": 10836,
"hoursPerWeek": 40,
"lastEdited": 1794729600,
"locationID": 73,
"name": "Conveyor line 2",
"parentAssetID": 0,
"startedOn": 1632949149,
"workRequestPortal": "https://app.limblecmms.com/#!/problem/fdle6w36/73/10836"
}
}Update task
Change a task's name, description, due date, type, asset, assignee, priority, status or schedule. Blank fields are left as they are.
Inputs
- Task
task_idtextRequired - The task. Pick an open one, or give its ID from an earlier step.
- Name
nametext - A new name.
- Due
duedate and time - A new due date.
- Type
task_typetext - Change it to this kind of task.One of:
2(Unplanned work order),4(Planned work order),1(Preventive maintenance),6(Work request). - Assign to user
assigned_usertext - The person to reassign the task to. Leave blank to assign a team instead.
- Assign to team
assigned_teamtext - The team to reassign the task to, if not a person.
- Status
status_idtext - Move the task to this status, such as In Progress. To complete it, use 'Complete task'.
- Description
descriptiontext - What needs doing.
- Asset
asset_idtext - The asset the task is for. Pick one, or give its ID.
- Priority
prioritytext - One of the priorities set up in Limble.
- Estimated time
estimated_minutesnumber - How long the task should take, in minutes.At least 0.
- Scheduled start
scheduled_startdate and time - When work is planned to start.
- Scheduled end
scheduled_enddate and time - When work is planned to finish. Must be after the start.
Outputs
taskobject- The task
Example output
{
"task": {
"assetID": 10836,
"completedByUser": 0,
"completionNotes": null,
"createdDate": 1794729600,
"dateCompleted": 0,
"description": "Belt on line 2 is fraying.",
"downtime": 0,
"due": 1794988800,
"lastEdited": 1794729600,
"lastEditedByUser": 341,
"locationID": 73,
"name": "Replace conveyor belt",
"poIDs": [],
"priority": 2,
"priorityID": 10,
"requestorDescription": null,
"requestorEmail": null,
"requestorName": null,
"requestorPhone": null,
"scheduledEnd": 0,
"scheduledStart": 0,
"status": 0,
"statusID": 1,
"taskID": 8261,
"teamID": 0,
"template": false,
"type": 2,
"userID": 341
}
}