N8N Workflow

Trigger and manage N8N automation workflows directly from your agent

Dev Tools✓ SafeIntermediatev1.7.0
Last verified:March 2026

About

N8N Workflow connects your OpenClaw agent to your N8N automation instance, letting the agent trigger workflows, pass data between systems and monitor automation runs through plain conversation. If you already use N8N for business automation, this skill turns your agent into the intelligent orchestration layer on top — deciding which workflows to trigger based on context rather than fixed schedules. Particularly powerful for teams using N8N as their backend automation layer who want to add AI decision-making on top.

Use Cases

  • Agent triggers the right N8N workflow based on what you ask it in plain English
  • Pass data collected by your agent directly into N8N for further processing
  • Monitor N8N workflow run status and alert you when something fails
  • Replace fixed cron schedules with agent-driven workflow triggering based on conditions

What N8N Workflow can access

Broad access

Read this skill's SKILL.md in full before installing it. Run it against a disposable host or test account first, and give it the narrowest credentials that still work.

  • Runs commands on the host

    This skill executes commands on the machine running the agent. That is the broadest permission you can grant: anything the agent user can do, this skill can do.

    This skill's own description refers to "cron"

  • Needs your credentials

    You must supply secrets for this skill to work. A skill with a valid key can do anything that key permits, so scope each one as narrowly as the provider allows and never reuse an admin key.

    Declares 2 required credentials: N8N_API_KEY, N8N_BASE_URL

These permissions are inferred from this listing — the credentials it declares, any maintainer warning, and the operations its own description mentions. ClawVault has not audited this skill's source code. Treat it as a starting point for your own review, not a substitute for one.

Installing N8N Workflow on OpenClaw

An OpenClaw skill is a directory containing a SKILL.md file: Markdown with YAML frontmatter. At startup OpenClaw scans the eligible skill directories and injects a compressed description of each skill into its system prompt, so the agent knows what it can do and invokes a skill when a request matches.

  1. 1

    Find the skill in the registry

    openclaw skills search n8n-workflow

    ClawHub is the public registry for OpenClaw skills. Searching first gives you the exact owner-qualified reference, which is what the install command needs. Omit the query to browse the default feed.

  2. 2

    Check what it does and who published it

    openclaw skills verify @<owner>/n8n-workflow

    verify prints ClawHub's verification envelope, including its scan decision and, when available, a commit-pinned source URL. Add --card to read the generated Skill Card instead. Substitute the owner handle returned by the search above.

  3. 3

    Install it

    openclaw skills install @<owner>/n8n-workflow

    Native ClawHub skills use an @owner/slug reference. By default this installs into the active workspace skills/ directory; add --global to install into the shared managed directory instead. You can also install from Git with git:owner/repo, or from a local folder with ./path.

  4. 4

    Confirm the agent can see it

    openclaw skills check

    check reports which ready skills are actually visible to the agent's prompt surface, which is the quickest way to catch a skill that installed but did not load.

Commands follow the official OpenClaw documentation. Placeholders such as <owner> are filled in by the search step, because registry references are publisher-scoped.

Requirements

API Keys & Credentials

N8N_API_KEYN8N_BASE_URL

Version & Updates

Current Version
1.7.0
Last Updated
March 24, 2026
What's New

N8N workflow orchestration, dynamic trigger system, improved data passing

Safety & verification

Listed as safe
No known issues reported for this skill in the OpenClaw ecosystem.

How OpenClaw screens skills

Since February 2026 ClawHub screens submitted skills with VirusTotal: each bundle is hashed and looked up, new bundles are scanned with Code Insight, and results drive an approve, warn or block decision with daily re-scanning. This materially reduces supply-chain risk but does not eliminate it, and independent research has found that different scanners frequently disagree about the same skill. Read the SKILL.md of anything you install, especially if it requests shell access or credentials.

Recommended

Running on a VPS?

Deploy OpenClaw, Hermes, or PicoClaw on Bluehost with the right template for the job.

Related Skills in Dev Tools