Setting Up the NordStellar Node in n8n

This guide walks you through installing the NordStellar community node, generating a Platform Integrations API access token, and connecting the two so your workflows can read and resolve NordStellar events.

Prerequisites

Before you begin, make sure you have:

An n8n instance where you can install community nodes. On self-hosted n8n this requires owner or admin access; on n8n Cloud the node must be available through the in-app community node catalog.
Permission in NordStellar to create a Platform Integrations API key.
Access to the NordStellar projects whose events you want to work with in n8n.

ℹ️

Community nodes are installed per n8n instance, not per workflow or per user. Once installed, the NordStellar node is available to everyone who can build workflows on that instance, though each user still needs their own credential to use it.

Step 1: Install the Community Node

Open the community nodes settings

Sign in to n8n as an instance owner or admin.
Open Settings from the left-hand menu.
Select Community Nodes.

Install the package

Click Install a community node.
In the npm package name field, enter:
```
n8n-nodes-nordstellar
```
Acknowledge the risk notice confirming you understand that community nodes are not maintained by n8n.
Click Install.

Confirm the node is available

Open or create a workflow.
Click the + button to open the node panel and search for NordStellar.
The NordStellar node should appear in the results.

Self-hosted instances can also install the package directly with npm install n8n-nodes-nordstellar in the n8n user folder. Restart n8n afterwards so the new node is registered. See the n8n community nodes installation guide (opens in a new tab) for the full set of options.

Step 2: Generate a Platform Integrations API Access Token

The node authenticates with a Platform Integrations API key. If you already have one, skip to Step 3.

Create the API key

Log in to the NordStellar Platform.
Navigate to Settings (opens in a new tab).
Click Platform Integrations API in the settings menu.
Click Create API Key.

Store the key securely

ℹ️

The API key is shown only once, when it is created. Copy it immediately and store it securely — if you lose it, you'll need to generate a new one.

Copy the generated key.
Keep it available for the next step, then store it in your password manager or secrets vault.

For more detail on the API itself, see Platform Integrations API.

Step 3: Create the Credential in n8n

Open the credential form

You can create the credential from either place:

From the node — add a NordStellar node to a workflow, then in the Credential to connect with dropdown choose Create new credential.
From settings — go to the n8n Credentials page, click Add credential, and search for NordStellar Integration API.

Enter the connection details

Fill in the credential fields:

Base URL — the base URL of the Platform Integrations API. Leave the default https://platform-integration-api.nordstellar.com unless NordStellar has given you a different endpoint. Do not include a trailing slash.
Access Token — paste the API key you generated in Step 2. This field is stored encrypted and masked in the n8n UI.

Review the domain restrictions

The credential includes two optional fields that control where it may be used if it is ever referenced from an n8n HTTP Request node:

Allowed HTTP Request Domains — set to Specific Domains by default. The other options are All and None.
Allowed Domains — defaults to nordstellar.com, *.nordstellar.com.

Leave these at their defaults unless you have a specific reason to change them.

ℹ️

Independently of these settings, the credential itself refuses to attach your access token to any request that is not HTTPS or is not addressed to nordstellar.com or one of its subdomains. This holds for every request, including credential tests and pagination follow-ups.

Save and test

Click Save.
n8n automatically tests the credential by calling GET /v3/projects?limit=1 against your base URL.
A green Connection tested successfully message confirms the token and base URL are valid.

Step 4: Verify With a Test Run

Confirm end-to-end that the node can read your data.

In a new workflow, add a NordStellar node.
Select the credential you created.
Set Resource to Project and Operation to Get Many.
Click Test step.

You should see one output item per project, each containing that project's identifier and name. Copy a project ID — you'll need it for the Event → Get Many operation.

Once projects are returning, you're ready to build. See the Node Reference for every available operation and parameter, or Example Workflows for complete patterns you can adapt.

Troubleshooting

If the node is not working as expected, review the following:

The NordStellar node doesn't appear in the node panel:
- Confirm the package installed successfully under Settings → Community Nodes.
- On self-hosted instances installed via npm, confirm you restarted n8n after installing.
- Check that community nodes are not disabled on your instance. The N8N_COMMUNITY_PACKAGES_ENABLED environment variable must not be set to false.
The credential test fails:
- Confirm the Base URL has no trailing slash and no /v3 suffix — the node appends the API version itself.
- Confirm the Base URL uses HTTPS and points to a nordstellar.com domain. Any other host is rejected before the request is sent.
- Verify the access token was pasted in full, with no leading or trailing whitespace.
- If the token may have been revoked or rotated, generate a new one in Settings → Platform Integrations API and update the credential.
A request fails with an invalid identifier error:
- Project ID and Event ID must be valid GUIDs. The node validates them before sending the request.
- If you are supplying the value from an expression, confirm the upstream node is producing the identifier itself rather than a whole object.
An operation returns no items:
- For Event → Get Many, confirm the Project ID belongs to a project your API key can access.
- Check the Date Added From and Date Added To filters — a narrow range is the most common cause of empty results.
- Remember that Limit defaults to 50. Enable Return All to page through the complete result set.
Network/Firewall:
- Confirm your n8n instance has outbound HTTPS access to platform-integration-api.nordstellar.com.
- If n8n runs behind an outbound proxy, confirm the proxy permits that host.

If you've checked these details and the problem persists, please contact NordStellar support for assistance.

Getting Started Node Reference