Lola Command Composer v2
AI-generatedOverview
The Lola Command Composer v2 node is designed to help users build and structure command definitions for use in the Lola Command Composer system. It allows you to specify a topic and define multiple commands, each with sample dialogs and customizable parameters. This node is useful when you need to programmatically compose or update a set of commands (with their metadata) that can later be consumed by other systems or processes, such as conversational AI, chatbots, or automation scripts.
Practical examples:
- Defining a set of chatbot commands for a specific topic (e.g., "Math Operations") with example user queries and required parameters.
- Structuring command data to be sent to an external API or stored for later processing.
- Automating the creation of command templates for training conversational agents.
Properties
| Name | Meaning |
|---|---|
| Topic Name | The topic name to be used in the Lola Command Composer. This groups the commands under a specific subject or context. |
| Commands | A collection of one or more commands. Each command includes: - Command Name: The identifier for the command. - Sample Dialog: An example dialog illustrating how the command might be invoked. - Command Params: A list of parameter name/value pairs relevant to the command. |
Output
The node adds or updates a field called lola_command_composer in the input item's json object. The structure is as follows:
{
"lola_command_composer": {
"commands": [
{
"cmd": "CALC",
"sample": "Human: how much is 2.34+234.10?",
"topic": "<Topic Name>",
"params": {
"<Param Name 1>": "<Value 1>",
"<Param Name 2>": "<Value 2>"
}
}
// ...more commands as defined
]
}
}
- lola_command_composer.commands: An array containing all composed command objects.
- cmd: The command name.
- sample: The sample dialog for the command.
- topic: The topic name provided.
- params: An object mapping parameter names to their values for this command.
Note: The node does not output binary data.
Dependencies
- No external services, API keys, or special n8n configurations are required.
- All logic is self-contained within the node.
Troubleshooting
Common issues:
- Missing or empty properties: If required fields like "Topic Name" or "Command Name" are left blank, the resulting command objects may be incomplete or invalid for downstream consumers.
- Incorrect parameter structure: Ensure that parameters are added correctly as name/value pairs; otherwise, the
paramsobject may be empty or malformed.
Error messages:
- The node does not throw custom error messages but may fail if required properties are missing or misconfigured. Double-check your input configuration if the output is not as expected.
Links and References
- n8n Documentation: Custom Nodes
- Lola Command Composer (if available) (Add actual link if applicable)