Receive Stripe & GitHub Webhooks on Localhost — Self-Hosted OpenClaw Relay
Get Stripe, GitHub, and Sentry webhooks delivered to your local OpenClaw agent — no port forwarding, no firewall rules. Set up a self-hosted relay in 15 minutes.
TL;DR: Receive webhooks on a self-hosted OpenClaw agent in 4 steps: (1) install the relay client — it opens an outbound tunnel with no port forwarding needed, (2) register a relay URL per service, (3) update Stripe, GitHub, and Sentry to point at those relay URLs, (4) verify delivery in the dashboard. The relay URL never changes and the tunnel auto-reconnects.
If you self-host OpenClaw, you've probably hit this problem already: external services like Stripe, GitHub, and Sentry need to send webhooks to your agent, but your agent sits behind a firewall or NAT. The webhooks have nowhere to go.
Port forwarding, ngrok tunnels, reverse proxies. They all kinda work, but they all break in annoying ways. Tunnels expire, URLs change on restart, and failures happen silently. A webhook relay takes a different approach: you get a stable public endpoint that forwards payloads to your local agent through a secure outbound tunnel.
The problem with self-hosted webhooks
When you run OpenClaw on a cloud VM with a public IP, webhooks just work. You give Stripe your server URL, payloads arrive. Self-hosted setups are a different story.
Home networks sit behind NAT routers that block inbound connections by default. Corporate firewalls restrict which ports can receive external traffic. Dynamic IPs change without warning, breaking hardcoded webhook URLs. And ngrok? The free-tier URLs change on restart, sessions expire, and you get zero visibility into delivery failures.
The result: missed webhooks, broken automations, and agents that silently stop receiving the events they depend on.
How a webhook relay works
A relay flips the connection model. Instead of external services connecting inbound to your agent, your agent connects outbound to the relay:
- A lightweight relay client runs alongside your OpenClaw agent.
- The client opens a persistent, encrypted outbound connection to the relay server.
- The relay server provides a stable public URL (e.g., wh.clawpulsar.com/abc123).
- External services send webhooks to the relay URL.
- The relay forwards payloads through the existing outbound tunnel to your agent.
Because the connection is outbound, no port forwarding or firewall rules are needed. The tunnel auto-reconnects if dropped. The relay URL never changes.
Setting up with ClawPulsar
ClawPulsar provides a managed relay with built-in monitoring. Here's how setup works:
Step 1: Install the relay client
The relay client is a single binary that runs alongside your OpenClaw instance. It establishes the outbound tunnel and handles reconnection on its own.
Step 2: Register your webhook endpoints
Each service gets its own relay URL. Register endpoints for Stripe, GitHub, Sentry, or any other webhook provider. Each endpoint can have custom headers, authentication, and retry policies.
Step 3: Point your services to the relay
Replace your old webhook URLs with the ClawPulsar relay URLs. For Stripe, update the endpoint in your Dashboard settings. For GitHub, update the webhook URL in your repository settings. For Sentry, update the webhook URL in your integration settings.
Step 4: Verify delivery
The ClawPulsar dashboard shows every webhook received, its delivery status, response time, and any errors. You can replay failed deliveries with one click.
Monitoring and reliability
A relay is only useful if it actually stays up. ClawPulsar adds a few layers on top of basic forwarding:
Delivery confirmation. Every payload is tracked from receipt to delivery. Failed deliveries get automatically retried with exponential backoff. For a deep dive into monitoring delivery rates and setting latency alert thresholds, see webhook monitoring best practices.
Uptime monitoring. External health checks run every minute to detect when your agent goes offline, even if your entire server is down.
Budget alerts. Connect your LLM API keys and set spend thresholds. Get warnings before a runaway agent racks up a surprise bill.
Health dashboard. One view for relay throughput, delivery rates, response times, and agent uptime across all your instances.
Common webhook providers
ClawPulsar works with any service that sends webhooks. The most common for OpenClaw users:
- Stripe: Payment events, subscription changes, disputes, invoices.
- GitHub: Pull requests, issues, deployments, releases, pushes.
- Sentry: Error events, issue state changes, deployment notifications.
- Linear: Issue updates, cycle events, project changes.
- Shopify: Orders, inventory, customer events, fulfillment.
Best practices
Use separate relay endpoints per service. This gives you independent monitoring, retry policies, and the ability to disable one without affecting others.
Enable delivery confirmation. Always verify that your agent acknowledged the payload. Silent failures are the hardest to debug.
Set up uptime alerts. External monitoring catches problems that self-hosted dashboards can't, because self-hosted monitors fail when the server they monitor fails.
Review relay logs weekly. Patterns in delivery times, error rates, and payload sizes help you spot issues before they become outages.
What comes next
ClawPulsar is currently in private beta. Join the waitlist to get early access to the managed webhook relay, uptime monitoring, and budget alerts for your self-hosted OpenClaw agent.
Monitor agent health in real time
ClawPulsar tracks uptime, latency, and error rates across your entire agent fleet.