Actions19
- Company Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Overview
This node operation allows you to create a new "Item Type" in a field service management system. An Item Type represents a category or classification of items such as materials, services, equipment, or parts that can be used in service requests or inventory management.
Typical use cases include:
- Adding new materials or equipment types to your inventory catalog.
- Defining service or exchange parts for tracking and billing.
- Setting up item types with associated costs, prices, and tax information for accurate financial management.
For example, you might create an Item Type called "Air Conditioner Unit" classified as Equipment, with specified purchase cost, selling price, VAT rate, and manufacturer details.
Properties
| Name | Meaning |
|---|---|
| Name Or Number | The name or identifying number of the item type (required). |
| External ID | Optional external identifier for the item, useful for searching or linking items in service requests. |
| Type | Category of the item type. Options: Material, Service, Equipment, Text, ExchangePart, or empty. |
| Costs | Purchase cost of the item. Defaults to 0.0 if not specified. |
| Price | Selling price of the item. Defaults to 0.0 if not specified. |
| Unit Name or ID | Unit of measurement for the item. Can be selected from a list or specified by expression. |
| Manufacture | Identifier or number of the item's manufacturer. |
| VAT | Tax value applicable to the item. Defaults to 0.0 if not specified. |
| Description | Additional descriptive text about the item type. |
| Global Trade Item Nr | Global trade item number (GTIN) for standardized identification. |
Output
The output is a JSON object representing the newly created Item Type as returned by the API. It includes all properties sent during creation along with any additional metadata assigned by the system (such as unique IDs).
No binary data output is produced by this operation.
Dependencies
- Requires an authenticated connection to the Field Service Management API via an API key credential.
- The node uses HTTP POST requests to the API endpoint
https://portal.mobilefieldreport.com/odata/ItemTypesto create the item type. - The "Unit Name or ID" property loads options dynamically from the API's Item Units endpoint.
Troubleshooting
- Missing required fields: Ensure "Name Or Number" is provided; otherwise, the API will reject the request.
- Invalid unit ID: If the unit is not selected correctly or the expression does not resolve to a valid unit, the API may return an error.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to create item types.
- API response errors: Check the exact error message returned by the API for issues like duplicate external IDs or invalid data formats.
- Network issues: Confirm network connectivity to the API endpoint.
Links and References
- Field Service Management API Documentation
- n8n Expressions Documentation (for using expressions in Unit ID)