clawproxy

Public webhook ingress for private OpenClaw nodes

Stop exposing ports just to receive webhooks

Webhooks for private nodes.

Accept webhook traffic from the public internet, store it durably, and deliver it to your OpenClaw node over authenticated outbound pull. No public node exposure required.

Built for OpenClawSelf-hostableDurable deliveryPrivate-node friendly

Live flow

From provider to private node

Healthy
1

GitHub / Stripe / Slack

Webhook hits your public clawproxy route.

2

Ingress accepted

Request validated and persisted to the durable queue.

3

Node pull

Your private OpenClaw node fetches pending events securely.

4

Ack complete

Processed events are acknowledged and marked delivered.

Mode

Pull-based

Storage

Durable queue

Ideal for

NAT + LAN

Never miss a webhook

Inbound events are persisted before delivery, so temporary downtime or sleeping nodes do not turn into dropped requests.

Keep your node private

clawproxy is designed for deployments behind NAT, residential routers, and private LANs that can only make outbound connections.

Pull-based by design

Your OpenClaw node authenticates, fetches queued events, processes them locally, and acknowledges success on its own schedule.

Built for operators

Manage routes, inspect recent traffic, debug failures, and understand delivery state from one lightweight dashboard.

How it works

Keep the webhook path public and the node private.

clawproxy is deliberately focused: it receives inbound webhook traffic on the public internet and hands it off to private OpenClaw nodes through authenticated outbound requests.

01

Expose a public route

Create a route in clawproxy and point GitHub, Stripe, Slack, or any provider at the generated URL.

02

Queue every inbound event

Each request is validated, accepted, and stored durably before your private node ever touches it.

03

Deliver over outbound pull

Your OpenClaw node polls securely, processes events locally, and acknowledges delivery when complete.

Ready to route inbound events?

Public ingress on one side. Secure outbound delivery on the other.

Built for the very common reality that your software can call out, but should not be exposed directly to the internet.

clawproxy.io