> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/templates/reverse-etl-templates/trigger-hightouch-syncs.md).

# Trigger Hightouch Syncs

Learn how to automatically trigger Hightouch syncs when your dbt™ runs complete successfully in Bolt. This integration helps data teams maintain synchronized data by sending fresh data to operational tools immediately after successful pipeline runs.

***

#### What You'll Get

When a run succeeds, Bolt automatically triggers your Hightouch sync:

* Webhook sent to Hightouch API endpoint
* Sync executes with your configured mappings
* Updated data flows to your operational tools (Salesforce, HubSpot, etc.)

***

{% hint style="success" %}
**Key Benefits for Data Teams**

* **Eliminate manual sync triggers** - No more logging into Hightouch after each dbt™ run
* **Accelerate data activation** - Fresh operational data available in minutes, not hours
* **Prevent stale data in business tools** - Ensure sales and marketing always use today's data
* **Scale reverse ETL operations** - Automate the data flow that powers customer-facing applications
  {% endhint %}

{% hint style="warning" %}
**Prerequisites for Hightouch Integration**

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Hightouch account with configured sync(s)
* Admin access to Hightouch workspace
  {% endhint %}

***

#### Setup Guide

Set up Hightouch sync triggering for successful runs. Follow the steps below, and watch our interactive tutorial.

**Step 1: Gather Your Hightouch Information**

1. **Get Your Sync Slug**:
   * Go to your Hightouch Sync and find your Sync Slug in the [overview section](https://hightouch.com/docs/syncs/overview#run-details)
   * Copy Sync Slug
2. **Generate Your API Key**:
   * Follow [Hightouch documentation](https://hightouch.com/docs/developer-tools/api-guide#create-an-api-key) to create API Key
   * Copy your API key and store it in a safe location (the key will only be displayed once)

**Step 2: Configure the Webhook in Bolt**

1. From the [Bolt](https://app.paradime.io/bolt) home screen, go to [Templates](https://app.paradime.io/bolt/templates)
2. Click **Reverse ETL** and select the "Trigger Hightouch Sync" template
3. Fill in the following fields:
   * **Select Schedules**: Choose the schedules for which you want to trigger this webhook. Leave blank or select all for all schedules without filtering
   * **Sync Slug**: Enter the Sync Slug you copied from Hightouch
   * **API Key**: Enter the API key you generated in Hightouch
4. Click "Connect"

<figure><img src="/files/PaepUSVNvvk5EOsYiqAj" alt=""><figcaption></figcaption></figure>

**Step 3: Test the Integration**

1. Run a Bolt schedule manually (the webhook triggers only on successful runs)
2. After the run succeeds:
   * From the Bolt homescreen, go to [Webhooks](https://app.paradime.io/bolt/webhook)
   * Select your Hightouch Sync Webhook
   * Check the Endpoints tab to verify the webhook triggered
   * Verify in Hightouch that your sync has started


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/bolt/creating-schedules/templates/reverse-etl-templates/trigger-hightouch-syncs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.