Step Two - Manage Connections
Hookdeck connections allow you to flexibly route webhooks from a source to a destination, optionally with additional logic (via connection rules) that allows you to configure how events are handled in-between.
Fanning out a request
By adding multiple connections to the same source, you can route one webhook to multiple destinations, allowing you to streamline your configuration without needlessly duplicating logic.
This is especially useful in situations where a given webhook is needed in multiple places (S3, server, etc.). Each source supports an unlimited number of unique connections.
Configuring Signature Verification
Signature verification allows you to offload webhook authentication to built-in and custom integrations before the webhooks are processed. After incoming requests are verified, an x-hookdeck-verified header is added to simplify verification downstream.
Hookdeck has built-in integrations for Twitter, GitHub, Shopify, Stripe, and more. A full list of providers, along with configuration options, is available on the Integrations page.
We've also made it simple to develop your own integration for any platform that implements any of the following verification methods:
- Base 64
- HMAC
- API Key
Read more about Signature Verification here.
Transforming requests
Transformations are a powerful tool that allow you to modify the data payload of webhooks in transit, allowing you to seamlessly connect services by changing the data structure of the source to match the expected structure of the destination.
Hookdeck allows for arbitrary transformations on request data using JavaScript (ES6). Read more about Transformations here.
Filtering requests
Oftentimes, you'll be receiving far more webhooks than expected, and many of them won't be relevant to the configured destination. Filters allow you to define rules for which webhooks you actually need to process and pass along, and reject the rest. This allows you to optimize and streamline your webhook workflow with minimal clutter.
Filters can be configured (via JSON) on the webhook body, header(s), path, and/or queries.
Learn more about Filters and their syntax here.
Up Next
Now that you've likely leveraged some or all of these features, your connection should now be tailored to your specific use case. Next, we'll go live with your first connection!