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 node integrates with the Everest Transport Management System (TMS) to perform various operations. Specifically, for the Notification resource and the Send Push Notification operation, it sends a push notification message to a specified agent within the system.
This is useful in scenarios where real-time alerts or updates need to be pushed directly to agents, such as notifying them about new missions, changes in assignments, or urgent messages. For example, a logistics coordinator can send a push notification to a driver (agent) informing them of a new delivery task with a mission reference code embedded in the message.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The numeric ID of the agent who will receive the push notification. |
| Message Text | The text content of the push notification message. Supports a placeholder [mission_ref] which will be replaced by the Mission Reference value. |
| Mission Reference | A string that replaces the [mission_ref] placeholder in the message text, typically representing a mission identifier or code. |
Output
- The output is a JSON array containing the result of the push notification sending operation.
- Each item corresponds to one input item processed.
- The exact structure of the JSON output depends on the response from the Everest TMS API but generally includes confirmation or status details of the push notification sent.
- This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses internal helper functions to make HTTP requests to the Everest API endpoints.
- No additional external services are required beyond the Everest TMS platform.
Troubleshooting
Common issues:
- Invalid or missing Agent ID: Ensure the agent ID exists and is correct.
- Incorrect API credentials: Verify the API key or authentication token is valid and has necessary permissions.
- Network or connectivity problems: Check network access to the Everest API endpoint.
- Placeholder replacement errors: If
[mission_ref]is used in the message text but no mission reference is provided, the placeholder may remain unreplaced.
Error messages:
- Errors returned from the Everest API will be propagated. Common messages might include "Agent not found" or "Unauthorized".
- To resolve, verify input parameters and credentials.
- Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.
Links and References
- Everest TMS official documentation (not provided here; consult your Everest TMS provider)
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/