n8n Workflow reviews Brings Approval Gates to Enterprise Automations.

n8n is adding a formal approval layer to workflow publishing, giving Enterprise teams a way to stop unreviewed automations from reaching production. Workflow reviews, available from version 2.36.9, lets organizations require an assigned team member to approve a workflow before it can be published.

The feature addresses a governance problem that becomes harder to ignore as automation spreads through a business. A workflow might begin as a small internal tool, then gain access to customer records, financial systems or AI agents capable of taking actions across multiple services. At that point, publishing a change without a second pair of eyes can carry material risk.

According to the company’s LinkedIn announcement, teams can make reviews mandatory. An assigned reviewer can then sign off on the workflow or request changes through comments.

Workflow reviews introduces a controlled handoff between building and publishing. Rather than coordinating approval through chat messages, tickets or a separate document, teams can keep the review process attached to the automation itself.

The basic process is straightforward:

• A builder creates or updates a workflow.
• The workflow is submitted to an assigned reviewer.
• The reviewer examines the changes and leaves comments where necessary.
• The reviewer either approves the workflow or requests revisions.
• When reviews are required, publication depends on that sign-off.

The feature also includes a workflow diff view. That is an important part of the release because visual automations can become difficult to audit once they contain many nodes, branches and configuration changes. A reviewer needs to understand what changed, not simply inspect the latest version from scratch.

n8n’s documentation for reviewing workflows currently labels the capability as Preview and places it alongside the platform’s workflow management features, including change history, sharing, tags and settings. The available source material does not specify whether administrators can configure different review rules for individual projects or workflow types.

Approval gates are especially relevant as n8n expands beyond conventional app-to-app automation into agent-based systems. The platform has recently added integrations for more complex AI operations, including an Amazon Bedrock AgentCore node for managed multi-agent workflows and a Statista node for automated research and fact-checking.

Those workflows can involve more consequential behavior than moving data between two databases. An agent might call external APIs, send messages, update business records or use credentials with broad permissions. Peer review does not eliminate those risks, but it can catch incorrect branching, unintended access, changed prompts and questionable integrations before publication.

For smaller teams, the feature also offers a more practical form of separation of duties. A founder or operations lead can build an automation while another technically responsible person verifies it. Agencies and consultants could similarly use the review step when handing workflows between builders and client stakeholders, although the Enterprise requirement may limit its relevance for smaller deployments.

Workflow reviews is therefore less about making workflow creation faster and more about making automation change management defensible. As n8n deployments become shared infrastructure, the ability to show who reviewed a change, discuss revisions and compare versions becomes increasingly useful.

What is n8n Workflow reviews?

Workflow reviews is an Enterprise feature that lets teams require peer approval before publishing an n8n workflow. An assigned member can approve the workflow or request changes through comments, while a diff view helps reviewers compare modifications.

Which n8n plan and version supports Workflow reviews?

The feature is available to n8n Enterprise customers starting with version 2.36.9. n8n’s documentation currently marks workflow reviewing as a Preview capability.

What changes when reviews are required?

A workflow can no longer move directly from editing to publication without the assigned reviewer’s sign-off. If the reviewer identifies a problem, they can request changes and communicate through comments before approval.