Beton + Webhooks
Send revenue signals anywhere with HTTP webhooks
Send signals to any tool via webhooks. Build custom integrations with your existing stack.
How It Works
1
Configure your webhook endpoint
Provide any HTTP endpoint URL. Beton sends structured JSON payloads for each detected signal.
2
Filter and transform signals
Choose which signal types to forward and customize the payload format to match your system's expectations.
3
Receive signals in real-time
Your endpoint receives a POST request with full signal context every time a matching signal is detected.
Sample Signal Payload
JSON
{
"signal_type": "product_qualified_lead",
"confidence": 0.92,
"source": "posthog",
"destination": "webhook",
"account": {
"name": "Acme Corp",
"domain": "acme.com"
},
"events": [
"visited_pricing_page",
"invited_team_member",
"api_key_created"
],
"enrichment": {
"company_size": "50-200",
"industry": "SaaS"
}
}Features
- Standard HTTP POST with JSON payloads
- Configurable headers and authentication
- Signal type filtering
- Payload transformation and mapping
- Retry logic with exponential backoff
- Delivery logging and debugging tools
Use Cases
- Send signals to Slack channels for team visibility
- Trigger custom scripts or serverless functions
- Feed signals into data warehouses or analytics tools
- Build custom integrations with internal tools
Frequently Asked Questions
What's the difference between Webhooks and the n8n integration?
The n8n integration is a pre-built connector with a fixed payload shape. Webhooks is the generic version — point it at any HTTPS endpoint, including your own API, Zapier, Make, Slack workflows, or a custom service.
How are webhook payloads authenticated?
Beton signs every request with HMAC-SHA256 using a shared secret you configure. The signature is in the X-Beton-Signature header. Basic auth and custom headers are also supported for legacy systems.
Can I retry failed webhook deliveries?
Yes. Beton retries failed deliveries with exponential backoff up to 10 attempts over 24 hours. Delivery logs are visible in the Signals dashboard so you can debug endpoint issues.
What does the webhook payload contain?
A JSON object with signal_type, confidence, source, destination, account (name, domain), events, enrichment, and detected_at. A sample payload is shown on this page.
Ready to connect Webhooks?
Start detecting revenue signals and routing them to Webhooks in minutes.
