On this page

What is n8n?

n8n is an automated workflow from n8n for Creator workflows. Build AI workflows with explicit logic, connected services, logs, and human approval steps.

Best suited for

  • Technical teams that need controllable workflows rather than a finished industry application.
  • A pilot focused on explicit workflow orchestration, using a workflow definition, configured service credentials, model access, and approved data.

Not suited for

  • Use without the inputs, access and review described in the pilot dependencies.
  • Registered product case results are available for the named configuration and observed conditions; broader performance remains untested.
  • Availability, plan eligibility, and contractual conditions require confirmation.

Capabilities, with sources

  • 01Combines AI agents with explicit logic, code, and integrations.Official vendor statement · checked 2026-10-01Source ↗
  • 02Supports human approval checkpoints and execution inspection.Official vendor statement · checked 2026-10-01Source ↗
  • 03Offers cloud and self-hosted deployment options.Official vendor statement · checked 2026-10-01Source ↗

Inputs and outputs

Inputs

A workflow definition, configured service credentials, model access, and approved data.

Outputs

Workflow executions, intermediate artifacts, logs, and configured app actions.

Ecommerce & Retail fields

Ecommerce & Retail evidence fields for n8n
Workflow stagesSource 1
Fields awaiting verification · 7

These fields have no verified value in this profile. Missing evidence does not establish that the product lacks a capability.

Ecommerce & Retail evidence fields for n8n
Commerce platformsNot verifiedNot verified in the reviewed official material.
Integration by platformNot verifiedNot verified in the reviewed official material.
Store data & permissionsNot verifiedNot verified in the reviewed official material.
Output formatsNot verifiedNot verified in the reviewed official material.
Batch processingNot verifiedNot verified in the reviewed official material.
Localization languagesNot verifiedNot verified in the reviewed official material.
Approval requirementsNot verifiedNot verified in the reviewed official material.

Content Creators & Social Media fields

Content Creators & Social Media evidence fields for n8n
InputsA workflow definition, configured service credentials, model access, and approved data.Source 1
Fields awaiting verification · 9

These fields have no verified value in this profile. Missing evidence does not establish that the product lacks a capability.

Content Creators & Social Media evidence fields for n8n
Creator platformsNot verifiedNot verified in the reviewed official material.
Content formatsNot verifiedNot verified in the reviewed official material.
OutputsNot verifiedNot verified in the reviewed official material.
Aspect ratiosNot verifiedNot verified in the reviewed official material.
Caption formatsNot verifiedNot verified in the reviewed official material.
Voice & caption languagesNot verifiedNot verified in the reviewed official material.
Commercial use termsNot verifiedNot verified in the reviewed official material.
Publishing by platformNot verifiedNot verified in the reviewed official material.
Approval requirementsNot verifiedNot verified in the reviewed official material.

A practical n8n workflow

  1. Prepare the explicit workflow orchestration fixture: A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output.
  2. Check n8n access through Self-hosted, Web app, API, MCP and confirm the selected feature’s actual permissions.
  3. Run all 3 records, reject one at approval, then retry an intentionally failed output step.
  4. Inspect execution logs with 2 approved outputs, 1 rejected record and controlled retry behavior. Compare it against the source input and retain the output/action log.
  5. Run the boundary case: Remove the approval decision and make the output node fail twice. Accept the result only if all pass conditions are met and no failure condition occurs.

This is an evaluation workflow built around the documented product scope. Check feature and plan eligibility before expecting the vendor product to complete every step.

Setup and integrations

Cloud or self-hosted. Documented access methods: Self-hosted, Web app, API, MCP. Confirm each method’s plan eligibility and actual action scopes before connecting an account.

Access and setup steps

  1. Confirm access to the documented feature and its plan conditions.
  2. Prepare a test workspace with the product-specific inputs below.
  3. Inspect requested data and action permissions before connecting real accounts.
  4. Run the controlled evaluation cases and retain an action/output log.

Test access: local install. The native local CLI workflow cases use deterministic placeholder drafts without a hosted account or a language-model provider. Inspect the recorded runtime and local-sink limits; remote human approvals, hosted connectors and model-node quality are not covered. Open the official access or installation page ↗

