Actions19
- Company Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Overview
This node operation removes a tag from a specified service request in a field service management system. It is useful when you want to update or clean up the metadata associated with service requests by detaching tags that are no longer relevant or were added by mistake.
Practical examples:
- Removing an outdated status tag from a service request after its completion.
- Detaching a category tag if the service request was misclassified.
- Cleaning up tags before archiving or deleting service requests.
Properties
| Name | Meaning |
|---|---|
| Search Service Request | Select the service request to modify, either by searching from a list or specifying its ID. |
| Tag Name or ID | Choose the tag to remove from the service request, either from a dropdown list or by expression. |
Output
The output is a JSON array representing the result of the API call to remove the tag link from the service request. Typically, this will be an empty object or confirmation of success since the operation is a DELETE request on a link resource.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Field Service Management API.
- The node uses authenticated HTTP requests to the API endpoints under
https://portal.mobilefieldreport.com/odata/. - No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an invalid or non-existent service request ID or tag ID will cause the API to fail.
- Insufficient permissions or expired API credentials can lead to authentication errors.
- Network connectivity problems may prevent successful API calls.
Error messages and resolutions:
- "404 Not Found" — The specified service request or tag does not exist. Verify IDs.
- "401 Unauthorized" — Authentication failed. Check API key validity and permissions.
- "400 Bad Request" — The request format is incorrect. Ensure the tag URL is correctly constructed.
- If the node throws an error about missing parameters, ensure both the service request and tag inputs are provided.
Links and References
- Field Service Management API Documentation
- n8n Expressions Documentation (for using expressions in property fields)