> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/integrations-and-data-ingestion/how-to-integrate-with/indecx.md).

# IndeCX

### Overview

This integration imports survey responses and their related attributes from your IndeCX account into Birdie, so that you can centralize customer feedback from IndeCX alongside other sources. Below are key details about what we need to set up the integration and how responses and data are imported.

### Requirements

For Birdie to authenticate with the IndeCX Rest API and import data, you'll need to generate an API token (**called company-key**), used to authenticate API requests. Provide the Birdie team with the following:

* **Token**: API token provided by the IndeCX team

### Setup in the third‑party tool

To generate the company-key token, log in to your IndeCX account and go to your account settings. Copy and save the generated token, it will look something like this:

> $2b$10$BLV4CJAYKSTkktvkJTCVj.dM4H3lHKyiSjoRt3npXGxcNljXXXXX

{% hint style="info" %}
IndeCX's public documentation doesn't describe how to generate the company-key token. If you have any doubts about where to find it, contact the IndeCX team.
{% endhint %}

### Share Connection Details with Birdie

To configure the integration, securely provide Birdie with the following information.

```json
{
  "connection_details": {
    "token": "YOUR-INDECX-COMPANY-KEY",
    "surveys": ["SURVEY-1", "SURVEY-2"]
  }
}
```

| Section              | Field     | Required | Description                                                                                                            |
| -------------------- | --------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| `connection_details` | `token`   | Yes      | The company-key token generated for your IndeCX account.                                                               |
| `connection_details` | `surveys` | No       | List of surveys (called actions in IndeCX) to import. Omit to import every survey (action) available for your account. |

[Share credentials securely](/integrations-and-data-ingestion/securely-sharing-credentials-for-data-integration.md) with the Birdie team. Never send credentials via email or unencrypted channels.

The Birdie team will configure the connector and confirm once the integration is active.

### Data in scope

Through this integration, you can import both **NPS** and **CSAT** data. To ensure the integration works correctly, a survey must include exactly one question of either the **NPS** or **CSAT** type, surveys without one of these types are ignored.

Any other type provided along with an **NPS** or **CSAT** question will be considered an additional question, and its answer is appended to the imported response. For example, a survey with one **CSAT** question and one **TEXT** question is imported as a **CSAT** response with the **TEXT** answer appended to it.

For each answer related to **CSAT** or **NPS**, we extract the main fields for that interaction, such as Rating, Author Name and when the answer was posted. After that, the feedback is imported into Birdie and integrated into our application.

#### Custom fields

The integration will retrieve additional fields from the IndeCX API that don't fit into the main schema, these fields can be mapped directly into Birdie, preserving your unique data structure.

Once imported, IndeCX fields appear as Birdie custom fields, maintaining consistency across all platforms and enabling enhanced segmentation, filtering, and custom workflows in Birdie.

### References

* [IndeCX Docs](https://indecx.github.io/doc-indecx/)


---

# 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://ask.birdie.ai/integrations-and-data-ingestion/how-to-integrate-with/indecx.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.