S2G Integration

OpenClaw is the orchestrator. S2G is the toolbox. Connect to an S2G workflow via WebSocket, auto-discover all nodes, and execute them as tools.

OpenClaw ──WS──▶ S2G (wss://s2g.run/api/openclaw/ws/{nodeId})
                   ├── PasswordGenerator
                   ├── HashGenerator
                   ├── DateMath
                   ├── SqlServer
                   ├── Knowledge Base
                   └── ... 200+ node types

The OpenClaw Node in S2G

The OpenClaw node is a built-in S2G node type (category: AI) that acts as a bidirectional bridge between OpenClaw agents and S2G workflows. It appears in the S2G node catalog as "OpenClaw Agent" and serves two roles:

1. Bridge Endpoint — Provides a WebSocket endpoint (wss://s2g.run/api/openclaw/ws/{nodeId}) that OpenClaw agents connect to. Once connected, the agent can execute any sibling node in the workflow.

2. Data Forwarder — Pushes upstream workflow data to connected OpenClaw agents via Input Forwarding. When the workflow triggers (e.g., from an HTTP webhook, scheduler, or another node), mapped fields are sent to all connected agents as {"type":"data","data":{...}}.

Setting Up the OpenClaw Node

1. Open the S2G designer at s2g.run
2. Create or open a workflow
3. Add an OpenClaw node from the AI category in the node palette
4. Add tool nodes — any nodes you want the agent to access (e.g., PasswordGenerator, HashGenerator, DateMath, SqlServer, Knowledge Base)
5. Connect the OpenClaw node to the tool nodes (the connection wiring tells S2G which nodes to expose)
6. Configure the OpenClaw node (click to open properties):
   • Auth Secret (optional) — If set, the bridge must send {"type":"auth","secret":"..."} as its first message
   • Per-Request Timeout — Maximum time per individual node execution request
   • Input Forwarding — Map upstream node outputs to push data to connected agents
   • Manual Payload — Send ad-hoc JSON payloads to connected agents for testing
7. Start the workflow (▶ button or API: POST https://s2g.run/api/v1/workflows/{id}/start)
8. Copy the Node ID (UUID) from the node properties — this is needed for the bridge connection URL

Live View

The OpenClaw node properties panel includes a Live View that shows:

• Connected clients count
• Real-time execute/result message flow
• Data push events
• Connection/disconnection events

Prerequisites

1. S2G account at s2g.run (or self-hosted instance)
2. A workflow with an OpenClaw node and tool nodes connected to it
3. Workflow running — the WebSocket endpoint only accepts connections while the workflow is active
4. Node.js with ws module: npm install ws

Quick Start

1. Install the bridge

# Copy bridge script to workspace
cp scripts/s2g-bridge.js ~/.openclaw/workspace/s2g-bridge.js
npm install ws

2. Get the OpenClaw node ID