Build custom workflows with Buska webhooks

The Buska Webhook integration sends a real-time HTTP POST event for every new buying signal detected on Reddit, Twitter / X, LinkedIn, Hacker News, Quora, YouTube, and 30+ other platforms. Connect Buska to any tool that accepts webhooks (Make, Zapier, n8n, Pipedream, custom backends), build fully custom automations, or push data to your own infrastructure. The JSON payload includes the lead's full post, author, platform, intent score (0 to 100), keyword match, ICP match score, and detection timestamp. HMAC-SHA256 signed for authenticity. Setup takes 2 minutes. The Buska Webhook integration is included on every plan starting at $49 per month.

Start free trial View setup docs

buska

Webhook

What you can do with Buska + Webhook

Receive real-time HTTP POST requests for every new qualifying buying signal with HMAC-SHA256 signature verification
Full JSON payload with post content, author profile, platform, intent score (0 to 100), intent type, ICP match score, and detection timestamp
Filter which leads trigger webhooks by intent score, platform, keyword, or language
Connect to any tool that accepts webhooks: Make, Zapier, n8n, Pipedream, Workato, Tray.io, or your custom Node / Python / Go backend
Build completely custom lead processing pipelines with your own scoring, enrichment, and routing logic
Multiple webhook endpoints with different filters for multi-team routing
Retry on failure with exponential backoff up to 5 attempts, so transient errors do not lose leads
Replay past webhook events from the Buska dashboard to test new endpoints without waiting for fresh signals

How to set up Buska + Webhook

Get your webhook URL

In your receiving tool (Make, n8n, Pipedream, Zapier, custom server), create a webhook endpoint and copy the URL. Buska requires HTTPS endpoints in production. For local testing, use ngrok or Cloudflare Tunnel to expose a localhost endpoint.

https://webhook.office.com/...

Add to Buska

Paste the webhook URL in Buska Settings > Integrations > Webhook. The connection is instant. Buska signs every webhook with HMAC-SHA256 using your webhook secret (auto-generated, viewable in settings). Your receiver verifies the signature before processing.

Settings/Integrations

Webhook

Paste URL here...

Save

Configure filters

Set minimum intent score (most teams use 70 out of 100) and platform / keyword / language filters. Only matching leads trigger the webhook. Buska filters out about 90% of irrelevant mentions before they reach your endpoint, saving you compute and rate-limit budget on downstream tools.

Min. score65

Platforms

TwitterRedditLinkedIn

Keywords

All

Parse the JSON payload

Parse the JSON payload in your tool. Fields included: `leadId`, `authorName`, `authorProfileUrl`, `postContent`, `postUrl`, `platform`, `keywordMatch`, `intentType`, `intentScore` (0-100), `icpMatchScore`, `language`, `detectedAt` (ISO 8601). Full schema is in the Buska Webhook docs.

Buska Alert2m ago

Score 82Twitter

View in Buska

Build your workflow

Build whatever automation you need: CRM sync (HubSpot, Salesforce, Pipedrive, Attio), enrichment (Apollo, Clearbit, Lusha), email / DM (Lemlist, Instantly, LGM), internal tools (Linear, Slack, Discord, Teams). The Webhook integration is infrastructure-grade, not toy automation.

Monitor delivery

View delivery status, response codes, and retry attempts in Buska Settings > Integrations > Webhook > Delivery Log. Failed deliveries retry up to 5 times with exponential backoff (1s, 5s, 25s, 125s, 625s). After 5 failures, the event is marked failed but can be replayed manually.

Real use cases with Webhook

Custom lead routing

Parse the webhook payload and route leads to different tools based on intent type, platform, or score. Active demand signals go to your CRM with high priority, question signals go to your content team to feed your blog backlog, competitor mentions go to a dedicated migration playbook.

Custom enrichment pipeline

Receive the webhook, enrich with your own data sources (Clearbit, ZoomInfo, Apollo, Lusha, Cognism), score with your own model (custom logistic regression, fine-tuned LLM, ICP centroid), then push to your CRM with the composite score attached.

Multi-tool orchestration

Use Buska webhooks to trigger complex workflows across multiple tools: create a HubSpot contact + send a Slack alert + add to a Lemlist campaign + update an Airtable tracker + create a Linear ticket for the SDR, all from one social signal. Total latency: under 60 seconds end-to-end.

Custom LLM enrichment

Send each Buska webhook to your own LLM endpoint (OpenAI, Anthropic, Mistral, self-hosted) to draft a personalized reply, classify the buying intent more granularly, or summarize the social thread for your sales team. Token cost: $0.0001 to $0.01 per lead.

Frequently asked questions about Buska + Webhook

What's in the Buska webhook payload?

The JSON payload includes: lead ID, author name, author profile URL, post content, post URL, platform, keyword matched, intent type (active demand, competitor mention, pain expression), intent score (0 to 100), ICP match score (0 to 100), language (ISO 639-1), and detection timestamp (ISO 8601). Full JSON schema with examples is in the Buska Webhook docs.

How fast are Buska webhooks sent?

Webhooks are sent in real time, within 30 seconds of Buska detecting and qualifying a new lead. P95 latency stays below 2 minutes even at peak load. Buska retries failed deliveries up to 5 times with exponential backoff so transient endpoint errors do not lose leads.

Can I have multiple Buska webhook endpoints?

Yes. You can configure multiple webhook endpoints with different filters in Buska Settings > Integrations > Webhook. Most teams run 3 to 5 endpoints: one for the CRM, one for Slack (via custom router), one for an internal data warehouse, one for billing-tier-specific customers. Multi-endpoint routing is on Growth and above.

How do I verify Buska webhook authenticity?

Every Buska webhook is signed with HMAC-SHA256 using your webhook secret (auto-generated, visible in Buska Settings). The signature is sent in the `X-Buska-Signature` header. Your receiver computes the HMAC of the raw request body with the secret and compares it to the header value. Code examples in Node, Python, Go, and Ruby are in the docs.

What if my webhook endpoint goes down?

Buska retries up to 5 times with exponential backoff (1s, 5s, 25s, 125s, 625s). If all 5 retries fail, the event is marked failed and stored in the Delivery Log for manual replay from the Buska dashboard. You can also configure a backup endpoint that fires after the 3rd failed retry.

Is the Buska Webhook integration secure?

Yes. TLS 1.3 in transit, HMAC-SHA256 signature on every payload, per-endpoint secrets (rotatable from the dashboard). Buska never sends sensitive data; the webhook payload contains only public social post content and derived metadata. The integration is compatible with SOC 2 customer requirements and GDPR.

Can I test the Buska webhook before going live?

Yes. Buska Settings > Integrations > Webhook has a "Send test event" button that fires a sample payload to your endpoint, so you can validate parsing and signature verification before turning on production traffic. You can also replay past events from the Delivery Log for ongoing testing.

How much does the Buska Webhook integration cost?

The Buska Webhook integration is included on every plan at no extra cost. Buska plans start at $49 per month (Starter, 3 keywords, 1 webhook endpoint), $99 per month (Growth, 10 keywords, multi-endpoint routing), and $249 per month (Scale, 25 keywords, advanced retry & replay). All plans include a 7-day free trial.

Ready to connect Webhook?

Start your free trial and set up the Webhook integration in under 2 minutes.

Start free trial