Actions20
- Company Actions
- Contact Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Item Type → Create One
AI-generatedOverview
This node operation creates a new Item Type in the Field Service Management system. It allows users to specify the main identifier (Name or Number) of the item type and optionally provide additional details such as costs, description, external ID, global trade item number, manufacturer, price, type, unit, and VAT. This operation is useful for managing inventory or cataloging different types of items used in field service operations, such as materials, services, equipment, or exchange parts.
Use Case Examples
- Creating a new material item type with a specific name, cost, and manufacturer ID.
- Adding a service item type with a description and price for billing purposes.
Properties
| Name | Meaning |
|---|---|
| NameOrNumber | The main identifier for the item type, either a name or a number. This is a required field. |
| additionalFields | Optional additional fields to provide more details about the item type, such as costs, description, external ID, global trade item number, manufacturer, price, type, unit ID, and VAT. |
Output
JSON
Id- Unique identifier of the created item type.NameOrNumber- Name or number of the created item type.Costs- Purchase cost of the item type.Description- Description of the item type.ExternalId- External ID of the item type.GlobalTradeItemNr- Global trade item number of the item type.Manufacture- Manufacturer ID or number.Price- Selling price of the item type.Type- Type category of the item type.UnitId- Unit name or ID associated with the item type.VAT- Tax value applied to the item type.
Dependencies
- An API key credential for the Field Service Management system (mfrApi)
Troubleshooting
- Ensure the 'NameOrNumber' field is provided as it is required; missing this will cause the request to fail.
- Verify that the API key credential is correctly configured and has permissions to create item types.
- Check that optional fields like 'UnitId' correspond to valid units available in the system to avoid errors.
- If the API returns errors, inspect the request payload and ensure all data types and required fields conform to the API specifications.
