Webhook Automations
2 min read
Webhook automations connect Binx to the outside world. External services — payment processors, CI/CD pipelines, monitoring tools, CRMs — can trigger Binx actions by calling a secure URL. The result lands in your WhatsApp as a message, powered by AI or a template you define.
How to use
Create a webhook automation from the Binx dashboard. You receive a unique URL and an optional webhook secret for HMAC-SHA256 signature verification. Point your external service (Stripe, GitHub, Zapier, etc.) at this URL. When the webhook fires, Binx processes the payload using your prompt or response template. Templates support Mustache-style interpolation: {{body.amount}}, {{headers.x-event}}, {{automation.name}}. Toggle 'Use AI' to have Binx generate intelligent summaries instead of static templates. Add event filters to trigger only on specific conditions, like header['x-event'] == 'payment_success'.
Video walkthroughs for tutorials are coming soon.
Use cases
Payment notifications
Stripe fires a webhook on successful payment → Binx sends you a WhatsApp message: 'New payment of $49 from customer@email.com for Pro plan.'
Deploy alerts
GitHub Actions webhook on deploy complete → Binx sends 'Production deploy succeeded for commit abc123 on main branch.'
Form submissions
Typeform or Tally webhook on new response → Binx summarizes the submission and sends it to your WhatsApp for quick review.
Custom integrations
Any service that supports outgoing webhooks can talk to Binx. Use the response template to format exactly the message you want.
Example
Send something like this in your Binx chat on WhatsApp.
“When my Stripe webhook fires for a successful payment, send me a WhatsApp message with the customer email and amount”
Tips
Always enable webhook secret verification in production for security. Use event filters to avoid noisy notifications — only trigger on the events that matter. Test your webhook with a manual 'Run Now' from the dashboard before connecting external services.
