Deliver Events to Any DestinationReliably
Route webhooks and events to multiple destinations with built-in retries, isolation, and visibility. Works with existing webhook integrations — no producer rewrites required.
Define Destinations Once — Deliver Everywhere
Configure destinations with endpoints, authentication, and filters. Pulse handles retries, failures, and isolation per destination.
Deliver Events to Multiple Destinations
Route events to webhooks, queues, or any endpoint with automatic retries, exponential backoff, and delivery guarantees.
Destination-Based Subscriptions and Filtering
Configure which destinations receive which event types with granular filtering and subscription management.
Per-Destination Isolation and Rate Limits
Isolate delivery per destination with independent rate limits, failure handling, and retry policies.
Destination-Level Authentication and Security
Configure authentication per destination with signature verification, API keys, or OAuth — securing each endpoint independently.
Destination-Specific Delivery Monitoring
Track delivery status, retry attempts, and performance metrics for each destination with detailed logs and analytics.
Real-Time Event Routing at Scale
Route events from your API or forwarded inbound webhooks to all configured destinations with low latency and high throughput.
Define Your Event Types
Define event types as contracts between producers and destinations. Schemas and versioning ensure reliable delivery across all configured destinations.
- Schema validation and versioning
- Bulk import event types
- Event categorization and filtering
Configure Destinations for Event Delivery
Destinations subscribe to event types with custom endpoints, filters, and authentication. Configure via UI or API for maximum flexibility.
- Granular event type selection
- Custom endpoint configuration
- Create subscription using UI or API/SDK
Monitor Event Delivery
Monitor delivery status per destination. Track retries, debug failures, and replay events — all with destination-level visibility for operational trust.
- Real-time delivery tracking
- Automatic retry with exponential backoff
- Detailed event logs and analytics
How It Works
Route events to destinations in three simple steps
Define Event Types
Create event types with schemas and documentation for your customers
Configure Destinations
Configure destination endpoints, authentication, and event filters
Publish Events
Publish events via API or forward from inbound webhooks. Pulse routes to all configured destinations.
Frequently Asked Questions
Everything you need to know about Pulse
What is the difference between Flow and Pulse?
Flow is for receiving and routing inbound webhooks from external services. Pulse is for sending events from your application to multiple customer endpoints. Flow handles incoming webhooks, while Pulse delivers outgoing events to destinations.
How does Pulse handle failed webhook deliveries?
Pulse automatically retries failed deliveries with exponential backoff. Each destination has independent retry policies, rate limits, and failure handling. You can monitor delivery status, debug failures, and manually replay events if needed.
Can I send events to multiple destinations simultaneously?
Yes, Pulse supports fan-out delivery to multiple destinations. Each destination receives events independently with its own retry logic, rate limits, and authentication. One event can be delivered to webhooks, queues, or any configured endpoint.
How do I configure authentication for different destinations?
Pulse supports per-destination authentication including signature verification, API keys, and OAuth. Each destination can have its own authentication method, allowing you to securely deliver events to different customer endpoints with their specific security requirements.
Stop Building Destination-Specific Delivery Logic
Start with webhooks. Scale to multiple destinations without rewrites.