Actions19
- Company Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Overview
This node operation creates a new Service Object in a field service management system. A Service Object typically represents a physical or logical asset or location associated with a company, such as equipment, facilities, or service points. Creating a Service Object allows users to track and manage these assets within the system.
Common scenarios where this node is beneficial include:
- Adding new equipment or assets to a company's inventory for maintenance scheduling.
- Registering new service locations or customer sites.
- Associating assets with specific companies for organizational purposes.
For example, a technician scheduling workflow might use this node to create a new service object representing a newly installed machine at a client site, linking it to the client's company record.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the Service Object to be created. |
| Location | A collection of fields describing the location details of the Service Object: |
| - Address (string): Street address or description. | |
| - Postal (string): Postal code. | |
| - City (string): City name. | |
| - State (string): State or province. | |
| - Country (string): Country name. | |
| - Is Valid Location (boolean): Indicates if the location data is verified as valid. | |
| Company ID | Reference to the company associated with the Service Object. Can be selected from a list or specified by ID. |
| External ID | An optional external identifier for the Service Object, useful for integration with other systems. |
Output
The output JSON contains the response from the API after creating the Service Object. This typically includes all properties of the newly created Service Object, such as its unique ID, name, location details, associated company ID, and any external identifiers.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the field service management platform's API.
- The node makes HTTP POST requests to the platform's OData endpoint for Service Objects (
https://portal.mobilefieldreport.com/odata/ServiceObjects). - Proper configuration of the API credential in n8n is necessary for successful execution.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions to create Service Objects.
- Validation errors: Missing required fields like "Name" or invalid formats in location fields may cause the API to reject the request. Verify input values before execution.
- Company ID issues: If the provided Company ID does not exist or is invalid, the creation will fail. Use the search functionality to select a valid company.
- Network or API downtime: Temporary connectivity issues or API outages can cause request failures. Retry after some time or check the service status.
Links and References
- Field Service Management API Documentation
- OData Protocol Overview
- n8n HTTP Request Node Documentation (for understanding how API calls are made)