Source Types, PagerDuty Integration, and the Event Destinations Initiative

We're always looking for ways to improve how you manage webhooks and event-driven workflows. This time around, we've rolled out three key updates: Source Types to simplify webhook setup, a PagerDuty integration to help teams stay on top of webhook issues, and we've removed the HTTP/CLI View dropdown from the Hookdeck dashboard to improve the DX of event discovery.

Plus, we're kicking off a broader conversation in the webhook and event-driven space with the Event Destinations Initiative—more on that later!

Source Types: Less Setup, More Control

Setting up webhook sources can be tricky, with each provider having its own settings and quirks. Source Types makes this process smoother by automatically adjusting Hookdeck's configuration options based on your webhook provider. This means less time spent figuring things out and fewer setup mistakes.

Why Source Types?

• Less guesswork, faster setup - Hookdeck only shows you the options that matter for your source.
• Helps avoid common mistakes - Some providers require secrets for verification—Source Types makes sure you don't miss them.
• Future-ready - This paves the way for supporting more integration source and destination types, including AWS Lambda, Amazon S3, WebSockets, and gRPC.

Want the details? Check out the Source Types announcement.

We've also introduced support for a number of new source types, including: DocuSign, Smile, Standard Webhooks, BigCommerce, LinkedIn, and Upollo.

Enhancing Webhook Incident Management with Hookdeck and PagerDuty

Webhook failures can be frustrating, especially when they go unnoticed. With our new PagerDuty integration, teams can automatically create PagerDuty incidents for webhook-related issues.

How it works

• Webhook delivery failures? Hookdeck detects them and triggers a PagerDuty incident.
• Outbound API request errors? If a third-party service API returns an error code, Hookdeck raises an issue and PagerDuty alerts your team.
• Real-time status syncing - Any updates in Hookdeck reflect in PagerDuty (and vice versa).

We recently demonstrated the Hookdeck PagerDuty on a livestream with PagerDuty. Watch the demo:

Need help setting it up? Read the PagerDuty integration docs.

Bye-Bye HTTP/CLI View

The HTTP and CLI view dropdown, which used to live on the left of the dashboard, has been removed. But don't worry...

Now, your CLI and HTTP events will be visible in the default Events view. If your CLI is connected, a dynamic view will appear that shows only your CLI events.

So, no more hopping between HTTP and CLI views which we believe improves the developer experience of event discovery—I know I've often spent time wondering why I couldn't see an event only to then realize I was in the wrong view.

Watch the explainer on YouTube for more information.

A Broader Industry Initiative: Event Destinations

Beyond Hookdeck's own updates, we're also working on something new: the Event Destinations Initiative. This is a community effort to define best practices for how events move between services, making integrations more seamless and reliable.

Specifically, Event Destinations champions the use of event destinations beyond webhooks, such as message queues and event gateways.

Why does this matter?

• More consistency across platforms - Common guidelines for event destinations makes integrations smoother.
• Improved interoperability - Easier connections between services mean fewer headaches for developers.
• Scalability and reliability - A stronger foundation for building event-driven applications.

This initiative is still in its early days, and we'd love to hear your thoughts. Want to get involved? Learn more at eventdestinations.org.

That's all for this update! If you're using any of these new features, let us know how they're working for you by getting in touch or joining our Slack community.