> 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/wootric.md).

# Wootric

### Overview

The [Wootric](https://www.wootric.com/) connector allows Birdie to import NPS survey responses directly from Wootric's REST API. See the [Wootric API documentation](https://docs.wootric.com/api/) for more information about the platform.

### Requirements

To access data through the Wootric API, you need:

* **Client ID** — Unique identifier for your application
* **Client Secret** — Secret key for your application

To obtain the `client_id` and `client_secret`:

1. Log into your **Wootric Account** (admin access required).
2. In the dashboard, navigate to **Settings** or **Integrations**.
3. Within the Integrations section, look for **API** or **API Keys**.
4. Copy the `client_id` and `client_secret` (or re-generate if needed).

> Depending on your account and the data you wish to integrate, you might need to configure specific permissions. Confirm with Wootric or consult the API documentation for any additional scopes.

### Share Connection Details with Birdie

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

```json
{
  "connection_details": {
    "client_id": "your-wootric-client-id",
    "client_secret": "your-wootric-client-secret",
    "grant_type": "client_credentials"
  }
}
```

| Section              | Field           | Required | Description                                      |
| -------------------- | --------------- | -------- | ------------------------------------------------ |
| `connection_details` | `client_id`     | Yes      | Wootric API Client ID.                           |
| `connection_details` | `client_secret` | Yes      | Wootric API Client Secret.                       |
| `connection_details` | `grant_type`    | Yes      | Authentication method. Use `client_credentials`. |

[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.

### Integration with Birdie

Birdie imports Wootric NPS responses by checking for updates through the `created_at` field, ensuring that only the most recent changes are captured without re-importing old data.

**Data Imported**

For each survey response, Birdie extracts:

* NPS score (rating)
* Response text
* Date posted
* End-user properties (as additional fields)
* Tags

**Example Feedback**

Raw data from Wootric API:

```json
{
  "id": 1,
  "score": 9,
  "text": "Great product, very intuitive.",
  "created_at": "2024-07-01 10:30:00 -0300",
  "tags": ["PRODUCT"],
  "end_user": {
    "properties": {
      "persona": "Individual",
      "pricing_plan": "Enterprise"
    }
  }
}
```

Feedback imported into Birdie:

```json
{
  "kind": "nps",
  "rating": 9,
  "text": "Great product, very intuitive.",
  "posted_at": "2024-07-01 10:30:00 -0300",
  "additional_fields": {
    "end_user.persona": "Individual",
    "end_user.pricing_plan": "Enterprise"
  }
}
```

### Custom Fields

All additional data provided by Wootric's API that doesn't fit into the main schema can be imported by Birdie as "additional fields". Additional fields can be configured as custom fields in the Birdie App, enabling text search and filtering.

If your Wootric setup includes custom properties for NPS surveys, they can be mapped directly into Birdie, preserving your unique data structure.

### References

* [Wootric](https://www.wootric.com/)
* [Wootric API Documentation](https://docs.wootric.com/api/)
* [Securely Sharing Credentials](/integrations-and-data-ingestion/securely-sharing-credentials-for-data-integration.md)


---

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