> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leapter.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Call a release from n8n with the Leapter node

> Install the Leapter community node in n8n, sign it in to your runtime cluster, and run a blueprint.

The Leapter node runs a blueprint of a deployed release from n8n. On the Leapter SaaS cluster, sign it in with **OAuth2** as yourself.

## Before you start

* A self-hosted n8n (n8n Cloud allows only verified community nodes; this one is not). Tested with n8n 2.44.7 and `n8n-nodes-leapter` 0.2.0.
* A deployed application ([Deploy a release and call it](https://docs.leapter.com/rc/user-guide/deploy-and-call.md)).
* Roles in the environment: operator, plus admin for a key (customer-hosted cluster only) and auditor for **Runs**.

## Steps

**1. Install the node**

In n8n, open **Settings**, **Community nodes**, **Install a community node**. Enter `n8n-nodes-leapter`, tick the risk note, click **Install**. You should see "1 node: Leapter".

**2. Connect the node**

Add the **Leapter** node, click **Connect to Leapter** and pick the way at the top right. Under **Advanced Settings**, enter your cluster address (`https://cluster.example.com`) as **Leapter Server**.

* **OAuth2**: **On the SaaS cluster, and on a customer cluster too.** Enter **Sign-in Server** and **Client ID** from your administrator, who registers the **OAuth Redirect URL** shown. Click **Connect**, sign in, click **Allow**.
* **Service Account Key**: **Paying customers on their own cluster only.** The SaaS cluster has no service account for n8n. In the Admin UI, click **Service accounts**, **Open** next to the service account your cluster has for n8n (such as `n8n`), **Create key**. Paste it as **Service Key**, click **Save**. You should see "Connection tested successfully"; a revoked key shows "The cluster refused this service key".

**3. Choose the blueprint**

Choose the **Project** and **Blueprint Name or ID**. On first use of a project, fields take up to a minute. Fill in **Values to Send**.

![The parameters of the Leapter node: Credential Leapter account, Project insurance-claim-triage, and Blueprint Name or ID Insurance Claim Triage with a green ring. Below, Input Mode Visual Mapping, Mapping Column Mode Map Each Column Manually, and the heading Values to Send.](https://mintcdn.com/leapter/3NthIZmfsFFgUhyn/rc/user-guide/images/n8n-node-blueprint.png?fit=max\&auto=format\&n=3NthIZmfsFFgUhyn\&q=85\&s=5d25cd194ac70154076034d606df714a)

The Leapter node with its project and blueprint.

**4. Run**

Click **Execute workflow**. The output shows `outputData` and a `runId`.

**5. Find the run**

**Executions** shows the execution ID, such as `ID#1`. In the Admin UI under **Runs**, your run has the number of this ID as its **Correlation ID**, here `1`.

## Result

n8n runs the blueprint on the runtime cluster.

## What to do next

* [Find a run and read usage](https://docs.leapter.com/rc/user-guide/runs-and-usage.md): the run's input and output.
* [Create and revoke an evaluation key](https://docs.leapter.com/rc/user-guide/evaluation-keys.md): the keys the node made.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.