Lola Command Composer v2 icon

Lola Command Composer v2

Lola Command Composer, a node to compose a command structure
Join our community

Overview

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—such as for chatbot training, automation scripts, or dynamic command configuration.

Practical examples:

  • Creating a set of commands for a conversational AI bot, each with example user interactions and required parameters.
  • Dynamically generating command structures based on workflow data for downstream processing or API calls.

Properties

Name Meaning
Topic Name The topic name to be used in the Lola Command Composer. This groups your commands under a specific context or subject.
Commands A collection of one or more commands. Each command includes:
- Command Name: The identifier for the command.
- Sample Dialog: An example interaction for the command.
- Command Params: A list of parameter name/value pairs for the command.

Details for "Commands" property:

  • Command Name: A string representing the command's name (e.g., "CALC").
  • Sample Dialog: Example text showing how a user might invoke the command (e.g., "Human: how much is 2.34+234.10?").
  • Command Params: Multiple key-value pairs specifying additional parameters for 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": "Command Name",
        "sample": "Sample Dialog",
        "topic": "Topic Name",
        "params": {
          "ParameterName1": "Value1",
          "ParameterName2": "Value2"
        }
      },
      ...
    ]
  }
}
  • If lola_command_composer.commands already exists, new commands are appended to it.
  • No binary output is produced by this node.

Dependencies

  • No external services, API keys, or special n8n configurations are required.

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 systems.
  • Incorrect parameter structure: Ensure that command parameters are provided as name/value pairs; otherwise, they will not be included in the output.

Error messages:

  • The node does not throw custom error messages but may fail if required properties are missing or misconfigured. Check that all necessary fields are filled out in the node configuration.

Links and References

Discussion