Public webhooks for OpenClaw workflows.

clawproxy is the webhook relay for OpenClaw workflows: accept provider events on the public internet, queue them safely, and deliver them to a private OpenClaw node over an outbound WebSocket or pull connection.

Open dashboard Copy setup snippet

openclaw route

/api/ingress/<user-id>/github-to-openclaw

queued

delivery path

Provider event in. OpenClaw action out.

GitHub, Stripe, and Slack webhooks get a stable public endpoint while OpenClaw keeps processing private behind NAT.

Ingress accepted

Queued safely

OpenClaw acked

GitHub events reach your local automation

Point repositories at one public clawproxy route while OpenClaw runs privately on a lab box, workstation, or Coolify service.

Durable delivery for sleeping workers

clawproxy stores every accepted webhook until your OpenClaw node reconnects, pulls the event, and acknowledges it.

No inbound firewall changes

The OpenClaw node initiates an outbound WebSocket or pull connection, so you do not expose SSH, dashboards, or agent ports.

Wire OpenClaw to clawproxy in minutes.

Start with one dashboard-generated route URL that includes your user id, verify delivery, then add more provider workflows without changing how your OpenClaw node reaches the public internet.

OpenClaw env

OPENCLAW_WEBHOOK_RELAY_URL=wss://clawproxy.io/api/nodes/ws
OPENCLAW_WEBHOOK_NODE_TOKEN=cpn_your_node_token
OPENCLAW_WEBHOOK_ROUTE_URL=https://clawproxy.io/api/ingress/<user-id>/github-to-openclaw

01Create a node token in the clawproxy dashboard.
02Create a route for each provider or workflow.
03Configure OpenClaw with the relay URL and node token.
04Send GitHub, Stripe, and Slack webhooks to the generated route URL.

System overview

Webhook events travel from the public internet to your private node without exposing a single port.

Provider

Public internet

GitHub
Stripe
Slack
Any webhook service

webhook POST

clawproxy

Public cloud

Accepts & validates
Saves events until delivery
Manages delivery state

outbound pullevents + ack

outbound pull / events

OpenClaw node

Your private network

Never exposed

Polls for new events
Processes locally
Acknowledges delivery

Your node always initiates the connection outbound. No open ports or firewall rules required.

Give OpenClaw a stable public webhook edge.

Keep provider URLs stable, keep OpenClaw private, and let clawproxy handle the queue between them.

clawproxy.io/openclaw

Open dashboard Back to clawproxy