> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/data-warehouse.md).

# Data Warehouse

Sync customer issue data directly into your warehouse

Without any engineering effort, sync customer data directly into your warehouse.

* Select the data columns you care about
* Select a cadence for the sync
* Data will automatically be upserted into your warehouse
* New data will be inserted as new rows into the table
* Updated data will be replace existing rows in the table
* New data columns can be subscribed to as they become available

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2Fhbu9kpXde6wYTD2A3V6x%2FCleanShot%202024-10-10%20at%2020.18.16%402x.png?alt=media&amp;token=bb95c55a-4fa3-443f-a519-7bc24977dae4" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If your warehouse restricts network access, allowlist [Pylon's IP addresses](https://docs.usepylon.com/pylon-docs/security/ip-addresses.md) for your region before you set up the sync.
{% endhint %}

## Failed syncs

If a sync fails 3 times in a row, Pylon pauses it so it stops retrying against a broken connection. Temporary warehouse errors, such as BigQuery backend, internal, timeout, or rate-limit errors, don't count toward this; the sync retries on its next run. A paused sync shows as **Inactive** in your list of syncs, and its toggle reads **Disconnected**.

When a sync is paused, Pylon sends an alert with the last error from your warehouse. To choose who gets it, open your warehouse app in the App Directory. Under **Notifications**, turn on alerts for errors and add Slack channels or email addresses. If notifications are off, Pylon emails the person who created the sync.

To resume syncing, fix the error in your warehouse, such as missing permissions or expired credentials. Then open the sync and switch it back to **Connected**.

{% content-ref url="/pages/kcfYpVMtk8aUHYNBU3jk" %}
[Snowflake](https://docs.usepylon.com/pylon-docs/integrations/data-warehouse/snowflake.md)
{% endcontent-ref %}

{% content-ref url="/pages/CCvYpOwGiC8koinoorRo" %}
[BigQuery](https://docs.usepylon.com/pylon-docs/integrations/data-warehouse/bigquery.md)
{% endcontent-ref %}

{% content-ref url="/pages/fRID7UTUjOPlL6crr3Ua" %}
[Redshift](https://docs.usepylon.com/pylon-docs/integrations/data-warehouse/redshift.md)
{% endcontent-ref %}

{% content-ref url="/pages/r8JH5VdH86YHm1toVT0q" %}
[AWS S3](https://docs.usepylon.com/pylon-docs/integrations/data-warehouse/aws-s3.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/integrations/data-warehouse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
