> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/workflow-builder/apps/hightouch.md).

# Hightouch

**What is Hightouch?**

Hightouch is a powerful integration node in StackAI that enables seamless data synchronization between your data warehouse and various business applications. With Hightouch, you can automate workflows, trigger actions, and keep your business tools up-to-date with the latest data.

**How to use it?**

To use the Hightouch node in StackAI, add it to your workflow and select the desired action. Configure the required inputs and connection settings, then connect it to other nodes to automate data-driven processes. Hightouch supports a variety of actions, allowing you to query sources and destinations, and orchestrate data syncs.

**Example of Usage**

Suppose you want to list all available sources in your Hightouch account. You would add the Hightouch node, select the "List Source" action, provide your connection ID, and connect the output to a display or processing node.

***

**Available Actions in Hightouch**

Below are the most commonly used Hightouch actions in StackAI:

***

#### 1. List Source

**Description:**\
Retrieves a list of all data sources connected to your Hightouch account.

**Inputs:**

* None required.

**Configurations:**

* `connection_id` (Required): The unique identifier for your Hightouch connection.

**Outputs:**

* `sources` (Required): An array of source objects, each containing details such as source name, type, and status.

**Example:**

```json
{
  "action_configurations": {
    "connection_id": "<your-hightouch-connection-id>"
  }
}
```

***

#### 2. List Destination

**Description:**\
Fetches all destinations configured in your Hightouch account.

**Inputs:**

* None required.

**Configurations:**

* `connection_id` (Required): The unique identifier for your Hightouch connection.

**Outputs:**

* `destinations` (Required): An array of destination objects, each with properties like destination name, type, and status.

**Example:**

```json
{
  "action_configurations": {
    "connection_id": "<your-hightouch-connection-id>"
  }
}
```

***

**How to Use These Actions in StackAI**

1. **Add the Hightouch Node:**\
   Drag the Hightouch node into your workflow.
2. **Select an Action:**\
   Choose "List Source" or "List Destination" based on your needs.
3. **Configure the Node:**\
   Enter your Hightouch connection ID in the configuration.
4. **Connect to Other Nodes:**\
   Use the output in downstream nodes for further processing or display.

***

**Example Workflow**

* Add Hightouch node → Select "List Source" → Set `connection_id` → Connect output to a Template or Output node to display the list of sources.

***

**Summary Table**

| Action           | Required Inputs | Required Configurations | Outputs      |
| ---------------- | --------------- | ----------------------- | ------------ |
| List Source      | None            | connection\_id          | sources      |
| List Destination | None            | connection\_id          | destinations |

***

Use the Hightouch node in StackAI to automate and streamline your data operations, ensuring your business tools always have the most up-to-date information.


---

# 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.stackai.com/workflow-builder/apps/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.