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 "Walter" resource with the "Send Message" operation in this node allows sending a message through the Walter system, which appears to be a messaging or notification service integrated within the Everest Transport Management System (TMS). This operation is useful for automating communication workflows, such as sending updates, alerts, or commands to users directly from n8n.
Typical use cases include:
- Sending status updates or notifications to specific users.
- Automating responses or messages triggered by other workflow events.
- Issuing commands to Walter for further processing or actions.
For example, you could configure the node to send a message like "Hello! I have an update for you." to a particular user or broadcast commands that Walter can interpret and act upon.
Properties
| Name | Meaning |
|---|---|
| Message | The content of the message Walter will send. Example: "Hello! I have an update for you." |
| User ID | Numeric ID of the user to whom the message should be sent. Optional; defaults to the authenticated user if not specified. |
| Save to History | Boolean flag indicating whether to save the sent message to the conversation history. Defaults to true. |
| Commands | A collection of commands to send along with the message. Each command includes: |
| - Command Name | The name of the command to execute, e.g., "get_missions". |
| - Parameters | Comma-separated parameters for the command, e.g., "date_start,date_end". |
Output
The node outputs JSON data representing the result of the send message operation. This typically includes confirmation details about the message sent, any response from Walter, or error information if the operation failed.
If multiple items are processed, the output is an array of such JSON objects, one per input item.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node depends on the Everest TMS backend services being accessible.
- No additional external dependencies beyond the configured API credentials and network access.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a non-existent User ID may result in errors or messages not being delivered.
- Improperly formatted commands or parameters might cause the Walter system to reject the command.
Error Messages:
- Errors returned from the Everest API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, invalid parameters, or server-side issues.
Resolutions:
- Verify API credentials and permissions.
- Ensure User IDs exist and are correct.
- Validate command names and parameter formats before sending.
Links and References
- Everest TMS official documentation (for API and Walter messaging specifics) — [Not provided in source]
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/
- General info on Transport Management Systems (TMS) and messaging automation.