n8n

n8n

Curated major addition platform in workflow automation with material relevance to the Marcom operating stack and a first-party developer surface.

Automation, data & MCP bridgesSystem of orchestrationAgent-accessible SaaS
System roleSystem of orchestration
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Workflow management, workflow building, data tables and explicitly exposed workflow tools; n8n can also consume external MCP servers

02 · Data you can retrieve

Workflow management, workflow building, data tables and explicitly exposed workflow tools; n8n can also consume external MCP servers

03 · Actions and write paths

n8n's first-party MCP/agent surface includes state-changing tools in the documented capability area: Workflow management, workflow building, data tables and explicitly exposed workflow tools; n8n can also consume external MCP servers. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Authentication model is documented by the vendor; inspect the cited source before implementation. Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP.

05 · Monitoring, approval, and recovery

Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP. Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP.

06 · Gaps and implementation limits

Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP.

First-party MCP tool catalog

30 named MCP tools · Instance-level MCP server

The complete 30-tool list in n8n's instance-level MCP reference. It covers workflow discovery and execution, execution records, credential metadata, workflow building and validation, and data tables; it is separate from individual MCP Server Trigger nodes. Reviewed Jul 10, 2026. Cloud and self-hosted instances support OAuth or access-token authentication after an owner or administrator enables MCP. Visibility follows the user, but enabled workflows cannot be scoped differently per connected MCP client. Several tools require recent n8n versions. Separately, n8n's public directory displayed 1,938 integration entries on 2026-07-10; that dynamic total mixes regular, trigger, core, partner-built, and other node types and should not be read as 1,938 connectors maintained or individually verified by n8n.

First-party exact listComplete list on cited pagen8n instance-level MCP server
30 shown
Workflow discovery and operation10
search_workflowsreadget_workflow_detailsreadexecute_workflowconsequential writetest_workflowconsequential writeprepare_test_pin_datareadpublish_workflowconsequential writeunpublish_workflowconsequential writesearch_projectsreadsearch_foldersreadlist_tagsread
Executions and credential metadata3
get_executionreadsearch_executionsreadlist_credentialsread
Workflow building and validation10
get_sdk_referencereadsearch_nodesreadget_node_typesreadget_workflow_best_practicesreadexplore_node_resourcesreadvalidate_workflowreadvalidate_node_configreadcreate_workflow_from_codedraftupdate_workflowwritearchive_workflowwrite
Data tables7
search_data_tablesreadcreate_data_tablewriteadd_data_table_columnwriterename_data_table_columnwritedelete_data_table_columnconsequential writerename_data_tablewriteadd_data_table_rowswrite

Agent access

MCP and adjacent posture

Verified first-party provider MCPBuilt-in n8n MCP server plus MCP server-trigger/client nodesCurrent service

Role: provider

Read scope: Workflow management, workflow building, data tables and explicitly exposed workflow tools; n8n can also consume external MCP servers

Write scope: 13 of 30 reviewed named tools have a write, draft, or mixed action label, including execute_workflow, test_workflow, publish_workflow, unpublish_workflow, create_workflow_from_code, and others. Read each catalog boundary before enabling them.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity2
Governance3
Agent access4
UI extensibility3
Portability4
Observability4
Documentation5

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that n8n ships these experiences.

Single-platform patterns

  • Custom agent and Marcom operations workbench
  • Marcom control plane
  • Data-quality exception console
  • Approved capability registry
Use in the brief composer →

Multi-platform compositions

  • n8n + systems of record: marcom control plane
  • n8n + systems of engagement + interface host or builder: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

7 recorded sources
MCPRepresentative source
https://docs.n8n.io/connect/connect-to-n8n-mcp-server ↗

Official n8n docs confirm native server, tool reference, trigger node and client node; distinguish tenant server from public docs MCP.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory
https://docs.n8n.io/api/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory
https://docs.n8n.io/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://docs.n8n.io/integrations/ ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://n8n.io/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Integration directoryTargeted review
Best app and software integrations ↗

Named catalog evidence used on this profile.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party catalog review

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.