Actions19
- Company Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Overview
This node interacts with a Field Service Management system to retrieve detailed information about a specific "Item Type" entity. It allows users to fetch an item type either by selecting it from a list or by specifying its unique identifier or external ID. This is useful in scenarios where you need to integrate or automate workflows involving inventory items, product types, or equipment classifications managed within the field service platform.
Practical examples include:
- Fetching details of a particular item type before creating a service request or appointment.
- Validating item type data during automated inventory updates.
- Integrating item type information into reporting or analytics workflows.
Properties
| Name | Meaning |
|---|---|
| Item Type | Select an item type either from a searchable list or specify its internal ID directly. |
| External ID | Provide an external identifier to look up the item type instead of using the internal ID. |
The "Item Type" property supports two modes:
- From List: Search and select from existing item types.
- By ID: Enter the internal numeric ID of the item type.
Output
The node outputs JSON data representing the retrieved item type(s). The structure corresponds to the fields defined in the Field Service Management system's "Item Types" entity, typically including identifiers, names, descriptions, units, pricing, and other metadata.
If an external ID is used for lookup, the output will contain the matching item type record(s). If an internal ID is specified, the output contains the single corresponding item type.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Field Service Management system.
- The node makes HTTP GET requests to the system's OData API endpoints.
- Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
- Empty results or no item found: Verify that the provided ID or external ID exists in the system. Ensure correct spelling and casing for external IDs.
- Authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- Network or timeout issues: Check connectivity to the Field Service Management API endpoint.
- Invalid input mode: When using the "From List" mode, ensure the search term matches existing item types; when using "By ID", confirm the ID is numeric and correct.