Route webhooks into private Hermes runs.

Route GitHub, Stripe, Slack, or custom webhooks into Hermes without opening inbound ports. clawproxy accepts the public request, stores it, and delivers it to Hermes when your node is configured with an outbound connection.

Create a route Copy setup snippet

delivery target

Hermes stays private. Work still starts instantly.

Public webhooks become reliable inputs for agent workflows, Kanban dispatch, and automation runs.

Provider webhook

clawproxy route

Hermes agent run

Trigger Kanban workers from GitHub

Use clawproxy as the durable public front door for Hermes automation that should stay behind outbound-only network boundaries.

Keep agent boxes private

Use clawproxy as the durable public front door for Hermes automation that should stay behind outbound-only network boundaries.

Debug webhook delivery

Use clawproxy as the durable public front door for Hermes automation that should stay behind outbound-only network boundaries.

Connect Hermes with one public route.

Create a clawproxy route, copy its generated provider URL and node token from the dashboard, then install the Hermes plugin. A clawproxy route named github-prs delivers to the Hermes webhook route with the same slug.

setup snippet

# 1. Create a clawproxy route in the dashboard
# Provider URL: https://clawproxy.io/api/ingress/<userId>/<routeSlug>

# 2. Install the Hermes gateway plugin
hermes plugins install ericdahl-dev/clawproxy-hermes

# 3. Add these to ~/.hermes/.env (or your profile's .env)
CLAWPROXY_NODE_TOKEN=cpn_your_node_token
CLAWPROXY_HERMES_WEBHOOK_SECRET=<platforms.webhook.extra.secret>

# 4. Restart the gateway, then check delivery
hermes gateway status