> 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/dashboard-templates/trigger-hex-projects.md).

# Trigger Hex Projects

Learn how to automatically trigger Hex projects when your dbt™ runs complete successfully in Bolt. This integration helps data teams maintain up-to-date dashboards by refreshing Hex projects immediately after successful pipeline runs.

### What You'll Get

When a run succeeds, Bolt automatically triggers your Hex project:

* Webhook triggers automatically
* Hex project refreshes with latest data

<figure><img src="/files/7TxhZzdHsYahn4V3aeXP" alt=""><figcaption></figcaption></figure>

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

* Automatic Hex project updates after successful Bolt runs
* Real-time dashboard refreshes
* Streamlined workflow between dbt™ pipelines and Hex analytics
* Always current visualizations and reports
  {% endhint %}

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

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Admin access to Hex
* Hex [workspace token](https://learn.hex.tech/docs/explore-data/notebook-view/hex-api/hex-api-overview#workspace-tokens) (API Key)
* Project UUID from your Hex project
  {% endhint %}

***

### Setup Guide

Set up Hex project updates for successful runs. Follow the steps below, and watch our [interactive tutorial](#step-3-test-the-integration).

#### Step 1: Gather Your Hex Credentials

1. **Get Your Project UUID**:
   * Find the UUID in either:
     * The URL after `/hex/`
     * The Variables view in the sidebar

<figure><img src="/files/1CartwEx02K88L3scdi3" alt=""><figcaption></figcaption></figure>

2. **Generate API Key**:

* Go to Settings > API Keys
* Create a new [workspace token](https://learn.hex.tech/docs/explore-data/notebook-view/hex-api/hex-api-overview#workspace-tokens)
* Save the token securely

#### Step 2: Configure the Webhook In Paradime

1. From the [Bolt](https://app.paradime.io/bolt) home screen, go to [Templates](https://app.paradime.io/bolt/templates)
2. Click "Trigger Hex Project"
3. Enter your Hex Credentials:
   * Project UUID
   * API Key (Workspace Token)
4. Click "Connect"

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

#### Step 3: Test the Integration

1. [Run a Bolt schedule manually](/app-help/documentation/bolt/managing-schedules/schedule-configurations.md#trigger-a-run-manually) (the webhook triggers only on successful runs)
2. After the run succeeds:
   * From the Bolt homescreen, go to Webhooks
   * Select your Hex Project Webhook
   * Check the Endpoints tab to verify the webhook triggered
   * Verify your Hex dashboard has updated

{% @arcade/embed url="<https://app.arcade.software/share/KI8qI3B8o3lP9QLdoPBE>" flowId="KI8qI3B8o3lP9QLdoPBE" %}


---

# 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/dashboard-templates/trigger-hex-projects.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.