npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-nosilo

v0.1.2

Published

n8n community node for fetching training/requirement completion data from noSilo.

Readme

n8n-nodes-nosilo

Community node for n8n that integrates with noSilo and lets you fetch training/requirement completion data for all users.

🧪 Status: early version (single operation)
Currently supports one read-only operation: fetching requirement results for all users via the GetRequirementResults API method.


Features

  • Simple integration with the noSilo API using Bearer API Key authentication
  • One operation available:
    • Get Requirements Results – returns requirement/training completion status for all users
  • Designed as a clean, focused community node that can be extended with more noSilo operations in the future

Requirements

  • n8n (self-hosted or desktop), version 1.x

  • Node.js ≥ 18 (LTS recommended)

  • A valid noSilo API Key with permission to call:

    GET https://app.nosilo.io/api/api-client/method?action=GetRequirementResults


Installation

1. Install the package

In the directory where you run n8n (for example, where your .n8n folder lives), install the package via npm:

npm install n8n-nodes-nosilo

2. Using with Docker (optional)

If you run n8n via Docker, you have two main options:

  1. Add the package to your custom image, OR
  2. Use the N8N_CUSTOM_EXTENSIONS environment variable and let n8n install the package at startup.

Example:

export N8N_CUSTOM_EXTENSIONS="n8n-nodes-nosilo"
n8n start

Consult the n8n documentation for more details on loading custom/community nodes in Docker.

3. Restart n8n

After installation:

  • Restart your n8n instance.
  • On startup, you should see logs indicating that the n8n-nodes-nosilo package (community node) has been loaded.

Credentials – noSilo API

This node uses a dedicated credential type: noSilo API.

  1. In n8n, go to the Credentials section.
  2. Create new credentials of type noSilo API.
  3. In the API Key field, paste your noSilo API Key.
  4. Save the credentials.

The node will automatically add the following HTTP header to all outgoing requests:

Authorization: Bearer <API_KEY>

You do not need to configure this header manually.


Usage

1. Add the node to your workflow

  1. Open or create a workflow in n8n.
  2. Click the + button on the canvas to add a new node.
  3. Search for noSilo.
  4. Select the noSilo integration.
  5. Inside that integration, choose the Get Requirements Results action.

2. Configure credentials

  1. In the node parameters, find the Credentials section.
  2. Select existing credentials of type noSilo API, or create new ones:
    • Choose noSilo API.
    • Provide your API Key.
    • Save the credentials.

3. Execute the node

  1. Optionally add a Manual Trigger node at the beginning of the workflow.
  2. Execute the workflow (or just the noSilo node).
  3. If everything is configured correctly, the node will:
    • Call the noSilo API using your API Key.
    • Return a list (array) of objects with requirement/training completion data.

The returned data typically includes, among other fields:

  • Requirement information (id, name, classification, categories, etc.)
  • User information (id, full name, email, position, organization structure)
  • Completion status flags
  • Dates (createdDate, startedDate, finishedDate, validTo)
  • Additional assignment and custom fields (depending on your noSilo configuration)

Operation details

Operation: Get Requirements Results

  • Label in node: Get Requirements Results
  • Purpose: Returns completion status of requirements/trainings for all users.
  • HTTP Method: GET
  • Base URL: https://app.nosilo.io
  • Path: /api/api-client/method
  • Query string:
    • action = GetRequirementResults
  • Authentication: Bearer API Key (noSilo API credentials in n8n)

The effective request looks like:

GET https://app.nosilo.io/api/api-client/method?action=GetRequirementResults
Authorization: Bearer <YOUR_API_KEY>
Accept: application/json
Content-Type: application/json

Development

If you want to develop or extend this node locally (for example, add more noSilo operations), you can clone the repository and use the n8n node CLI.

1. Clone the repository

git clone https://github.com/FilipLangiewicz/n8n-nodes-nosilo.git
cd n8n-nodes-nosilo

2. Install dependencies

npm install

3. Build

npm run build

4. Run in dev mode

npm run dev

This will:

  • Start a TypeScript build watcher.
  • Launch a local n8n instance (typically at http://localhost:5678).
  • Load your node from the local dist folder.

Any changes you make to the .ts files (e.g. NoSilo.node.ts, NoSiloApi.credentials.ts) will be rebuilt and picked up automatically while the dev process is running.


Extending the node

At the moment, the node exposes a single operation:

  • Get Requirements Results

You can extend it by:

  • Adding more operations to the properties section (for example different actions or endpoints),
  • Reusing the same noSiloApi credentials type (Bearer API Key),
  • Adding additional parameters (query, path, or body fields) for more advanced use cases.

If you follow the same pattern (declarative routing with routing.request), your new operations will appear as separate actions under the same noSilo integration in n8n.


License

MIT