ClawHub

Session OpenClaw Bridge

v0.1.0

Configure, validate, and troubleshoot a Session Messenger ↔ n8n ↔ OpenClaw bridge for two-way text messaging and image exchange when the hosted relay support...

⭐ 0· 112·0 current·0 all-time
by@droidhackzor

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for droidhackzor/session-openclaw-bridge.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Session OpenClaw Bridge" (droidhackzor/session-openclaw-bridge) from ClawHub.
Skill page: https://clawhub.ai/droidhackzor/session-openclaw-bridge
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install session-openclaw-bridge

ClawHub CLI

Package manager switcher

npx clawhub@latest install session-openclaw-bridge
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description align with the bundled artifacts: an n8n workflow template, a small Python relay validator, and packaging/release notes. Nothing in the repository requires unrelated capabilities (no cloud credentials, no unrelated binaries).
ℹ
Instruction Scope
SKILL.md limits actions to workflow import/patch, endpoint verification (/health, /poll, /send, optional /attachment) and packaging. The included script performs only HTTP GET/POST probes against a user-supplied base URL and prints a JSON summary. Note: the validator will POST a test message to /send (body: {"to":"TEST","text":"probe"}) and will probe an attachment URL — so run it against your own test or development relay to avoid generating real messages.
✓
Install Mechanism
No install spec; this is an instruction-only skill with a small script. Nothing is downloaded or written automatically by an installer.
ℹ
Credentials
The skill does not request environment variables or credentials. The n8n workflow contains placeholder variables (REPLACE_SESSION_BOT_HOST, REPLACE_SESSION_BOT_API_KEY, REPLACE_OPENCALW_ENDPOINT and references to $env.*) that the operator must supply; this is expected. There are no hidden or unexpected credential requests in SKILL.md or the script.
✓
Persistence & Privilege
always is false, no autoregistration or system-wide configuration changes are requested. The skill is instruction-only and does not attempt to modify other skills or global agent settings.
Assessment
This skill appears to be what it says: a template and a small validator for a Session ↔ n8n ↔ OpenClaw relay. Before running anything: (1) run scripts against a test/dev instance, not a production bot, because validate_relay.py will POST a probe message to /send and probe /attachment; (2) replace the placeholder host/API key/OpenClaw endpoint in the n8n workflow with your real values and keep any real API keys secret; (3) inspect the workflow and validator output before packaging/publishing to ensure you are not exposing real credentials or endpoints. If you need higher assurance, request the upstream source (GitLab) referenced in release.md so you can verify the relay project and tags.

Like a lobster shell, security has layers — review code before you run it.

latestvk977pex7xypztfbkwhspvw04n183yz9y
112downloads
0stars
1versions
Updated 4w ago
v0.1.0
MIT-0
@droidhackzor
latest
Download

Session ↔ OpenClaw bridge

Use this skill to manage the OpenClaw and n8n side of a Session Messenger relay.

Scope

Handle:

  • n8n workflow generation/import/patching
  • relay health validation
  • endpoint verification for /health, /poll, /send, and attachment download when present
  • mismatch detection between deployed relay and expected API
  • OpenClaw endpoint wiring guidance
  • packaging the skill for reuse or publication

Do not assume the Session relay should implement OpenClaw chat generation internally. Keep the model:

  • relay handles Session connectivity and exposes HTTP endpoints
  • n8n orchestrates polling, filtering, and reply delivery
  • OpenClaw generates replies

Primary files

Read these when needed:

  • references/openclaw-session-relay-workflow.json — n8n workflow template
  • references/release.md — shared publication version for the skill and relay project
  • scripts/validate_relay.py — probe relay endpoints and summarize readiness

Expected relay API

Expected minimum HTTP API:

  • GET /health
  • GET /poll?since=<seq>&limit=<n>
  • POST /send

Optional attachment endpoint for image/file workflows:

  • GET /attachment/:messageId/:attachmentId

Expected /health fields for a correct modern deployment:

  • ok
  • sessionId
  • inboundEnabled
  • queued
  • lastSeq

If /poll returns 404 or /health omits the inbound queue fields, treat the deployed relay as an older/wrong build.

n8n workflow model

Preferred flow:

  1. Cron trigger
  2. Poll Session relay /poll
  3. Extract next cursor
  4. Split messages
  5. Filter allowed sender
  6. POST message text to OpenClaw endpoint
  7. POST reply to relay /send

The relay is text-first but may support image/file exchange when its /health capabilities and implementation confirm attachment receive/send support. Do not promise calls or live media.

OpenClaw endpoint note

Do not invent the OpenClaw HTTP endpoint. Confirm the actual endpoint and payload shape before activation.

Packaging

Current shared release version: 0.1.0

Package with:

scripts/package_skill.py /home/openclaw/.openclaw/workspace/skills/session-openclaw-bridge

If preparing for ClawHub, ensure:

  • the skill release version matches the hosted relay project version
  • the packaged skill contains only:
    • SKILL.md
    • minimal scripts
    • references actually used by the skill

Comments

Loading comments...