N8n Dispatch

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Note

ASI02: Tool Misuse and Exploitation

What this means

If the configured n8n workflow performs actions, a dispatch can trigger real workflow or device changes; malformed or unusual prompt text may also confuse the downstream payload parser.

Why it was flagged

The command forwards user-controlled request type and prompt text to the n8n MCP service. This is the skill's purpose, but action workflows should be scoped, and manual JSON construction can be brittle if prompts contain special characters.

Skill content

type=$(arguments requestType)
prompt=$(arguments text)
payload="{\"requestType\":\"$type\", \"text\":\"$prompt\"}"
openclaw mcporter call --name "n8n_dispatch" --payload "$payload"

Recommendation

Use this only with a trusted, scoped n8n_dispatch workflow; validate requestType and prompt handling in the workflow, and add confirmation or guardrails for action requests.

Note

ASI07: Insecure Inter-Agent Communication

What this means

Prompt contents may leave OpenClaw and be processed by the configured n8n service; if HTTP is used over an untrusted network, that traffic may not be encrypted.

Why it was flagged

The skill relies on a configured MCP/n8n endpoint and the documented example uses an HTTP URL. Prompts are intentionally sent to that service.

Skill content

openclaw mcporter add \
  --name "n8n_dispatch" \
  --url "http://your-n8n-host:8080/api"

Recommendation

Register only a trusted endpoint, prefer localhost/private-network access or HTTPS where possible, and avoid sending sensitive prompts unless the n8n service is intended to receive them.