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

# Typeform

### Overview

This integration imports form responses from your **Typeform** account into Birdie. Below are key details about what we need to set up the integration and how form responses and data are imported.

### Requirements

For Birdie to authenticate with the **Typeform API** and import data, you'll need to generate an **Personal token** (an auto-generated password). The token is used to authenticate API requests.

### Setup in the third‑party tool

{% stepper %}
{% step %}

#### Accessing your Typeform account

* If you are not logged in, please log in to your [Typeform](https://admin.typeform.com/login) account.
* Go to **Account Settings**

![](/files/NrrFUtJlh1fSrkIx6F6N)

* In the left menu, click in [**Personal tokens**](https://admin.typeform.com/user/tokens).

![](/files/x0UZt7me8yA9oRoQ3Mp4)
{% endstep %}

{% step %}

#### Generate an API Key

* Click in **Generate a new token**.

![](/files/aJHiZPwV5B7DtiXhN4a5)

* In the **Token name** field, enter a name for your **Personal Token**. Customize the name field as you wish, we recommend using a descriptive name such as: `BirdieAI Integration`.
* Birdie integration only requires **READ** scopes for:

  * Accounts
  * Forms
  * Responses
  * Webhooks

  ![](/files/1PzwEXlexmbcJGnXK4bR)
* Click **Generate token**.

{% hint style="warning" %}
Permissions cannot be changed once the key is created.
{% endhint %}
{% endstep %}
{% endstepper %}

### Delete an API Key

If you suspect a token has been compromised, delete it immediately. Deleting a token will deactivate it permanently.

* Go to [**Personal tokens**](https://admin.typeform.com/user/tokens) page.
* Identify the token you want to delete.
* Click in the **three dots button** in the right-side of the list.
* Click **Delete this token**.

![](/files/geuiDZlFRseeX1hxROGi)

When using **Personal Tokens**, keep the following in mind:

* The token cannot be edited, only deleted.
* When selecting roles, be mindful of what permissions are necessary for this token. For example, if a service only requires READ access, you can create a token with just this scope.
* Provide a helpful naming to your API Key since your team may use dozens of tokens along the way.

### Connect to Birdie

Once you have generated an **Personal Token**, [share securely](https://ask.birdie.ai/integrations-and-data-ingestion/securely-sharing-credentials-for-data-integration) with the Birdie team:

* The generated **Personal Token**.

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

### References

* [Get Started](https://www.typeform.com/developers/get-started/)
  * [Personal Access Token](https://www.typeform.com/developers/get-started/personal-access-token/)


---

# 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/typeform.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.
