
Table of contents
Basecamp Integration Overview
The Basecamp integration brings project activity onto the WorkSights timeline. When mapped users create to-dos, post messages, add comments, or update scheduled events, WorkSights records each as a structured timeline entry.
WorkSights does not import historical Basecamp data. Activity appears from the point of connection onwards.
For connection steps, see Basecamp Setup.
What WorkSights Receives
WorkSights captures to-do creation, updates, completions, and deletions; message board posts and updates; comments on any Basecamp recording; and schedule entry creation and updates.
User Mapping
WorkSights imports Basecamp users and matches them to WorkSights users by email. After import, activity is attributed by Basecamp person id. Mapping is managed from the Users tab on the Service Details page.
Basecamp external collaborators are not mapped as scored WorkSights users. When an external collaborator's email matches a known client contact, their activity appears on ClientSights as client-authored activity. If their email does not resolve to a known client contact, their events are not captured.
How It Appears in WorkSights
Basecamp activity appears in three categories: Task, General, and Calendar Change.
To-Dos
To-dos are categorized as Task. They appear with the full project hierarchy in the title: Project > To-do list > To-do > Action. Creation, updates, completions, and deletions are all captured. When the same user makes several changes to the same to-do within 10 minutes, WorkSights consolidates them into a single activity.
Messages and Comments
Messages and comments are categorized as General. Messages show the project and message board context. Comments show the project and the object they belong to, whether that is a message, a to-do, or a scheduled entry. Comment text is not stored; only this metadata appears.
Schedule Entries
Schedule entries are categorized as Calendar Change. Creation and updates appear with the project context and the entry title.
What Is Not Captured
WorkSights does not ingest Basecamp Docs, file uploads, Campfire chat, check-ins, or any recording type beyond the four above. Document bodies, message bodies, and comment text are never received. Only titles, hierarchy, and timestamps are stored.
Integration Page Overview
The Basecamp Service Details page has three tabs: Overview, Users and Connections. See Connected Services and Service Details for how these tabs work.

Troubleshooting
No activity appearing
Confirm the affected user is mapped in the Users tab and has an active Basecamp subscription in WorkSights. Basecamp is an all-or-nothing subscription with no per-feature toggles. Also confirm the activity occurred after the connection was made, as no historical data is imported.
Activity is delayed
This is expected. Basecamp notifies WorkSights as changes happen, and activity appears within about 20 minutes.
A whole activity type is missing
Only to-dos, messages, comments, and schedule entries are ingested. Docs, files, Campfire, and check-ins are not supported.
Client activity is not appearing on ClientSights
The external collaborator's email may not match a known client contact for that account. Client-authored activity only appears when the creator's email resolves to an existing ClientSights contact.
Activity stopped after reconnecting
Webhooks are registered only when you connect or reconnect. If your Basecamp URL has changed, reconnect from the Service Details page so the webhook is registered at the new address.