Lilypad Generic Job icon

Lilypad Generic Job

Execute custom Lilypad job

Overview

The "Lilypad Generic Job" node allows users to execute custom jobs on the Lilypad platform by specifying a module and providing custom inputs. This node is useful when you want to run specific Lilypad modules dynamically with tailored input parameters, enabling flexible integration with Lilypad's job execution capabilities.

Common scenarios include:

  • Running a predefined Lilypad module (e.g., "cowsay:v0.0.3") with user-defined inputs.
  • Automating workflows that require dynamic execution of different Lilypad jobs based on input data.
  • Integrating Lilypad job results into larger n8n workflows for further processing or decision-making.

Example: You might use this node to run a text transformation module on Lilypad where the module name and inputs are set dynamically, then use the output in subsequent workflow steps.

Properties

Name Meaning
Module The identifier of the Lilypad module to execute, e.g., "cowsay:v0.0.3".
Inputs A collection of custom input key-value pairs to pass to the Lilypad module during execution. Each input has:
- Name: The input parameter name expected by the module.
- Value: The corresponding value for that input parameter.

Output

The node outputs an array of JSON objects, each representing the result of executing the specified Lilypad job for each input item. The structure of each output item is:

{
  "json": {
    // The response returned from the Lilypad job execution,
    // containing the processed data or results from the module.
  }
}

If the node encounters errors and is configured to continue on failure, the output may also include an error field describing the issue alongside the original input data.

The node does not explicitly handle binary data output.

Dependencies

  • Requires valid credentials for accessing the Lilypad API (an API key or token).
  • Depends on the external function queueLilypadJob from a shared commons module to enqueue and execute the job on Lilypad.
  • The node expects the Lilypad service to be reachable and the specified module to exist and be accessible via the provided credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Specifying a non-existent or incorrectly named module will result in errors from the Lilypad API.
    • Incorrect input names or values may cause the job to fail or return unexpected results.

  • Error messages:

    • Errors thrown during job execution are wrapped as operation errors with the item index for easier debugging.
    • If "Continue On Fail" is enabled, errors are included in the output per item instead of stopping the workflow.

  • Resolution tips:

    • Verify that the API credentials are correctly configured and have necessary permissions.
    • Double-check the module name and version string for correctness.
    • Ensure input names match those expected by the Lilypad module.
    • Use the error details in the output to identify and fix input or configuration issues.

Links and References

Discussion