> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/project-management/basecamp/faq.md).

# FAQ

<details>

<summary>Does Coupler.io support Basecamp 2 or Basecamp Classic?</summary>

No. Only **Basecamp 3** accounts are supported. If you're on an older version, you'll need to upgrade your Basecamp account before connecting.

</details>

<details>

<summary>Where do I find my Basecamp API token?</summary>

Go to [launchpad.37signals.com/integrations](https://launchpad.37signals.com/integrations) while logged into your Basecamp 3 account. Under the **API tokens** section, generate a personal access token. Copy it right away — you may not be able to view it again after leaving the page.

</details>

<details>

<summary>Can I pull data from multiple Basecamp accounts into one report?</summary>

Yes. Add multiple sources to the same data flow — one per Basecamp account — and use the **Append** transformation to combine them. This works well if your organization manages separate Basecamp accounts by team or client.

</details>

<details>

<summary>Why are my assignee fields showing as arrays or JSON instead of names?</summary>

Basecamp returns assignees and participants as lists. The raw output is an array, which some destinations display as a JSON string. Use your destination's split or flatten function to convert these into readable values. See the Data Overview for field details.

</details>

<details>

<summary>Can I get only incomplete (open) todos?</summary>

Coupler.io pulls all todos based on your start date. To filter for open tasks, apply a filter in your destination (e.g., a filter on `completed = false` in Google Sheets or a WHERE clause in BigQuery). This approach is more flexible than restricting the source, since it lets you report on both open and closed tasks from the same data flow.

</details>

<details>

<summary>What's the difference between Schedules and Schedule entries?</summary>

Schedules are the calendar tool containers attached to a project. Schedule entries are the individual events, milestones, or deadlines inside those containers. You need to add **Schedule entries** as its own entity to see the actual events — pulling Schedules alone only gives you the container metadata.

</details>

<details>

<summary>Can I send Basecamp data to an AI tool?</summary>

Yes. Coupler.io supports AI destinations including **ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw**. This is especially useful for Messages data, where AI tools can summarize discussions, extract decisions, or flag action items automatically.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

This depends on your start date setting. You can set it as far back as your Basecamp account history goes. For large accounts with years of data, consider starting with a recent date range, validating the output, then adjusting the start date to pull older records.

</details>

{% hint style="info" %}
For field-level details on each entity, see the [Data Overview](/sources/category/project-management/basecamp/data-overview.md). For connection errors or missing data, check [Common Issues](/sources/category/project-management/basecamp/common-issues.md).
{% endhint %}


---

# 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.coupler.io/sources/category/project-management/basecamp/faq.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.