Implementation Guide | Healthcare

    Reviewing n8n community nodes before they touch PHI in a health system

    Treat every n8n community node as untrusted third-party code sitting in a PHI data path. Before approval, verify its provenance, read its source, analyze its dependencies and outbound network behavior, scope its credentials, and test it with synthetic data. Then record an approve, restrict or reject decision with evidence. This review is necessary but not sufficient, because approved nodes change through updates and behave differently on live data. Runtime policy enforcement on tool calls covers what review cannot.

    A six-step pre-approval review

    1. 1

      1. Establish provenance

      Identify the publisher, the source repository, and whether the published package matches that repository. Note maintainer history and how recently the code was changed.

    2. 2

      2. Read the source

      Inspect install scripts, dynamic code execution, obfuscated code, file system access, and every place the node reads workflow data or credentials.

    3. 3

      3. Analyze dependencies

      Generate the full dependency tree, scan for known vulnerabilities, and check licenses. Transitive packages are in scope.

    4. 4

      4. Map data egress

      List every outbound host the node can contact. Compare observed traffic in a test environment with what the code and documentation claim.

    5. 5

      5. Scope credentials

      Define the narrowest credential the node needs. Confirm it does not log, forward or persist secrets, and that no shared or administrative credential is required.

    6. 6

      6. Test in isolation

      Run the node against synthetic data in a network-restricted environment, then pin the version and record the result.

    Why a community node is a PHI risk

    A community node is code written by a third party that executes inside your workflow. It receives the data the workflow passes to it, can use the credentials the workflow holds, and can reach whatever network paths the host allows. When the workflow carries PHI, the node is part of the PHI data path whether or not anyone mapped it that way.

    Three failure modes matter. The node can read PHI it does not need. It can transmit data to an endpoint outside your control. It can handle credentials unsafely, for example by sending them to a third party or holding broader access than the task requires. Informal review, such as a quick look at a repository's star count, rarely addresses any of these and produces nothing an auditor can examine.

    The Security Rule's maintenance requirement at 45 CFR 164.306(e) expects you to review and modify security measures as needed and to update the documentation of those measures. A node review that leaves a durable record, and is repeated when something changes, fits that expectation better than a one-time approval in a chat thread.

    Making the decision: approved, restricted or rejected

    Reject a node when its provenance cannot be established, its code contains unexplained network calls or obfuscation, or it requires credentials broader than its function justifies. Reject also when it has dependencies with unresolved serious vulnerabilities and no maintainer response.

    Approve a node for PHI workflows only when every step is clean, the version is pinned, and the egress list is short and explained. Restricted approval is the useful middle category. A node might be approved only for workflows that never carry PHI, only with a specific scoped credential, only with outbound access limited to a named host, or only with human sign-off on certain actions. Write the restriction into the record so it can be enforced rather than remembered.

    Assign a named approver and a re-review trigger to every decision. Triggers should include any node version change, any change to the n8n version or relevant settings, and any new vulnerability disclosed in the node's dependencies.

    The platform version and settings are part of the review scope

    A node review is only as sound as the platform it runs on. Recent n8n vulnerability records show that platform behavior can change what a node, or an attacker, can do.

    CVE-2026-65598 describes a crafted repository planted in the community node directory that n8n loads as a custom node on the next restart, executing arbitrary JavaScript on the server. Affected versions are those before 1.123.64, and from 2.0.0 before 2.29.8. CVE-2026-65595 affects versions before 2.30.1 and 2.29.8: tokens issued through the Token Exchange module receive all Public API key scopes regardless of the user's role, and where unverified Community Package installation is enabled this can lead to remote code execution.

    Credential handling is also a platform matter. CVE-2026-85166 describes credential references in nodes that execute inline sub-workflows, such as the Workflow Tool node, not being validated before n8n 2.35.4 (and 2.36.x before 2.36.2). A user could persist a node referencing a credential they do not own. CVE-2026-27497 shows a built-in node, Merge, becoming a code execution path for users who can edit workflows. The advisory's mitigations are to limit workflow edit rights to fully trusted users and to add the node to NODES_EXCLUDE.

    The practical implications: record the exact n8n version and compare it with the fixed-version thresholds above, disable unverified Community Package installation unless it is specifically needed, restrict who can create and edit workflows, and use NODES_EXCLUDE to disable nodes that are not approved for PHI workflows.

    What belongs at review time and what belongs at runtime

    Review-time controls answer the question of whether a node should be allowed to exist in a PHI workflow. Provenance, code reading, dependency scanning, egress mapping, credential scoping, version pinning and the approval record all belong here. So do platform controls such as NODES_EXCLUDE and edit-rights restrictions.

    These controls share a limit: they describe the node at one moment. A maintainer can publish an update after approval. A node can behave differently with real PHI than with synthetic data, and a workflow can be edited to pass it more data than the reviewer assumed. The Security Rule also expects procedures to regularly review records of information system activity, such as audit logs, access reports and security incident tracking reports. A review file written before deployment cannot supply that.

    Runtime controls act on what actually happens when the workflow runs. Enforcement in the execution path can evaluate each tool call against policy and then allow it, redact PHI from the payload, block it, or escalate it for human approval. This is how a restricted approval becomes enforceable: a node limited to one host is blocked from contacting any other, and a call that would send identifiers outside the approved scope is redacted or stopped. Each decision also produces a record of what was attempted and what the policy did, which is the evidence regular activity review depends on.

    The proposed January 2025 HHS NPRM, which as of November 2026 remains a proposal and not a current requirement, describes risk analysis being reviewed and updated in response to environmental or operational change, and review of asset inventories and network maps to locate where ePHI is handled. Teams that already maintain a PHI data-flow map per workflow will find this review process consistent with that direction.

    Where Trussed fits

    Trussed enforces policy in the execution path across models, agents, tools and MCP servers, at the level of individual interactions and tool calls. Policy decisions are allow, redact, block, rate limit, or escalate for human approval. They are enforced at runtime, not reviewed after the fact. Enforcement generates continuous audit-ready evidence mapped to HIPAA, including audit controls under 164.312(b). Trussed also provides code provenance, covering the origin, licence and security context of code, which supports the provenance and dependency steps above.

    Trussed can be self-managed in the customer cloud, with configurable retention and data residency, and it runs in production with healthcare and pharma organizations. It complements the review described here and does not replace it. A node still needs to be vetted before approval, and the runtime layer constrains and evidences what the approved node does afterward.

    Community node review path

    Provenance and source

    Who publishes it, what the code does, what it pulls in.

    Egress and credentials

    Where data can go and what the node can authenticate as.

    Decision

    Approved, restricted or rejected for PHI workflows.

    Runtime enforcement

    Allow, redact, block or escalate on live tool calls, with evidence.

    Constrain and evidence approved nodes at runtime

    Talk through how enforcement on tool calls and audit-ready evidence can support your n8n node approval process for PHI workflows.

    Explore Agent and Tool-Call Enforcement
    Next step

    How does your AI governance program compare?

    See where your program has gaps in less than 2 minutes.