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 add tags to an existing Service Request in a field service management system. Tags are useful for categorizing, filtering, or marking service requests with specific labels that help organize and manage them efficiently.
Common scenarios where this node is beneficial include:
- Automatically tagging service requests based on certain criteria or workflow steps.
- Adding priority or status tags to service requests as they progress.
- Grouping service requests by type, customer, or other custom categories using tags.
For example, after creating a new service request, you might use this operation to add a "High Priority" tag to it, enabling easier filtering and reporting later.
Properties
| Name | Meaning |
|---|---|
| Search Service Request | Select the target Service Request either from a searchable list or by specifying its ID directly. |
| Tag Name or ID | Choose the tag to add to the Service Request from a list of available tags or specify a tag ID. |
Output
The output JSON contains the response from the API call that links the specified tag to the selected service request. Typically, this will be an empty object or confirmation of success since the operation is a link update via HTTP PUT.
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 service's OData endpoints.
- Proper permissions to modify service requests and tags in the connected system are necessary.
Troubleshooting
Common issues:
- Invalid or missing Service Request ID: Ensure the service request exists and the ID is correct.
- Invalid Tag ID: Verify the tag exists and the ID is valid.
- Authentication errors: Confirm the API key credential is correctly configured and has sufficient permissions.
- Network or connectivity problems: Check network access to the API endpoint.
Error messages:
- 404 Not Found: The specified Service Request or Tag does not exist. Double-check IDs.
- 401 Unauthorized: Authentication failed. Reconfigure the API key credential.
- 400 Bad Request: Possibly malformed request body or parameters. Validate inputs.
Resolving these typically involves verifying input values, credentials, and network connectivity.
Links and References
- OData Specification
- Field Service Management API Documentation (generic) (Note: actual documentation URL may vary)