Table of contents
WorkSights integrates with Basecamp to display project activity as structured signals on the timeline. When mapped users create messages, to-dos, comments, files, or scheduled events, WorkSights receives metadata and surfaces it as clear activity entries. This gives teams visibility into ongoing work without exposing sensitive content.
How Basecamp Data Appears in WorkSights
Each Basecamp activity appears as an individual entry on the timeline with the associated project name and object context (such as message subject, to-do title, or file name). WorkSights uses distinct icons for messages, to-dos, files, comments, and scheduled events to make activity types easy to recognize.
Because Basecamp's scheduling API provides minimal information, scheduled events appear as simple activity entries rather than full calendar items.
WorkSights represents Basecamp activity using existing WorkSights activity categories (such as Task for to-dos and General for messages and comments). Each category follows WorkSights's standard color system.
Objects WorkSights Syncs from Basecamp
WorkSights receives metadata for the following Basecamp objects:
Messages — message creation, updates, and related comments
Comments — comments on messages, files, and to-dos
To-dos — to-do list creation, to-do creation, updates, and completions
Files — file uploads and file comments
Scheduled Events — event creation with limited metadata
WorkSights does not ingest message bodies, comment text, file content, or schedule notes.
Integration Page Overview
The Basecamp integration page contains:
- Overview Tab — connection details and integration owner
- Users Tab — Basecamp users mapped to WorkSights users
- Connections Tab — connected Basecamp accounts
Only mapped users generate Basecamp activity inside WorkSights.
Data Access and Privacy
WorkSights ingests only the metadata required to represent Basecamp activity. This includes object names, timestamps, references to the originating project, and the identity of the user who performed the action.
WorkSights does not receive message text, comment bodies, file contents, attachment data, or schedule descriptions.
The integration follows Basecamp's permission model, and WorkSights displays only the information accessible to the Basecamp account used during setup. All processing remains metadata-only and avoids storing or exposing sensitive content from within Basecamp.
Troubleshooting
If Basecamp activity does not appear, check that the relevant Basecamp user is mapped to a WorkSights user, confirm that OAuth permissions were approved, verify that the activity occurred after the connection was established, or reconnect the integration if the authorization token has expired.
For connection steps, see the Basecamp Setup Guide.