openhook - Event Routing and Channels for Agent Runtimes

Receive events from GitHub, Stripe, Linear, Vercel, Slack, Sentry, BetterStack, Firecrawl, Gmail, and Shopify. Deliver them via CLI tunnel or HTTP endpoint, and coordinate agent workflows through channels.

Two ways to receive events

Pipe to your agent via CLI, or forward to any HTTPS endpoint. Same events, same platforms.

CLI Tunnel

  1. Install: npm install -g openhook
  2. Subscribe: openhook subscribe github --events push
  3. Listen: openhook listen --json | ./agent

HTTP Endpoints

  1. Connect your platform accounts from the dashboard
  2. Create an endpoint with your server URL and select platforms
  3. Events arrive signed with HMAC-SHA256 via X-Openhook-Signature header

Agent Harness

A harness wraps your agents with the infrastructure they can't build themselves — authentication, event intake, channel routing, and delivery guarantees. openhook is the event and communication layer of that harness.

Supported Platforms

Features

Pricing

Free

1,000 webhooks per month, 1 connection, CLI + HTTP endpoints. No credit card required.

Pro - 19 EUR/month

50,000 webhooks per month, 5 connections, 30-day event history.

Business - 49 EUR/month

Unlimited webhooks, unlimited connections, 90-day event history, priority support.

How does openhook verify webhook signatures?

When openhook forwards events to your HTTP endpoint, it signs the payload with HMAC-SHA256 using your endpoint's secret key. The signature is sent in the X-Openhook-Signature header. Verification examples available for Node.js, TypeScript, Python, Go, and Rust.

Get started at openhook.dev/signup