Introducing HookdeckStep One - Initial TestingStep Two - Manage ConnectionsStep Three - DeploymentStep Four - MonitoringStep Five - Recover from Errors

Step Three - Deployment

At this point, you've setup your dashboard and tweaked the configuration to meet the expectations of your use case. Deployment with Hookdeck does not require any code change, so going live is as simple as updating the destination with the live URL. Before going into production, however, we recommend a few configuration tweaks that will help you troubleshoot down the line.

Setting a Rate Limit


Similar in effect to the filtering effect covered in the previous step, a rate limit will allow you to define the pace (upper bound) at which your destination will receive webhooks.

Learn more about rate limiting here.

Defining Automatic Retry


Event delivery failures can happen for a wide variety of reasons, and a sizeable portion succeed on a subsequent attempt. With automatic retries, you can define a retry strategy to try and automatically resolve delivery failures and save your hands-on troubleshooting for more serious issues.

Learn more about automatic retries here.

Configuring Notifications


The first step in resolving issues is knowing they exist. Setting up issue triggers for your connection allows you to define which issues to alert on, and who should be notified so you can get back up and running quickly.

Learn more about issue triggers here.

Pause your connection


Need to update your destination, but don't want to deal with the headache of sorting out data you may have missed during the downtime? Hookdeck has you covered with connection pausing, allowing you to pause the event stream and queue your events until you unpause.

Learn more about connection pausing here.

Up Next

After configuring these options, you should feel confident (well, as confident as possible) putting your integration into production. We've saved ourselves a lot of future work in this step, so next up we'll be looking at monitoring and troubleshooting any issues we haven't automated in the previous steps.