Basecamp

Connect AI agents to Basecamp. Agents create and update projects, manage to-do lists and to-dos, post messages, comments, and Campfire lines, add schedule entries, and maintain documents so project chatter turns into tracked work.

37 actions OAuth available

Basecamp website ↗ Platform Documentation ↗ Capability data verified 2026-07-21

A new client engagement is signed and the details arrive from the CRM

Create Project spins up the delivery workspace with the engagement description

Create To-do List seeds the standard onboarding checklist for this service line

Create To-do assigns each kickoff task with due dates, with Notify emailing the assignees

Create Schedule Entry books the kickoff call on the project schedule with participants

Create Message posts the engagement brief to the message board where it will not scroll away

The delivery lead reviews the generated workspace and adjusts scope before the client joins

Create Campfire Line tells the team the project is live

What This Integration Enables

Basecamp's whole argument is that a project should live in one calm place: to-dos, message board, docs, schedule, and Campfire chat under one roof. The argument fails the moment work starts arriving somewhere else, and in most companies it always does. This connector closes that gap. FlowRunner agents turn form submissions, tickets, and leads into assigned to-dos with due dates, keep message boards and documents in sync with content produced elsewhere, post automated updates to Campfire, fan schedule entries out to project teams, and complete to-dos as downstream systems finish the work. The connector resolves each project's tool IDs from its dock automatically, so agents work with just a project ID rather than Basecamp's internal plumbing. And because agents can also provision whole projects, the workspace itself becomes reproducible: every engagement starts from the same checklist, with [human-in-the-loop](/concepts/human-in-the-loop) review before anything client-facing goes live.

Without FlowRunner

Work arrives outside the tool Requests land in email and chat, and someone has to remember to turn them into tasks

Project setup by copy-paste Every new engagement means rebuilding the same lists, events, and briefs by hand

Status updates as a chore The weekly digest exists only if a project manager compiles it

With FlowRunner

Everything becomes a tracked to-do Form submissions, tickets, and leads arrive as assigned to-dos with due dates

Workspaces born complete Projects appear with their checklists, schedule, and brief already in place

Digests that send themselves Open to-dos roll up into a daily summary without anyone chasing them

Use Case Scenarios

Intake that files itself

A support ticket in [Zendesk](/integrations/zendesk) gets tagged for the product team. The agent creates a to-do in the right project with Create To-do, assigns the owner by ID from List Project People, sets the due date from the SLA, and attaches the ticket detail with Create Comment. When the ticket closes, Complete To-do marks the task done and Basecamp notifies the completion subscribers. Nothing depends on someone remembering to transcribe the ticket.

The daily digest nobody compiles

Each morning, the agent runs List To-dos across active projects, groups open items by assignee and due date, and sends the digest through [Gmail](/integrations/gmail-service) to stakeholders while posting a short version to each project's Campfire with Create Campfire Line. Overdue items get a Create Comment nudge on the to-do itself, where the assignee will actually see it. The project manager reads the digest instead of building it.

Documents that stay current

A process runbook is generated from the operations wiki whenever procedures change. The agent writes it into the project's Docs and Files vault with Create Document, updates it in place with Update Document on each revision, and posts a Create Message announcement summarizing what changed. Meetings scheduled in [Google Sheets](/integrations/google-sheets) planning tabs become Create Schedule Entry events with the right participants. The project's vault stops drifting behind reality.

Human-in-Loop Highlight

Trash Project is the operation that ends a workspace: the project disappears from everyone's view immediately, and Basecamp permanently deletes it after 30 days, taking every to-do, message, document, schedule entry, and Campfire history with it. Trash Recording does the same to individual items. An end-of-engagement cleanup flow wants exactly these calls, which is why they never run on the agent's judgment. The agent presents the candidates: this project's engagement closed 90 days ago, its final invoice cleared, its documents were archived to the client folder. The operations lead confirms each one, and only then does Trash Project run. Thirty days of recoverability is a safety net, not a decision-maker; the decision to erase a client's project history belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

37 actions

Projects

List Projects Lists visible projects, active by default or archived and trashed, each with its dock of tool IDs.
Get Project Retrieves one project with its people access and dock. The one ID agents need; tool IDs resolve automatically.
Create Project Creates a project with name and description. The provisioning step for new engagements.
Update Project Changes a project's name or description, merging with current values.
Trash Project Moves a project to the trash, hidden immediately and permanently deleted after 30 days. The operation this page's human gate exists for.

To-dos

Get Todoset Retrieves the project's to-do container with list count and completion ratio.
List To-do Lists Lists a project's to-do lists with pagination, active by default.
Get To-do List Retrieves one list with its name, description, and completion ratio.
Create To-do List Creates a to-do list in a project. The checklist-seeding step.
Update To-do List Changes a list's name or description, merging with current values.
List To-dos Lists a to-do list's items with content, due dates, assignees, and completion state. The read behind every digest.
Get To-do Retrieves one to-do in full, including dates, assignees, and subscribers.
Create To-do Creates a task with assignees by people ID, due dates, and optional email notification. The intake workhorse.
Update To-do Updates a to-do safely by fetching and merging first, since the raw API replaces the whole record.
Complete To-do Marks a to-do done and notifies completion subscribers.
Uncomplete To-do Reopens a completed to-do onto the active list.

Recordings

Trash Recording Trashes any item by ID: to-dos, lists, messages, documents, comments, schedule entries, or chat lines. Runs only with review.

Messages

List Messages Lists a message board's posts with subject, content, and comment counts.
Get Message Retrieves one message with its full rich-text content.
Create Message Publishes a message to the board. Where agents post briefs and announcements that must not scroll away.
Update Message Changes a message's subject or content, merging with current values.

Comments

List Comments Lists the comments on any recording, paginated.
Get Comment Retrieves one comment with content and its parent recording.
Create Comment Comments on any recording, notifying its subscribers. The nudge and context-attach step.

Campfire

List Campfires Lists the chat rooms visible across all projects.
Get Campfire Lines Retrieves a campfire's messages, newest first, resolving the main campfire automatically.
Create Campfire Line Posts a chat line to a project's campfire. The lightweight status ping.

People

List All People Lists everyone on the account with IDs, emails, and roles. The directory for assignments.
List Project People Lists who can access a specific project. The source of valid assignee IDs.
Get Person Retrieves one person's profile by ID.
Get My Profile Returns the connected user's own profile and ID, for self-assignment and subscriptions.

Schedule

List Schedule Entries Lists a project's events with times and participants.
Create Schedule Entry Creates an event with ISO 8601 times, participants by ID, and optional notification.

Documents

List Documents Lists a project vault's documents with titles and comment counts.
Get Document Retrieves one document's full rich-text content.
Create Document Publishes a document to the vault. The landing step for generated runbooks and briefs.
Update Document Revises a document's title or content in place, merging with current values.

Frequently Asked Questions

What can FlowRunner do with Basecamp?

FlowRunner agents can run List Projects, Get Project, and Create Project in Basecamp, plus 34 more actions.

Does connecting Basecamp to FlowRunner require OAuth?

Yes. Basecamp connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Basecamp trigger a FlowRunner workflow automatically?

Basecamp doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Basecamp

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us