> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/getting-started-with-humanic/connecting-your-data.md).

# Connecting your Data

Humanic supports multiple options for connecting your data from uploading a simple .csv to integrating with your Data Warehouse. 

Data Connections are used to set up Triggered Campaigns, which automatically send onboarding, activation, or transactional emails to new users as they start using your product or app.

1. To send onboarding and activation emails, Humanic integrates with tools like Posthog, Segment, and Amplitude. The Humanic app is available on both the Segment and Amplitude app stores. 
2. Transactional emails can be triggered by connecting Humanic to data sources such as Stripe. For more details [click here](/humanic/transaction-emails.md)

{% hint style="info" %}
Uploading contacts using a .csv file will not trigger automated campaigns. These contacts can only be used for one-time campaigns.
{% endhint %}


---

# 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://humanic.gitbook.io/humanic/getting-started-with-humanic/connecting-your-data.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.