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

# Hightouch

{% content-ref url="/pages/18BJ1EXOUeuNcmclWpFV" %}
[Hightouch Metadata Extracted](/integrations/data-pipeline-tools/hightouch/metadata-extracted.md)
{% endcontent-ref %}

## **Getting Started with Hightouch** <a href="#h_3a4bfd6458" id="h_3a4bfd6458"></a>

There are two steps to get started using Hightouch with Secoda:

1. Create a Hightouch API key
2. Connect Hightouch to Secoda

#### Create a Hightouch API key <a href="#h_088224f7c9" id="h_088224f7c9"></a>

1\. Open up <https://app.hightouch.io> and login

2\. Go to **Settings -> API keys**

3\. Click the **Add API Key** button on the top right

#### **Connect Hightouch to Secoda** <a href="#h_276d2819e7" id="h_276d2819e7"></a>

After retrieving the API key, the next step is to connect Secoda:

1. In the Secoda App, select ‘Add Integration’ on the Integrations tab
2. Search for and select ‘Hightouch’
3. Enter your API key. This information is kept encrypted.
4. Click 'Connect'
5. After the extraction is complete your Hightouch Syncs will be in Secoda


---

# 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.secoda.co/integrations/data-pipeline-tools/hightouch.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.