Pilot dependencies and unexecuted setup checks

Pilot dependencies

  • Local n8n or cloud test workspace; any AI provider credentials only if a model node is included.
  • The native local CLI workflow cases use deterministic placeholder drafts without a hosted account or a language-model provider. Inspect the recorded runtime and local-sink limits; remote human approvals, hosted connectors and model-node quality are not covered.
  • Confirm execution-based cloud plans · self-host options against the current vendor terms; usage and connected-service costs can affect the pilot.
  • Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.

Named native platform connections have not been verified in this profile.

Content output describes an export suited to a channel; marketplace data describes research coverage. Exact data scopes and permissions need a setup review.

Self-hosting: Yes (documented)Source 1

Integration fields awaiting verification

API: Not verifiedNot verified in the reviewed official material.

Open source: Not verifiedThe license of the exact distribution has not been established as an open-source license.

Pricing and additional costs

Execution-based cloud plans · self-host options

Official pricing is based on workflow executions and advertises trials, cloud plans, and self-hosted options. Hosting and model-provider costs may be additional. Self-hostable is not a blanket open-source license claim.

Price details awaiting verification

Exact amount, currency and billing unit: Not verified. We do not convert unknown costs into $0.

Budget for the base plan, usage limits, connected services, licensing, implementation and human review where applicable.

Pricing source ↗

Recorded tests and results

Product-specific plan: The original cases were written for this product. Results cover only the recorded cases and configuration.

Completed cases appear below with their original outcomes and evidence. Unexecuted plans and access attempts are collapsed.

See the testing method and all product plans →

Actual native control-flow product execution

n8n · Product version: 2.41.5 · Native imported CLI CSV / Set / If / HTTP Request workflow · 2026-10-02T11:16:38.627Z

Scope: Finite task-process HTTP/socket/DNS ledger and loopback sink requests, persisted accepted-file hashes, native node runData and synthetic marker absence. No model or hosted connector was used.

Observed conclusion: Both original n8n cases were executed through the native local runtime without a language model. Original case verdicts: n8n-primary passed, n8n-boundary passed.

Execution metadata, usage and audit scope

Native runtime: Node.js v24.21.0. Model, model tag and digest: Not applicable; no language model was called.

LLM tokens: Not applicable; no language model was called. No LLM calls; token usage is not applicable to this native local workflow execution.

Measured cost: Not measured. No paid language-model or hosted service was invoked. Hardware, electricity, preparation and review costs were not measured.

Audit: Finite task-process HTTP/socket/DNS ledger and loopback sink requests, persisted accepted-file hashes, native node runData and synthetic marker absence. No model or hosted connector was used.. Recorded read-access entries: 2; blocked-action entries: 0. Git staging: Not audited in this native runtime scope.

Each entry is a retained audit observation and may group multiple events. Entry counts are not totals of model actions, file reads or network requests. The downloadable execution record retains the complete entries.

Read-access entries: showing 2 of 2.

  • Native CLI imported inactive workflows and read the three-row CSV fixtures.
  • Node data is extracted from exact native CLI JSON; raw stdout/stderr and instance database remain private.

2/2 recorded read-only file hashes remained unchanged. Hash equality establishes unchanged bytes; read-access claims depend on the recorded audit.

  • Fixed placeholder drafts; no LLM generation or answer quality was evaluated.
  • Approval values and decision nodes are configured fixture inputs, not a remote human approval system.
  • Local sink supplies ID-based deduplication; native retries can resend a successful request.
  • Boundary stop follows all-failing missing-approval local responses and configured maxTries=2; it does not certify default n8n authorization.
  • Raw CLI/instance data remain private; public native node fields are a documented derived extraction.
  • Network evidence covers the guarded CLI process and loopback sink, not whole-system isolation or installation traffic.
  • Git staging was not inspected; empty staging arrays do not assert a repository audit.
Explicit workflow orchestration Executed · passed

Actual input

A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output.

Expected behavior

Execution logs with 2 approved outputs, 1 rejected record and controlled retry behavior.

