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 Prompt" operation allows users to send a question or command to Walter, an interactive assistant within the Everest Transport Management System (TMS). This node is useful for automating queries or commands that require conversational interaction with Walter, such as requesting information about missions, clients, or other TMS data.
Typical use cases include:
- Asking Walter for updates on today's missions.
- Sending commands to Walter to perform specific tasks or retrieve data.
- Integrating conversational AI capabilities into workflow automation.
For example, you might ask: "Show me today's missions," and Walter will respond with relevant mission details.
Properties
| Name | Meaning |
|---|---|
| Question | The question or command text to send to Walter. Example: "Show me today's missions". |
| User ID | Optional numeric ID of the user for whom Walter should respond. Defaults to the authenticated user if not set. |
| Save to History | Boolean flag indicating whether to save this interaction in the conversation history. Defaults to true. |
Output
The node outputs a JSON array where each item represents Walter's response to the prompt sent. The structure typically includes fields with the content of Walter's reply, which may contain textual answers or structured data depending on the prompt.
If binary data were involved (not indicated here), it would represent files or media returned by Walter, but this node focuses on JSON responses.
Dependencies
- Requires an API key credential to authenticate with the Everest TMS backend.
- Depends on the Everest TMS API endpoint that handles Walter interactions.
- No additional external services are explicitly required beyond the Everest TMS environment.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Sending empty or malformed questions may result in errors or no meaningful response.
- If the User ID is invalid or does not exist, Walter may default to the authenticated user or return an error.
Error messages:
- Errors from the Everest API will be propagated; typical messages might include authentication errors, invalid parameters, or service unavailability.
- To resolve, verify API credentials, ensure the question string is properly formatted, and confirm the User ID is valid if specified.
Links and References
- Everest TMS official documentation (for API and Walter assistant): [Not provided in source]
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
- General info on conversational AI integration in workflows: https://en.wikipedia.org/wiki/Conversational_AI