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

@skhema/n8n-nodes-skhema

v0.2.0

Published

n8n community node for Skhema — the strategy platform. Trigger on new users and workspace members, create workspaces and elements, and complete member compliance.

Downloads

570

Readme

@skhema/n8n-nodes-skhema

An n8n community node for Skhema — the strategy platform. Trigger workflows when people join your organization or workspaces, and create workspaces, strategy elements, and compliance completions from any n8n workflow.

The node mirrors Skhema's Zapier and Make integrations exactly (same triggers, actions, field semantics, and output shapes), so an automation recipe built on one platform replicates on the others.

Installation · Credentials · Triggers · Actions · Example · Resources


Installation

Follow the n8n community nodes installation guide: in your n8n instance, go to Settings → Community Nodes → Install and enter @skhema/n8n-nodes-skhema.

Self-hosted n8n requires Node.js 20.19–24.

Credentials

The node authenticates with Skhema OAuth2 (Authorization Code + PKCE, as a public client — no client secret). A connection represents your Skhema organization.

  1. In Skhema, have an organization owner or admin register your n8n instance's OAuth callback URL under Connections: https://<your-instance>/rest/oauth2-credential/callback (for n8n Cloud: https://<workspace>.app.n8n.cloud/rest/oauth2-credential/callback). Skhema refuses OAuth flows targeting unregistered callbacks — this is what ties a connection to your instance.
  2. Add a new Skhema OAuth2 API credential in n8n. The Client ID is prefilled (Skhema's shared public client) and there is no secret to enter; the endpoints and scopes are pre-configured.
  3. Click Connect and authorize as an organization admin or owner, selecting the organization the connection should act for.

Trigger node — Skhema Trigger

Instant, webhook-backed trigger — no polling. Subscriptions are registered automatically when the workflow is activated and removed when it is deactivated. Pick one or both events:

| Event | Fires when | Payload highlights | | ------------------------ | -------------------------------- | ------------------------------------------------------------------------------------------ | | New User | a member joins your organization | user_name, user_email, role, joined_at | | New Workspace Member | a member joins a workspace | the above plus workspaceName, membership source, and pendingCompliance (see example) |

The New Workspace Member event also carries has_pending_compliance, pending_compliance_count, and pending_compliance_names — flat fields that are easy to filter on. An optional Workspace parameter restricts the trigger to a single workspace; leave it empty to fire for every workspace in the organization.

Action node — Skhema

| Resource | Operation | What it does | | ---------- | ------------------------------ | --------------------------------------------------- | | Workspace | Create | Create a workspace (name, visibility) | | Workspace | Find | Find a workspace by name or ID | | Element | Create | Create a strategy element in a workspace | | Compliance | Find Requirement | List a workspace's compliance requirements | | Compliance | Complete Member Compliance | Mark a member's compliance requirement as satisfied |

Create Element understands Skhema's component → element-type structure: the element-type options scope to the chosen component. Workspace, member, and requirement fields accept values from dropdowns or — the common pattern — mapped expressions from a trigger, e.g. {{ $json.newState.workspaceMemberId }}.

Example: compliance hand-off

Automate workspace compliance (e.g. NDAs) end to end:

  1. Skhema Trigger — New Workspace Member, filtered on has_pending_compliance being true.
  2. Your e-signature node (PandaDoc, DocuSign, …) sends the document to user_email.
  3. On completion, Skhema — Complete Member Compliance marks the requirement satisfied — mapping workspaceId, newState.workspaceMemberId, and metadata.pendingCompliance[0].id straight from the trigger.

The trigger payload carries everything the completion action needs, so the Skhema side of the workflow is exactly two nodes.

Compatibility

  • n8n on Node.js 20.19–24 (self-hosted)
  • Tested against n8n 2.x

Resources

License

MIT