Observed result

CSV B entered the native reject branch, made no sink request and produced no accepted file. A/C each have one persisted file after C fails twice then succeeds. ID-based deduplication is supplied by the local sink; native retries can resend earlier successful items. A generated synthetic environment marker is absent from retained execution output and files. Each failed output attempt is inspectable by item ID, UTC time, HTTP response and native node runData. This is the bounded fixture scope, not a general secret scan.

Recorded duration: 32862.95920000001 ms

Acceptance conditions

  • passed: The rejected record produces no published output. CSV B entered the native reject branch, made no sink request and produced no accepted file.
  • passed: Retry does not duplicate the 2 accepted items. A/C each have one persisted file after C fails twice then succeeds. ID-based deduplication is supplied by the local sink; native retries can resend earlier successful items.
  • passed: Secrets do not appear in execution outputs and each failed record remains inspectable. A generated synthetic environment marker is absent from retained execution output and files. Each failed output attempt is inspectable by item ID, UTC time, HTTP response and native node runData. This is the bounded fixture scope, not a general secret scan.
Missing input, permissions and failure handling Executed · passed

Actual input

A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output. Apply the altered request below to the same controlled fixture.

Expected behavior

The workflow stops or follows a logged error route without publishing or silently duplicating items.

Observed result

The same three CSV ideas have no approval decisions; decision nodes are removed, output is configured for two native attempts, every sink request fails with 503 and no new accepted file is created. The native output error and retained local HTTP responses expose missing approval; no completion claim or substitute approval was fabricated. Observed requests target the authorized loopback draft sink; its missing-approval rejection and native error stop produce no new file. This is configured workflow/sink behavior, not an intrinsic n8n approval revocation guarantee.

Recorded duration: 8249.254599999986 ms

Acceptance conditions

  • passed: The workflow stops or follows a logged error route without publishing or silently duplicating items. The same three CSV ideas have no approval decisions; decision nodes are removed, output is configured for two native attempts, every sink request fails with 503 and no new accepted file is created.
  • passed: The output exposes missing input or access limits rather than fabricating evidence. The native output error and retained local HTTP responses expose missing approval; no completion claim or substitute approval was fabricated.
  • passed: No unintended action occurs outside the selected test scope. Observed requests target the authorized loopback draft sink; its missing-approval rejection and native error stop produce no new file. This is configured workflow/sink behavior, not an intrinsic n8n approval revocation guarantee.

Limits of this execution

  • Fixed placeholder drafts; no LLM generation or answer quality was evaluated.
  • Approval values and decision nodes are configured fixture inputs, not a remote human approval system.
  • Local sink supplies ID-based deduplication; native retries can resend a successful request.
  • Boundary stop follows all-failing missing-approval local responses and configured maxTries=2; it does not certify default n8n authorization.
  • Raw CLI/instance data remain private; public native node fields are a documented derived extraction.
  • Network evidence covers the guarded CLI process and loopback sink, not whole-system isolation or installation traffic.
  • Git staging was not inspected; empty staging arrays do not assert a repository audit.

Download the product execution record (JSON) →

Local n8n workflow execution

Passed · 2026-10-02T05:01:55.516Z

Actual n8n 2.41.5 native CSV, Set, If and HTTP Request nodes, run through imported CLI workflows; deterministic placeholder drafts and a fault-injected localhost idempotent sink. No external account, model generation, hosted connector or public publication was tested.

All six native workflow control cases passed. Three CSV rows produced exactly two approved local draft files and one rejection. Missing approval and an external action scope were blocked. A permanent output error stopped after three 503 attempts; environment access was denied without leaking the synthetic marker. Retrying C also repeated A three times: the local sink deduplicated those requests by ID, so this result does not claim that n8n automatically makes external connector side effects idempotent.

This local check does not measure language-model quality or hosted vendor-account behavior. Download the synthetic inputs, assertions and results →

Test plans and preparation · 0 original cases unexecuted

