Use Cases
Explore real-world patterns for webhook routing, transformation, and delivery with Hookbase. These examples demonstrate how to combine sources, destinations, routes, transforms, and filters to build powerful webhook pipelines.
Featured Use Cases
Stripe Payment Fan-Out
Route Stripe payment events to multiple systems simultaneously. Send checkout.session.completed and invoice.paid events to your billing API, analytics service, and Slack notifications—each with custom transforms tailored to the destination.
Key Features:
- Multi-destination routing from a single source
- Event filtering by type and amount
- Custom JSONata transforms per destination
- Slack Block Kit message formatting
GitHub → Slack Notifications
Route GitHub webhook events to different Slack channels based on event type. Send PR events to your #dev channel and deployment events to #ops, with rich, formatted messages.
Key Features:
- Header-based routing (
x-github-event) - Conditional formatting based on status
- Slack Block Kit integration
- Color-coded messages for visibility
Shopify Order Routing
Route Shopify order webhooks to different systems based on order value and type. High-value orders ($500+) go to priority fulfillment and PagerDuty, all orders update inventory, and refunds notify the finance team via Slack.
Key Features:
- Content-based routing by order value and topic
- PagerDuty integration for high-value order alerts
- Inventory management with warehouse routing hints
- Slack Block Kit refund notifications for finance
Multi-Provider Monitoring Dashboard
Aggregate webhooks from GitHub, Stripe, and Shopify into a unified monitoring dashboard using the fan-in pattern. Each provider's payload is normalized into a common schema with dedicated transforms.
Key Features:
- Fan-in from multiple providers to one destination
- Normalized common schema across all providers
- Easy to extend with new providers
- Provider-specific severity mapping
Webhook Logging & Audit Trail
Build a compliance-grade webhook audit system that logs all events to a data warehouse. Includes structured audit records, PII field encryption, test event filtering, and non-repudiation through signature preservation.
Key Features:
- Dual routing: operational destinations + audit logging
- Field encryption for PII/GDPR compliance
- Test and health-check event filtering
- Structured audit records with payload hashing
Provider-Specific Examples
For more examples tailored to specific webhook providers, see our integration guides:
- GitHub - PR events, deployments, issue tracking
- Stripe - Payment processing, subscription management
- Shopify - Order events, inventory updates
- Slack - Interactive messages, slash commands
- Twilio - SMS delivery, call events
Each integration guide includes signature verification setup, common event patterns, and ready-to-use transform examples.
Build Your Own
These use cases are just starting points. Hookbase's flexible architecture lets you combine sources, destinations, routes, transforms, and filters to build custom pipelines for any webhook scenario.
Key Building Blocks:
- Sources - Receive webhooks with signature verification
- Destinations - Send to APIs, webhooks, or Slack
- Routes - Define event flow with filters and transforms
- Transforms - Reshape payloads with JSONata
- Filters - Route events based on content or headers
- Pipeline Architecture - Understand the full data flow
Common Patterns
Fan-Out
Route a single webhook to multiple destinations with different transforms. Useful for:
- Payment events → billing, analytics, notifications
- CI/CD events → monitoring, chat, ticketing
- Order events → inventory, fulfillment, customer service
Fan-In
Aggregate webhooks from multiple sources into a single destination. Useful for:
- Multi-provider notifications → unified Slack channel
- Cross-platform analytics → single data warehouse
- Vendor consolidation → normalized API
Content-Based Routing
Route events to different destinations based on payload content:
- High-value orders → priority queue
- Failed payments → finance team alerts
- Security events → dedicated monitoring
Enrichment
Transform webhooks by adding context from external APIs:
- Customer data from CRM
- Product details from catalog
- Geolocation from IP addresses
Production Best Practices
When building webhook pipelines for production:
- Enable Deduplication - Prevent duplicate event processing (Guide)
- Configure Circuit Breakers - Protect downstream services from overload (Guide)
- Set Up Failover - Ensure critical events reach backup destinations (Guide)
- Use Notification Channels - Get alerted to delivery failures (Guide)
- Monitor with Audit Logs - Track configuration changes and access (Guide)
- Test with CLI - Validate your pipeline locally before deploying (Guide)
Need Help?
- Review the Pipeline Architecture guide for a deep dive into data flow
- Check the Transforms guide for JSONata syntax and examples
- Explore the Filters guide for advanced routing logic
- See the API Reference for complete endpoint documentation