Actions55
- Client Actions
- General Actions
- Mission Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Overview
The "Update Location" operation for the "Agent" resource in this node allows updating the GPS coordinates (latitude and longitude) of an agent within the Everest Transport Management System (TMS). This is useful for real-time tracking or status updates of agents (e.g., drivers, field personnel) to reflect their current location.
Practical scenarios include:
- Updating an agent's position during a delivery route.
- Tracking field agents for dispatch optimization.
- Logging location data for compliance or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent whose location is being updated. Optional; if omitted, the authenticated agent's location will be updated. |
| Latitude | The GPS latitude coordinate of the agent's current location. |
| Longitude | The GPS longitude coordinate of the agent's current location. |
Output
The node outputs a JSON array where each element corresponds to the result of the update location operation for each input item. The structure typically contains confirmation or details about the updated agent location as returned by the Everest TMS API.
If the operation fails for any item and "Continue On Fail" is enabled, the output for that item will contain an error message describing the failure.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node depends on the Everest API endpoints to perform the update location action.
- Proper permissions for the API key to update agent information are necessary.
Troubleshooting
- Missing or invalid Agent ID: If no Agent ID is provided, the node attempts to update the authenticated agent's location. Ensure the authentication context is correct or provide a valid Agent ID.
- Invalid latitude or longitude values: Coordinates must be valid GPS strings. Invalid formats may cause API errors.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues can cause failures; retrying later may resolve these.
- Error messages: The node returns error messages from the Everest API. Common errors might include "Agent not found," "Invalid coordinates," or "Unauthorized." Review the error message and adjust inputs or credentials accordingly.
Links and References
- Everest TMS official API documentation (refer to your internal or vendor-provided docs)
- GPS coordinate standards and validation references
- n8n documentation on setting up API credentials and error handling