Lola Workflow Defination icon

Lola Workflow Defination

Lola Workflow Defination
Join our community

Overview

The Lola Workflow Defination node is designed to retrieve and cache configuration data about workflows within n8n. It allows users to specify a set of parameter names, fetches corresponding workflow information (such as workflow IDs by name), and stores this mapping in the output. Optionally, it can cache the results globally for faster subsequent access. This node is useful when you need to dynamically reference or reuse workflow metadata across different parts of your automation.

Practical examples:

  • Dynamically look up workflow IDs by their names for use in other nodes.
  • Cache workflow configuration data to avoid repeated API calls and improve performance.
  • Share workflow metadata between executions using global static data.

Properties

Name Meaning
Parameters A collection of parameter names (as strings) to look up. Each entry has:
- Name: Parameter name.
Cache Ouput Whether to cache the output data globally for future executions. (true/false)

Output

  • The node outputs an array of items, each with a json field.
  • The first item's json will include a property:
    • workflowConfig: An object mapping each specified parameter name to its corresponding workflow ID (or value).

Example output:

[
  {
    "json": {
      "workflowConfig": {
        "MyWorkflow1": "12",
        "MyWorkflow2": "34"
      }
    }
  }
]

If caching is enabled and valid cached data exists, the node will return the cached workflowConfig instead of making new API requests.

Dependencies

  • No external services or API keys are strictly required.
  • The node uses n8n's internal API to list workflows.
  • If caching is enabled, it relies on n8n's global static data storage.

Troubleshooting

Common issues:

  • Missing or incorrect parameter names: If a specified parameter name does not match any workflow, it will not appear in the output.
  • Cache not updating: If you change workflow names or IDs but have caching enabled, you may receive outdated data. Disable caching or clear the cache to refresh.
  • Empty output: If no parameters are provided, or none match existing workflows, the workflowConfig object will be empty.

Error messages:

  • Errors related to missing properties or failed API requests may occur if the n8n instance is misconfigured or lacks necessary permissions.

Links and References

Discussion