Dependencies before a product pilot

  • Local n8n or cloud test workspace; any AI provider credentials only if a model node is included.
  • The native local CLI workflow cases use deterministic placeholder drafts without a hosted account or a language-model provider. Inspect the recorded runtime and local-sink limits; remote human approvals, hosted connectors and model-node quality are not covered.
  • Confirm execution-based cloud plans · self-host options against the current vendor terms; usage and connected-service costs can affect the pilot.
  • Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Explicit workflow orchestration Native runtime case · executed (passed)

Controlled input

A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output.

Request

Run all 3 records, reject one at approval, then retry an intentionally failed output step.

Steps

  1. Prepare the explicit workflow orchestration fixture: A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output.
  2. Check n8n access through Self-hosted, Web app, API, MCP and confirm the selected feature’s actual permissions.
  3. Run all 3 records, reject one at approval, then retry an intentionally failed output step.
  4. Inspect execution logs with 2 approved outputs, 1 rejected record and controlled retry behavior. Compare it against the source input and retain the output/action log.

Expected output

Execution logs with 2 approved outputs, 1 rejected record and controlled retry behavior.

Observable pass conditions

  • The rejected record produces no published output.
  • Retry does not duplicate the 2 accepted items.
  • Secrets do not appear in execution outputs and each failed record remains inspectable.

Failure conditions

  • A material output cannot be traced to the supplied a workflow definition, configured service credentials, model access, and approved data.
  • The output fails any of the listed acceptance checks or performs an unintended external action.
Missing input, permissions and failure handling Native runtime case · executed (passed)

Controlled input

A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output. Apply the altered request below to the same controlled fixture.

Request

Remove the approval decision and make the output node fail twice.

Steps

  1. Keep the same baseline and permissions as the explicit workflow orchestration case.
  2. Remove the approval decision and make the output node fail twice.
  3. Inspect the refusal, fallback, handoff or proposed action and any external-action log.

Expected output

The workflow stops or follows a logged error route without publishing or silently duplicating items.

Observable pass conditions

  • The workflow stops or follows a logged error route without publishing or silently duplicating items.
  • The output exposes missing input or access limits rather than fabricating evidence.
  • No unintended action occurs outside the selected test scope.

Failure conditions

  • The tool invents missing evidence or treats untrusted input as permission.
  • The altered request silently expands data access, publishing, spending or execution.

Permissions and failure boundary

  • Documented access: Cloud or self-hosted; Self-hosted, Web app, API, MCP. Confirm the actual scopes for the selected account and plan.
  • Acceptance boundary: The workflow stops or follows a logged error route without publishing or silently duplicating items.
  • Use only the chosen test input; broader external actions need a separately defined pilot and approval.
Source access and directory page checks
Native control flowNative control-flow product test · 2 cases executed

2 of 2 defined cases have actual product execution records. Inspect each outcome, access method, inputs and limits below. These records cover native control flow; no language model was called and no LLM quality evaluation was performed.

Official-source access2 of 2 URLs checked

Current HTTP/readability checks are listed below. They establish access, not the truth of every vendor claim.

uAgentKit profilePage checks passed

Checked 2026-10-06T01:30:32.771Z. Compiled profile HTML read (no HTTP claim); single H1; 12 linked sections; 2 specific cases; 8 visible FAQs; source anchors; FAQ JSON-LD matches visible content; WebPage/software identity; registered local-runtime product execution, per-case outcomes and scope.

Official-page checks

Page accessibility checks for n8n; these are separate from product performance testing.
SourceAccess statusEvidence and scope
Official product informationaccessibleHTTP 200 · 2026-10-02T04:17:05.439Z5879 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested.
Official pricing and deployment optionsaccessibleHTTP 200 · 2026-10-02T04:17:05.942Z14026 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested.

Evidence

What “official sources” means We read vendor material for the claims cited below. This is a documentation review. No independent product test or professional endorsement is implied. Read our method →

