Book a build call
Back to Help
Guide

Connect n8n, OpenClaw or your own script

5 min read

You may already run work on your own computer: an n8n workflow, OpenClaw, or a script you call from the command line. NetShow can bring that helper home to your agent. Your agent stays the one your visitors meet. It is voice-first and hands-free: it speaks first in NetShow's own voice, the visitor's microphone opens only after the visitor taps, and typed chat sits in the small menu for people with no microphone or speaker. Your helper works behind it, and it only sees the questions you choose to send it.

For the big picture of the Harness, read One face, many brains. This guide walks the two pages you use to connect one of these three.

Open the recipes page

Open your agent's Harness agents board (/dashboard/agents/{id}/outside-agents). The recipes page sits at the same address with /recipes on the end. Its heading is Bring your agents home, and it says it plainly: Only the work you address to your harness leaves with it. Connecting does not share your avatar's memory or let a harness spend through NetShow.

Each helper has its own card with a status in bold and the date it was last checked. The three this guide covers are marked Ready. Codex and Claude Code are marked Ready too; they have their own cards. Back to harness agents returns you to the board.

What each card asks of you

n8n. The card asks you to run your own n8n agent on your computer with the command you already use for it. It shows a connector command with a placeholder, "<your CLI command>". Replace the placeholder with that local command. You need a local command that starts your n8n work; NetShow does not supply the workflow.

OpenClaw. You need OpenClaw already set up on the computer where you run the connector. The card's command starts OpenClaw for you with a fixed command, so there is no placeholder to fill in. If OpenClaw is not installed there, the connector says so and stops before it connects.

Headless CLI agent. This card starts with a test: Try the echo connector on your own computer. It returns your text so you can check the connection without a model call. Once that works, the card explains that the --exec option can connect a headless CLI agent that you run with your own account.

The n8n and OpenClaw cards say what the local command receives: only your addressed question on its input, and it returns its answer as plain text.

Connect it

Every ready card lists the same four steps. In short:

  1. On the board, under Attach your agent, type an Agent name and choose the Agent family (n8n, openclaw or cli). The cards suggest the name "CLI agent". If you use another name, give the connector the same name with its --name option.
  2. Press Attach. The board shows a code with the line Enter this code in the connector on your own machine. It is shown only here.
  3. Run the connector from its checkout and set its --base option to this NetShow site's address. Paste the board’s private, one-time code only into the connector’s prompt. It expires after five minutes.
  4. Go back to the board. When it says Home. Connected., send one short ask.

The card's own button, which reads "Attach your" and then the helper's name (n8n, OpenClaw or CLI), takes you straight to the board.

Never paste the code anywhere else, and never share it. If you run the connector yourself and want the technical detail, it lives in the Harness Developer Guide.

What the board shows once connected

Your helper appears under Your harness home with its name, its family and the words Home. Connected. Beside it are Reconnect and Detach. Detach disconnects it and clears its relay data.

Under Ask your harness agent, type Your question and press Ask this agent. Only this question goes to your harness. Its answer stays here for you to read. Your helper has 60 seconds to answer, and up to five questions can wait at once.

Only one helper can be home with an avatar at a time. The board says so under Attach your agent: One harness agent can be home with this avatar. It receives only the text you choose to send to it.

What is not ready yet

The recipes page also shows helpers that cannot connect today, each with its reason and a greyed Connection unavailable button. Hermes, CrewAI, LangGraph and True Forge are Drafted — awaiting review. BetterClaw is Listed — connection unavailable. Grok, Muse, Instinct, DeepSeek Harness and CellCog show No supported connection. A card that is not ready is coming or has no door; it is not broken, and this guide will not tell you to connect it.

Back to the getting-started guides.

Still stuck?

The longer documentation covers models, voice, knowledge, and workflows in depth.

Open the documentation