n8n CI guide

Validate n8n workflows before they reach production.

Exported n8n workflows are JSON, which means a pull request can review more than syntax. A lightweight preflight can flag structural mistakes and risky configuration before somebody imports or deploys the workflow.

What a useful preflight should check

A preflight should stay deterministic and conservative. It should not execute the workflow or send its contents to an external service. Useful review signals include:

malformed workflow JSON and missing node structure;
possible hardcoded secret-like values or Authorization headers;
duplicate node names and missing webhook paths;
active exports that deserve review before another environment imports them;
high-impact nodes such as Execute Command or SSH.

Add the free GitHub Action

The open-source n8n Workflow Preflight Action is zero-dependency and emits native GitHub annotations. A minimal workflow looks like this:

name: n8n preflight
on: [push, pull_request]

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: corleoneappsh-create/n8n-workflow-preflight-action@v1
        with:
          path: workflows
          fail-on: error

Point path at one exported workflow or at a directory. Directory scans ignore unrelated JSON files that do not look like n8n workflows.

Start free

Use the public Action first. It is already exercised by a separate public n8n workflow repository on GitHub-hosted runners.

Open the free GitHub Action

What the free check intentionally does not do

A static preflight cannot prove that credentials are valid, that an upstream API is healthy, or that a workflow's business logic is correct. It also cannot know whether a retry is safe after a real failure. Those need runtime context.

When a deeper report is useful

The Reliability Toolkit Pro adds Markdown/JSON reports, broken connection and duplicate webhook checks, domain and credential-type inventory, HTTP/private endpoint review signals, a ready-to-use CI template, and Incident Doctor Pro for failed-run triage.

Full reliability bundle — $29 one-time

Pre-deploy scanner + reports + CI template + Incident Doctor Pro. Automatic digital delivery after checkout.

See Reliability Toolkit Pro Use the workflow audit checklist Read the failure-debugging guide

A practical review flow

Export workflow JSON into a versioned repository.
Run deterministic preflight checks on every push and pull request.
Review blocking findings before importing into the target environment.
Run a real n8n test execution in a safe environment.
If a production run fails, diagnose the saved execution separately instead of rewriting the entire workflow blindly.