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

@mookielianhd/n8n-nodes-infisical

v0.1.4

Published

n8n community node for the Infisical API - manage secrets, folders, projects, environments, dynamic secrets and more

Downloads

322

Readme

n8n-nodes-infisical

This is an n8n community node. It lets you use Infisical — the open-source secrets, certificates and access management platform — in your n8n workflows.

It wraps the Infisical REST API directly (no SDK dependency) and supports managing secrets, folders, projects, environments, secret tags, secret imports, dynamic secrets, machine identities, and audit logs.

n8n is a fair-code licensed workflow automation platform.

Installation Operations Credentials Compatibility Usage Resources

Installation

Follow the installation guide in the n8n community nodes documentation.

In n8n, go to Settings > Community Nodes, select Install, and enter:

@mookielianhd/n8n-nodes-infisical

Operations

| Resource | Operations | | --- | --- | | Secret | Create, Get, Get Many, Update, Delete | | Folder | Create, Get, Get Many, Update, Delete | | Project | Create, Get, Get Many, Update, Delete | | Environment | Create, Get, Update, Delete | | Secret Tag | Create, Get, Get Many, Update, Delete | | Secret Import | Create, Get, Get Many, Update, Delete | | Dynamic Secret | Create, Get, Get Many, Update, Delete | | Identity | Create, Get, Get Many, Update, Delete | | Audit Log | Get Many |

Credentials

This node authenticates with Infisical using Universal Auth (a machine identity Client ID and Client Secret). The node exchanges these for a short-lived access token automatically and refreshes it when it expires.

To set up credentials:

  1. In Infisical, create a Machine Identity and attach the Universal Auth method to it (Organization Settings → Access Control → Identities). See the Universal Auth docs.
  2. Add the identity to the project(s) you want to manage and grant it the required roles.
  3. Copy the identity's Client ID and create a Client Secret.
  4. In n8n, create new Infisical API credentials and fill in:
    • RegionUS Cloud, EU Cloud, or Custom / Self-Hosted (with a Custom Base URL for self-hosted instances).
    • Client ID and Client Secret.
  5. Click Test to verify the connection.

Compatibility

Built and tested against n8n's current declarative node API (n8nNodesApiVersion: 1). Requires a recent version of n8n.

Usage

  • Most operations require selecting a Project (searchable list or manual ID) and an Environment (slug). Dynamic secrets use the project slug and environment slug instead.
  • The Secret → Get Many operation returns decrypted secret values by default. Use the View Secret Value option to disable this. Be mindful of where secret values flow in your workflow.
  • Dynamic Secret → Create takes a JSON Provider object whose shape depends on the provider type (e.g. postgres, redis, aws-iam). Refer to the Infisical dynamic secrets docs for the exact inputs.

Resources

License

MIT