---
title: "Update Meter Trigger's Work Order Template"
method: PATCH
path: "/metertriggers/{id}/workordertemplates"
tags: ["Meter Triggers"]
---

# Update Meter Trigger's Work Order Template

`PATCH /metertriggers/{id}/workordertemplates`

## Path parameters

- `id` integer, required

## Query parameters

- `skipWebhook` boolean

## Request body

- object
  - `procedureTemplateId` integer, nullable — ID of the procedure template used
  - `saveProcedureAsTemplate` boolean, nullable — Save the procedure in data as a new procedure template
  - `title` string — Title of the work order that will be generated. Same string for meter trigger's name. Setting this will also set the corresponding meter's trigger name.
  - `data` object
    - `assetId` integer, nullable
    - `assigneeIds` number[] — Users IDs assigned to the template
    - `description` string, nullable
    - `dueDate` object, nullable
      - `type` 'OFFSET'
      - `offset` number
    - `locationId` integer, nullable — Global ID of the location assigned to the work order
    - `partsUsed` object[], nullable
      - `partId` integer — Global ID of the part
      - `quantityUsed` integer — Quantity used in the work order.
      - `locationId` integer, nullable — Global ID of the location of the part
      - `copyOnRecurring` 'NoCopy' | 'Copy' | 'Default' — Indicates if the parts will be copied to the next work order in the chain (if applicable).
    - `priority` 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH'
    - `procedure` object, nullable
      - `id` number — You should favor 'procedureTemplateId' to attach a procedure template.
      - `title` string, required — Title of the procedure
      - `fields` object[], required — Steps of a procedure
        - `label` string, required
        - `type` 'NUMBER' | 'AMOUNT' | 'TEXT' | 'UNSUPPORTED' | 'HEADING' | 'FILE' | 'SIGNATURE' | 'MULTIPLE_CHOICE' | 'INSPECTION_CHECK' | 'YES_NO_NA' | 'CHECKBOX' | 'CHECKLIST' | 'METER' | 'DATE' | 'CYCLE_COUNT', required
        - `description` string, nullable
        - `choices` string[]
        - `urls` object[]
          - `label` string — Label of the url
          - `link` string, required — Link
        - `meterId` number, nullable — Id of the meter
        - `isDateAndTime` boolean — Indicate if a DATE field also contains the time
        - `index` number — Order which the row is displayed
    - `tagsIds` number[] — Categories IDs
    - `teamIds` number[] — Teams IDs
    - `title` string — Use the `title` field at the root level. If both `title` and `data.title` are provided, `title` will be used.
    - `vendorIds` number[] — Vendor IDs

## Response `204`

Successfully edited the procedure template

## Other responses

- `400` — Bad request
- `401` — Invalid token
- `404` — Could not find the specified work order template.

---

[API](https://skmtc.net/getmaintainx/apis/maintainx-api.md) · [All operations](https://skmtc.net/getmaintainx/apis/maintainx-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/getmaintainx/maintainx-api/revisions/ef9153fcac7c/schema)