Connect Basecamp to OverlayQA
Last updated: October 26, 2026
Connecting Basecamp to OverlayQA lets you export design QA issues to a Basecamp to-do list and keep their status and comments in step. Each issue becomes a to-do named after the issue, with the page URL, element selector, computed CSS values, severity, browser and viewport inside it. Screenshots and comment files are uploaded to Basecamp and shown in the to-do, and each to-do links back to the OverlayQA issue.
Connect Your Basecamp Account
- Open Integrations in the OverlayQA dashboard and click Connect on the Basecamp card.
- A 37signals sign-in page opens. Sign in with the login that owns your Basecamp projects and approve access for OverlayQA.
- Back in OverlayQA, the Basecamp card shows as connected.
Tip: You only need to connect once. OverlayQA remembers the Basecamp connection for every later export. A 37signals login with no Basecamp account cannot be connected: sign in to the account that owns your Basecamp projects, then connect again.
Choose a Destination
Every export asks where the to-do should go:
| Setting | Details |
|---|---|
| Project | A Basecamp project your login can reach. If the login reaches more than one Basecamp account, each project is shown with its account name. |
| To-do list | The to-do list the to-do is created in. A project needs To-dos turned on and at least one to-do list. |
Export Issues
- Open an issue and choose Export to Basecamp from its actions menu, or select several issues and export them with bulk actions.
- Pick the project and the to-do list.
- Confirm. OverlayQA uploads the screenshots and creates one to-do per issue.
Exports work on the dashboard and in Team Review. Bulk actions handle up to 100 issues at a time.
What Gets Exported
| Field | Description |
|---|---|
| To-do name | The issue title from OverlayQA. |
| Description | The issue description, page URL, Figma frame link when there is one, type, severity, browser, OS, viewport, element tag and CSS selector, computed CSS values, AI analysis, the comments present at export time, and an Open in OverlayQA link back to the issue. |
| Screenshots and files | The element screenshot and, when captured, the full-page screenshot, plus any files attached to comments. They are uploaded to Basecamp and shown inside the to-do. |
What Is Not Exported
Note: There is no field picker for Basecamp: to-dos are created without an assignee or a due date, and you set those in Basecamp. CSS values are the computed values from the live page, not the expected values from a Figma design.
After Exporting
On the dashboard, the issue lists the Basecamp to-do with an Open link to it.
What Syncs Back
Changes to an exported to-do come back to OverlayQA. Completing the to-do in Basecamp marks the issue Resolved, reopening it marks the issue Open, and moving it to the trash or archiving it marks the issue Closed. A comment on the to-do appears on the OverlayQA issue with the commenter's name.