Work order templates for standardized job creation.
Templates define reusable work order configurations including tasks, pay structure, and service windows. They ensure consistency across similar jobs.
GET /templates
Retrieve all templates available to your company.
{
"results": [
{
"id": 88,
"name": "Standard Router Install",
"description": "2-hour window, fixed pay",
"type_of_work": {
"id": 15,
"name": "Networking"
},
"pay": {
"type": "fixed",
"amount": 125.00
},
"tasks": [
{ "name": "Site survey", "required": true },
{ "name": "Equipment install", "required": true },
{ "name": "Speed test", "required": true }
]
}
]
}When creating a work order, reference a template:
{
"title": "Router Install - Site #44",
"template": { "id": 88 },
"location": { "id": 12345 }
}The work order inherits:
| Benefit | Description |
|---|---|
| Consistency | All WOs for same job type have identical requirements |
| Efficiency | Reduced API payload - just send template ID |
| Governance | Centralized control over job specifications |
Best Practice: Create and maintain templates in the Field Nation UI. Use the API to list available templates and reference them by ID when creating work orders.
| Approach | When to Use |
|---|---|
| Template ID | Standardized, repeatable jobs (recommended) |
| Full Payload | Unique, one-off jobs with custom requirements |
Last updated on