Skip to main content
The Code workflow puts a blueprint’s logic into an n8n Code node as JavaScript. The workflow runs the logic inside n8n and never calls the runtime cluster, so it needs no evaluation key. Use it when an n8n workflow should run a blueprint without a connection to the cluster. To call the cluster instead, use the HTTP workflow (Call a release from n8n).

​
Before you start

  • The application is deployed to the environment (Deploy a release and call it). The Admin UI builds the workflow from the release the environment serves. You need no evaluation key.
  • You can sign in to the Admin UI, and you hold content:read in the environment, for example as an auditor. Without it, the n8n card says “You need the content:read right”.
  • An n8n instance. The steps were run with n8n 2.44.5; other versions may name the menu items differently.

​
Steps

1

Download the workflow

Open the Admin UI (the cluster address followed by /runtime-management/ui/), click Sign in with Leapter and sign in with the account you use for the Lab. The Admin UI may open on another environment: click the environment’s name at the bottom of the sidebar and choose yours in the list that opens. Then click the application’s name on the Status page, and scroll down to the n8n card. Under Blueprints, click Code workflow next to the blueprint. Your browser saves a file such as pizza-pricing-calculator-180269-playground-pizza_pricing-code.json.The card says that the Code workflow runs the logic inside n8n and needs no key. It calls nothing, so it has no X-API-Key header to fill in.
The Admin UI application page, scrolled to the n8n card. Under Blueprints, Pizza Pricing has the buttons HTTP workflow and Code workflow. Code workflow has a green ring.

The Code workflow button of the blueprint Pizza Pricing.

2

Import it into n8n

Sign in to n8n and create a new workflow: click + at the top of the left sidebar, then New workflow. Open the workflow menu (… next to the workflow name), choose Import, then From file, and select the downloaded file.The workflow is renamed to “Code example - Pizza Pricing”. You should see three nodes: Form Trigger, Pizza Pricing and Form. The node Pizza Pricing is a Code node with the blueprint’s logic. Double-click it to read the JavaScript; you do not need to change it. Close the node with × at its top right. You do not need to save or publish the workflow to run it.
An n8n canvas with three connected nodes: Form Trigger, Pizza Pricing with a curly-brace icon and a green ring, and Form with the subtitle Form Ending.

The imported Code workflow, with the Code node Pizza Pricing in the middle.

3

Run the workflow

Click Execute below the canvas. n8n opens the form Input Data in a new tab, with the note “This is a test version of your form”. Fill in the fields:Click Submit.

​
Result

The form shows Run complete and the blueprint’s outputs, the same outputs a call to the runtime cluster returns for these inputs.
An n8n form page that says Run complete: totalPrice 20.9, basePrice 16, toppingsCost 3, crustUpcharge 0, subtotal 19, dayMultiplier 1.1, weeklyPrices 19, 15.2, 17.1, 19, 20.9, 21.85, 19.

The result of the run, shown by the workflow's last node.

The logic ran inside n8n. The runtime cluster received no call, so the Admin UI’s Runs and Usage pages do not show this run. The Code node holds the logic of the release the environment served when you downloaded the file. After a new deploy or a roll back, the workflow still runs the old logic. Download the Code workflow again and import it to get the new one.

​
When to use Code vs HTTP

​
Troubleshooting

After Sign in with Leapter, you are in the Lab and not in the Admin UI, or the Lab says “This sign-in cannot go on.” and “authorization not found”. Open the Admin UI’s address again and click Sign in with Leapter once more. The Status page opens.

​
What to do next