Emblr Cmdr

Run pre-approved commands on your resources

Emblr Cmdr

AI-generated

Overview

This node, named "Emblr Cmdr," allows users to run pre-approved commands on their resources by selecting templates and assemblers, and providing parameters and seed data. It is useful in scenarios where automated command execution based on predefined templates is needed, such as triggering workflows or updating database entries dynamically.

For example, a user can select a command template, specify parameters and seed values, and execute the command which updates a resource stack accordingly. The node listens for changes triggered by this command and outputs the resulting data.

Properties

Name Meaning
Template Name or ID Select a command template from a list or specify its ID via expression. Templates define the command structure to be executed.
Choose Assembler Name or ID Select an assembler (by name or ID) that will be used for the stack operation. Assemblers are components that process or assemble the command.
Seed Parameters Provide one or more seed parameters consisting of a seed parameter name/ID and corresponding seed value name/ID. These act as input data seeds.
Parameters Provide one or more parameters with a name/ID and string value. These parameters customize the command execution according to the selected template.

Output

The node outputs JSON data representing the result of the executed command. Specifically, it returns an array of objects under the json key, each containing a data field with the updated information from the triggered resource stack.

The node does not output binary data.

Dependencies

  • Requires an API key credential to connect to a Supabase backend service.
  • Uses the Supabase client to query and update tables such as template, assembler, cmdr, and stack_trigger.
  • Relies on real-time subscriptions to listen for updates on the stack_trigger table to capture command execution results.
  • Requires n8n credentials configured with URL and public anonymous key for the Supabase instance.

Troubleshooting

  • Common issues:

    • Failure to load options for templates, parameters, seed parameters, or assemblers may indicate incorrect or missing API credentials.
    • Errors during command execution or subscription setup could be due to network issues or misconfigured Supabase tables.
    • If no output is returned, ensure that the selected template and assembler exist and that the seed parameters and fields are correctly specified.

  • Error messages:

    • Errors logged from Supabase queries (e.g., error fields in responses) should be checked in the console logs.
    • Subscription errors or timeouts might occur if the real-time channel is not properly established; verify network connectivity and Supabase configuration.

Links and References

Discussion