Common Issues

Connection issues

My API token isn't being accepted

Make sure you're using a personal access token from 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.

I can't find my Basecamp account in the dropdown

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.

The connection fails with an "unsupported account" error

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.

Missing data

Some projects or tasks aren't showing up

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.

Archived or trashed projects are missing

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.

Schedule entries aren't appearing even though schedules are pulling correctly

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.

Permission errors

I get a 403 Forbidden error when pulling data

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.

Data discrepancies

Task counts in Coupler.io don't match what I see in Basecamp

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.

Assignee or participant fields show raw arrays instead of names

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.

Rate limits

Sync is slow or failing with rate limit errors

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.

Avoid running very large syncs (long date ranges, many projects) simultaneously — this increases the chance of hitting Basecamp's API rate limits.