n8n MCP integration for AI agents.

Connect AI agents to n8n through 36 structured actions, including get data table, create data table, archive workflow, and activate workflow. Review authenti…

ACTION CONTRACTS
36
AUTHENTICATION
API key
SOURCE STATUS
Provider-backed

CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE

CAPABILITY PROFILE

What the n8n integration exposes

The n8n Agent App exposes 36 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve one n8n data table by id, create an n8n data table with columns, and archive an n8n workflow. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.

A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.

For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected n8n account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real n8n capabilities.

Showing 12 of 36 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

get_data_tableREAD

Retrieve one n8n data table by ID.

INPUTS: dataTableId

create_data_tableWRITE

Create an n8n data table with columns.

INPUTS: name / columns / projectId

archive_workflowHIGH IMPACT

Archive an n8n workflow.

INPUTS: workflowId

activate_workflowREVIEW

Activate or publish an n8n workflow.

INPUTS: workflowId / versionId / name / description

create_data_table_columnWRITE

Add a column to an n8n data table.

INPUTS: dataTableId / name / type / index

create_tagWRITE

Create an n8n tag.

INPUTS: name

create_variableWRITE

Create an n8n variable for workflow runtime configuration.

INPUTS: key / value / projectId

deactivate_workflowREVIEW

Deactivate an n8n workflow.

INPUTS: workflowId

delete_data_tableHIGH IMPACT

Delete an n8n data table.

INPUTS: dataTableId

delete_data_table_columnHIGH IMPACT

Delete a column from an n8n data table.

INPUTS: dataTableId / columnId

delete_tagHIGH IMPACT

Delete an n8n tag.

INPUTS: tagId

delete_variableHIGH IMPACT

Delete an n8n variable.

INPUTS: variableId

INPUT CONTRACTS

Know what the action needs before it runs.

get_data_table

dataTableIdREQUIRED
The n8n data table identifier.

create_data_table

nameREQUIRED
The data table name.
columnsREQUIRED
Columns to create in the table.
projectIdOPTIONAL
An n8n resource identifier.

archive_workflow

workflowIdREQUIRED
The n8n workflow identifier.

activate_workflow

workflowIdREQUIRED
The n8n workflow identifier.
versionIdOPTIONAL
The specific workflow version ID to activate.
nameOPTIONAL
An optional name for the workflow version.
descriptionOPTIONAL
An optional description for the workflow version.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Get Data Table

Retrieve one n8n data table by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

get_data_table

Control Create Data Table

Create an n8n data table with columns. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.

create_data_table

Verify with Create Data Table

Create an n8n data table with columns. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

create_data_table

SAFETY BOUNDARY

Operate n8n with explicit limits

  • Authorize n8n with API key and grant only the provider access required by the selected actions.
  • 17 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
  • Treat `archive_workflow`, `delete_data_table`, and `delete_data_table_column` as high-impact operations and require an explicit approval boundary.
  • No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in n8n rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the n8n task completed successfully.

CONNECTION MODEL

API key

n8n API key sent with the X-N8N-API-KEY request header. Create or view API keys in n8n user settings: https://docs.n8n.io/api/authentication/.

Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.

READ SIGNALS
13
WRITE SIGNALS
12
HIGH IMPACT
5
REVIEW SIGNALS
6

EVIDENCE AND AVAILABILITY

Provider reference

Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by n8n.

Official n8n website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS