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

# Basecamp

Connect Basecamp projects, todos, and schedules to Google Sheets or BigQuery with Coupler.io for unified project reporting.

Basecamp is a project management and team collaboration tool that keeps tasks, messages, schedules, and discussions in one place. Connecting it to Coupler.io lets you pull your project data into spreadsheets, dashboards, or AI tools — without manual exports.

**Why connect Basecamp to Coupler.io?**

* Consolidate todos, messages, and schedule entries across all projects into a single report
* Analyze task completion rates and project activity in Google Sheets, Excel, or BigQuery
* Combine Basecamp data with other sources (like CRM or time tracking tools) using Join or Append transformations
* Send project updates to AI destinations like ChatGPT or Claude for summaries and insights

## Prerequisites

* A Basecamp 3 account (Basecamp 2 and Classic are **not** supported)
* Your Basecamp Account ID
* A Basecamp API token (you'll generate this during setup)

## Quick start

{% hint style="success" %}
If you want a broad project health view, start with the **Projects** and **Todos** entities combined in one data flow using the Append transformation.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Go to your Coupler.io workspace and click **Add data flow**. Search for and select **Basecamp** as your source.
{% endstep %}

{% step %}
**Get your Basecamp API token.** Log in to Basecamp and go to [launchpad.37signals.com/integrations](https://launchpad.37signals.com/integrations). Under **API tokens**, generate a personal access token and copy it.
{% endstep %}

{% step %}
**Enter your credentials in Coupler.io.** Paste your API token when prompted. Then select your **Basecamp account** from the dropdown — this is your Basecamp 3 account ID.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to choose the earliest date for syncing records. Only data created on or after this date will be exported.
{% endstep %}

{% step %}
**Choose an entity.** Select which data you want to pull: Projects, Schedules, Schedule entries, Todos, or Messages.
{% endstep %}

{% step %}
**Choose a destination and run.** Pick a destination — Google Sheets, Excel, BigQuery, Looker Studio, or an AI tool like ChatGPT or Gemini. Then click **Run** to complete your first manual sync.
{% endstep %}
{% endstepper %}

## Basecamp data overview

When you connect Basecamp to Coupler.io, you can pull five types of data, each mapping to a distinct part of how Basecamp organizes work. Here's what's available and how to use it.

## Available entities

| Entity           | What it contains                                      |
| ---------------- | ----------------------------------------------------- |
| Projects         | Project names, statuses, dates, and metadata          |
| Schedules        | Schedule tools attached to each project               |
| Schedule entries | Individual calendar events, deadlines, and milestones |
| Todos            | Tasks and to-do lists, including status and assignees |
| Messages         | Message board posts and discussion threads            |

#### Projects fields

| Field       | Description                                |
| ----------- | ------------------------------------------ |
| id          | Unique project identifier                  |
| name        | Project name                               |
| description | Project description                        |
| status      | Active, archived, or trashed               |
| created\_at | Date and time the project was created      |
| updated\_at | Date and time the project was last updated |
| purpose     | Internal or external classification        |

#### Schedules fields

| Field          | Description                         |
| -------------- | ----------------------------------- |
| id             | Unique schedule identifier          |
| project\_id    | ID of the associated project        |
| title          | Schedule name                       |
| entries\_count | Number of entries in the schedule   |
| created\_at    | Date the schedule was created       |
| updated\_at    | Date the schedule was last modified |

#### Schedule entries fields

| Field        | Description                              |
| ------------ | ---------------------------------------- |
| id           | Unique entry identifier                  |
| schedule\_id | ID of the parent schedule                |
| title        | Entry title or event name                |
| starts\_at   | Entry start date/time                    |
| ends\_at     | Entry end date/time                      |
| all\_day     | Whether the entry spans the full day     |
| creator      | Name of the person who created the entry |
| participants | List of assigned participants            |

#### Todos fields

| Field         | Description                               |
| ------------- | ----------------------------------------- |
| id            | Unique task identifier                    |
| title         | Task description                          |
| project\_id   | ID of the project the task belongs to     |
| completed     | Whether the task is complete (true/false) |
| due\_on       | Due date                                  |
| assignees     | People assigned to the task               |
| created\_at   | Date the task was created                 |
| completed\_at | Date the task was completed               |
| creator       | Name of the person who created the task   |

#### Messages fields

| Field           | Description                              |
| --------------- | ---------------------------------------- |
| id              | Unique message identifier                |
| project\_id     | ID of the project the message belongs to |
| subject         | Message subject line                     |
| content         | Body text of the message                 |
| creator         | Author of the message                    |
| created\_at     | Date and time the message was posted     |
| comments\_count | Number of comments on the message        |

## Common metric combinations

* **Todos + Projects** — Join on `project_id` to see task volume and completion rates per project
* **Schedule entries + Projects** — Join on `project_id` to map upcoming milestones to project names
* **Todos (filtered by completed = false)** — Surface overdue or unassigned open tasks across all projects
* **Messages + Todos** — Append into a single activity feed to track overall project engagement

## Use cases by role

{% tabs %}
{% tab title="Project managers" %}

* Track open vs. completed todos across all projects in a single dashboard
* Monitor upcoming schedule entries and deadlines in Google Sheets or Looker Studio
* Use the Aggregate transformation to count tasks by assignee and spot workload imbalances
  {% endtab %}

{% tab title="Operations teams" %}

* Export Projects data to BigQuery for long-term project portfolio reporting
* Combine Basecamp todos with time-tracking data from another source using Join to calculate effort per task
* Send weekly todo summaries to ChatGPT or Claude for automated status reports
  {% endtab %}

{% tab title="Leadership" %}

* Get a high-level view of project statuses (active, archived) to assess portfolio health
* Use Messages data to gauge team communication volume across projects
* Feed project and schedule data into Gemini or Perplexity for AI-generated project briefs
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Only **Basecamp 3** accounts are supported — Basecamp 2 and Classic will not connect
* The **start date** parameter controls how far back data is synced; records created before that date are excluded
* Todos include both individual tasks and entire to-do lists — filter by type in your destination if needed
* Archived and trashed projects are included in the Projects entity and can be filtered by the `status` field
* Participants and assignees may return as arrays — flatten these in your destination tool if you need one row per person

## Basecamp common issues

### Connection issues

<details>

<summary>My API token isn't being accepted</summary>

Make sure you're using a **personal access token** from [launchpad.37signals.com/integrations](https://launchpad.37signals.com/integrations), not an OAuth token from a third-party app. Copy the token immediately after generating it — it may not be shown again.

</details>

<details>

<summary>I can't find my Basecamp account in the dropdown</summary>

You may have multiple 37signals accounts. Make sure you're logged into the correct Basecamp 3 account when generating the token. If the account still doesn't appear, try regenerating the token while signed into only the account you want to connect.

</details>

<details>

<summary>The connection fails with an "unsupported account" error</summary>

This usually means you're trying to connect a Basecamp 2 or Basecamp Classic account. Coupler.io only supports **Basecamp 3**. There's no workaround for older account versions.

</details>

### Missing data

<details>

<summary>Some projects or tasks aren't showing up</summary>

Check your **start date** setting. If the missing records were created before the date you specified, they won't be included in the export. Use the date picker to set an earlier start date and re-run the data flow.

</details>

<details>

<summary>Archived or trashed projects are missing</summary>

Archived and trashed projects are included in the Projects entity, but double-check that you're not filtering them out in your destination. Look for a `status` column and remove any filters on it.

</details>

<details>

<summary>Schedule entries aren't appearing even though schedules are pulling correctly</summary>

Schedules and Schedule entries are separate entities — you need to add **Schedule entries** as its own source in your data flow. Adding only Schedules will not include the individual events.

</details>

### Permission errors

<details>

<summary>I get a 403 Forbidden error when pulling data</summary>

Your API token may belong to a user who doesn't have access to certain projects. In Basecamp 3, project access is set per person. Ask your Basecamp admin to either grant the token owner access to those projects or generate a token from an admin account.

</details>

### Data discrepancies

<details>

<summary>Task counts in Coupler.io don't match what I see in Basecamp</summary>

The Todos entity includes both to-do list containers and individual tasks. If you're counting rows to estimate task numbers, filter by the record type field to isolate individual tasks. Also verify that your start date isn't excluding older tasks.

</details>

<details>

<summary>Assignee or participant fields show raw arrays instead of names</summary>

Basecamp returns assignees and participants as arrays. Depending on your destination, these may appear as JSON strings. Use your destination's array-flattening or split function to convert them into readable columns.

</details>

### Rate limits

<details>

<summary>Sync is slow or failing with rate limit errors</summary>

Basecamp's API enforces rate limits on requests. If you're pulling multiple entities in the same data flow and hitting limits, try splitting them into separate data flows and running them at staggered times.

{% hint style="warning" %}
Avoid running very large syncs (long date ranges, many projects) simultaneously — this increases the chance of hitting Basecamp's API rate limits.
{% endhint %}

</details>

## Basecamp 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](#basecamp-data-overview). For connection errors or missing data, check [Common Issues](#basecamp-common-issues).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/project-management/basecamp.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.
