Webhook

Table of Contents

A webhook is a method of augmenting or altering the behavior of a web page or web application with custom, user-defined HTTP callbacks.

Overview

With the Webhook destination, Hightouch can send events to your custom webhook whenever a row is created, updated, or deleted.Webhooks batch results, up to 1,000 records per request, with the results being sent in the body as an array of named objects.

Prerequisites

You'll need a webhook that is ready to accept a payload already setup. If you don't have one, you can set one up with Pipedream in under a minute. Just set up a Workflow with a New Requests trigger.

Once created, you'll have a https endpoint that you can use during the setup process on Hightouch.

Allow-listing IP addresses

Our webhooks will originate from the following two IP addresses: 54.196.30.169 or 52.72.201.213. You will need to add these IPs to your allow-list to ensure you can receive our traffic to your destination.

Setup

Step 1: Create a Destination

First, we'll want to create a Webhook destination. Under the Webhook URL, provide the endpoint where the payload will be sent when your data changes.Add any headers you may need for authorization, for example, below we're using an Authorization header with a Basic type and encoded credentials.

Step 2: Add the Destination to a Model

Once you've named and saved your destination, create a sync if you already have a model, or create a new model and then apply the destination.Below, we create a Snowflake query that will send company_id, name, website to our webhook.

Once you've named the model and picked your primary key, you'll be able to add the destination you created in Step 1. You'll be prompted to configure the webhook.

Here we've opted to sync all columns with the same name, and will trigger on all events. Finally, pick your schedule, and click Start Run to start you first sync. You should see the progress update to Completed.

Once completed, you can manually initiate the first run, or wait for it to sync automatically. Your endpoint will receive a body with an array of named objects for each row and column.