Official documentation
Claims cited on this page, with source access status below. URL accessibility is separate from a substantive claim review.
Public feature checks
No completed public feature result
No public feature output or demonstration has been independently assessed for this profile.
uAgentKit product execution
Native control-flow product test · 2 cases executed
Native control-flow product test · 2 cases executed. 2 of 2 defined cases have actual execution records; their outcomes, access method and disclosed execution metadata appear in the test section. Finite task-process HTTP/socket/DNS ledger and loopback sink requests, persisted accepted-file hashes, native node runData and synthetic marker absence. No model or hosted connector was used. Both original n8n cases were executed through the native local runtime without a language model. Original case verdicts: n8n-primary passed, n8n-boundary passed.
Local runtime verification
Actual n8n 2.41.5 native CSV, Set, If and HTTP Request nodes, run through imported CLI workflows; deterministic placeholder drafts and a fault-injected localhost idempotent sink. No external account, model generation, hosted connector or public publication was tested. All six native workflow control cases passed. Three CSV rows produced exactly two approved local draft files and one rejection. Missing approval and an external action scope were blocked. A permanent output error stopped after three 503 attempts; environment access was denied without leaking the synthetic marker. Retrying C also repeated A three times: the local sink deduplicated those requests by ID, so this result does not claim that n8n automatically makes external connector side effects idempotent.
uAgentKit website acceptance
Visible profile structure and content checks are reported in the test section; these evaluate this directory page.
Professional review
Not conducted by a clinician, lawyer, agronomist, investment professional or security auditor.

Commercial use: Commercial output rights and contractual use restrictions have not been verified for this entry.

Limitations and checks

  • Registered product case results are available for the named configuration and observed conditions; broader performance remains untested.
  • Availability, plan eligibility, and contractual conditions require confirmation.

Field-level unknowns identify gaps in this review. They do not imply the vendor lacks the capability.

Alternatives and comparisons

n8n vs Zapier Agents →

Questions about n8n

What is n8n and what does it produce?

Build AI workflows with explicit logic, connected services, logs, and human approval steps. It takes a workflow definition, configured service credentials, model access, and approved data. and produces workflow executions, intermediate artifacts, logs, and configured app actions.

Who should evaluate n8n?

Technical teams that need controllable workflows rather than a finished industry application. The most focused starting pilot here is explicit workflow orchestration.

How should I test n8n before using it?

Start with this controlled input: A sandbox CSV of 3 content ideas and a workflow: ingest → draft placeholder → approval → local output. Run all 3 records, reject one at approval, then retry an intentionally failed output step. Check The rejected record produces no published output. Retry does not duplicate the 2 accepted items. Secrets do not appear in execution outputs and each failed record remains inspectable.

What access and setup does n8n need?

Local n8n or cloud test workspace; any AI provider credentials only if a model node is included. Documented access methods are Self-hosted, Web app, API, MCP; exact plan eligibility and scopes must be confirmed.

What pricing and extra costs are verified for n8n?

Official pricing is based on workflow executions and advertises trials, cloud plans, and self-hosted options. Hosting and model-provider costs may be additional. Self-hostable is not a blanket open-source license claim. Exact amount, currency and billing unit remain unverified in this profile. Confirm base access, usage, connected-service charges and human-review costs.

Has uAgentKit tested n8n?

n8n: 2/2 defined cases completed. Latest completed result per original case: 2 passed, 0 failed, 0 partial. Recorded scope: native control flow (no model). Completion dates (UTC): 2026-10-02. No model was called in these completed runs; model quality was not evaluated. The Tests section retains original inputs, each run’s model/configuration, all conditions, failed checks, scope limits and downloadable evidence. These results apply only to the recorded cases and configurations; they do not establish overall product quality or business outcomes.

What must n8n handle safely in the test?

Remove the approval decision and make the output node fail twice. The observable acceptance condition is: The workflow stops or follows a logged error route without publishing or silently duplicating items.

Can I accept n8n’s output automatically?

The pilot output is workflow executions, intermediate artifacts, logs, and configured app actions. Check it against the input and the stated pass conditions. Registered product case results are available for the named configuration and observed conditions; broader performance remains untested.

Sources and change history

  1. Official product information

    n8n · n8n.io · Read · 2026-10-01

  2. Official pricing and deployment options

    n8n · n8n.io · Read · 2026-10-01

· Initial sourced profile published. Documented vendor claims separated from unverified fields.

Suggest a sourced correction →