> 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-census-syncs.md).

# Trigger Census Syncs

Learn how to automatically trigger Census 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 Census sync:

* Census receives the webhook
* Sync process begins immediately
* Fresh data flows to your operational tools

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

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

* Automatic Census sync triggering after successful Bolt runs
* Real-time data synchronization with operational tools
* Streamlined workflow between dbt™ pipelines and data syncs
* Faster time-to-value for fresh data
  {% endhint %}

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

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Census account with configured syncs
* Census Sync Trigger API URL
  {% endhint %}

***

### Setup Guide

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

#### Step 1: Get Your Census Sync URL

1. Open [Census](https://app.getcensus.com/) and navigate to your syncs
2. Find and select the sync you want to trigger
3. In the Sync Trigger section, copy the API URL

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

#### Step 2: Configure the Webhook

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 use the "Trigger Census Sync" template
3. Enter your Census Sync URL.

{% code title="Example Sync URL: " %}

```
https://bearer:secret-token%3AqhvcTdAX5tLV3J4JLUAVigdD@app.getcensus.com/api/v1/syncs/2511163/trigger
```

{% endcode %}

4. Click "Connect"

<figure><img src="/files/ISYezj8ZBwse9p5Io57V" 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](https://app.paradime.io/bolt/webhook)
   * Select your Census Sync Webhook
   * Check the Endpoints tab to verify the webhook triggered

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


---

# 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-census-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.