🚧 Beta Testing 🚧

🧠 n8n-nodes-function

• 📦 Features
• 🛠️ Installation
• ℹ️ Notes
• 🔎 Similarities to n8n's Execute Workflow
  • ⚡ Function trigger (similar to When Executed by Another Workflow)
  • ➡️ Call Function (similar to Execute Workflow)
• 🎓 Getting Started

Blueprint-style function system for n8n, inspired by Unreal Engine 5.

Define reusable logic blocks with Function, call them with Call Function, and return values with Return From Function.

📦 Features

• 🧱 Define reusable logic with named Function nodes
• 📞 Call functions with dynamic parameters using CallFunction
• 🔁 Return values cleanly using ReturnFromFunction
• 🧬 Nested function calls - functions can call other functions with isolated return values
• 🌍 Global functions - share logic across workflows

🛠️ Installation

ℹ️ Notes

👋 Hey n8n team devs, feel free to take these ideas and build this into n8n 😉 <3

• 🟢 Functions only work on Active workflows.

• 🔃 To detect changes to new/existing Function nodes, toggle the workflow off/on.

  The Call Function and Return from Function do not require toggle workflow after changes.
  But function names/params from Function nodes require toggling the active state.
  It's not an intentional choice, it's just a limitation of how trigger nodes work in n8n.

• ▶️ Functions appear as separate Executions.

  Again, this is not an intentional choice, it's just how n8n works with trigger nodes.

• Both standard and queue mode are supported

  In queue mode, Redis streaming is used.

🔎 Similarities to n8n's Execute Workflow

Functions are a way of organizing reusable logic in n8n, similar to the Execute Workflow node.

They allow you to define a set of operations that can be called with parameters, and return values cleanly.

The main difference is that Execute Workflow encapsulates an entire workflow, while Function nodes can live alongside other nodes in the same workflow.

It's just a different level of abstraction and a different way of organizing logic.

Note: behind the scenes, the implementation may be quite different, but at a high-level of how to organize your workflow logic, they are similar.

⚡ Function trigger (similar to When Executed by Another Workflow)

One limitation of the When Executed by Another Workflow node is that it can only be used once in a workflow.

Whereas Function nodes can be used multiple times in a workflow, allowing for a different way of organizing reusable code.

➡️ Call Function (similar to Execute Workflow)

🎓 Getting Started

...
similar to Execute Workflow