# Basecamp AI automation and integrations

> Basecamp has a REST API authenticated with OAuth 2.0 through 37signals Launchpad, plus per-project webhooks. Zapier and Make have built-in Basecamp apps, and n8n connects through its HTTP Request node. Useful AI automations turn emails into to-dos, post meeting summaries to message boards and write weekly client status updates. Expect a limit of about 50 requests per 10 seconds per IP.

- Category: Project Management
- Vendor: https://basecamp.com/
- How to connect: Basecamp REST API; Webhooks; Zapier and Make apps; n8n HTTP Request node
- Authentication: OAuth 2.0 through 37signals Launchpad, which returns the Basecamp accounts the user can access
- Notes: Every request must include a User-Agent header naming your app with a contact URL or email, or Basecamp returns 400. Access tokens expire, so the integration must store and use refresh tokens.
- Last updated: 2026-10-14

## What you can automate with Basecamp

- **Email to to-do.** Turn client emails into to-dos in the right project and list, with an AI summary, assignee and due date proposed for confirmation. Guide: https://www.lumeor.studio/guides/ai-email-to-task-automation/
- **Meeting summaries on the message board.** Post a short summary of each client or team call to the project's message board and add the action items as to-dos. Guide: https://www.lumeor.studio/guides/ai-meeting-summaries-and-action-items/
- **Weekly client status updates.** Read completed and open to-dos and recent messages in each project and draft a status message for the project lead to post. Guide: https://www.lumeor.studio/guides/automate-project-status-updates/
- **Cross-project operations report.** Summarize overdue work and activity across all active projects into one weekly report for owners. Guide: https://www.lumeor.studio/guides/automate-weekly-ops-reporting/
- **New hire and new client projects.** Create a project from a template when a hire or client signs, invite the right people and set to-do dates. Guide: https://www.lumeor.studio/guides/automate-employee-onboarding/
- **Check-in answer digest.** Summarize answers to automatic check-in questions across the team into themes and open issues for the manager.

## What makes Basecamp easy (and a little manual) to automate

Basecamp organizes work into projects, and each project has a fixed set of tools: message board, to-dos, schedule, docs and files, chat and automatic check-ins. The API reflects that structure, with each item stored as a recording inside a project. Once you know the IDs of a project's to-do set or message board, creating and reading items is simple.

Zapier and Make both have Basecamp apps. n8n has no dedicated node, so we use HTTP Request nodes with the required User-Agent header. That is not much extra work, since the API is small and stable.

The manual part is discovery. To post to a project, a workflow first looks up the project's dock to find the IDs of its tools. Pagination is also unusual: page sizes grow from page to page, and you must follow the Link header rather than build page URLs.

## The AI layer

Basecamp is popular with agencies, consultancies and small teams that run client work in it. AI saves time on the writing around that work:

- **Capturing requests** from email and calls as to-dos, as covered in [turning emails into tasks with AI](/guides/ai-email-to-task-automation/).
- **Summarizing** calls and posting them where the client and team will read them.
- **Status drafting** across projects, as in [automated project status updates](/guides/automate-project-status-updates/).

Basecamp's philosophy favors calm, written communication. AI drafts should be short, plain and edited by a person before they post.

## Limits to plan around

- **Rate limits.** The commonly hit limit is 50 requests per 10 seconds per IP address. Other limits apply over longer windows and can change, so honor 429 responses and the Retry-After header.
- **User-Agent header** on every request.
- **Geared pagination.** Follow the Link header and use X-Total-Count to size jobs.
- **Account selection.** Launchpad can return several Basecamp accounts for one user. Store the account ID the workflow should use.

## How Lumeor typically connects it

We register an OAuth app with 37signals, store refresh tokens in n8n, and build a small set of reusable HTTP Request nodes for project lookup, to-do creation and message posting. Webhooks per project feed a single n8n webhook endpoint. For agencies, the weekly status flow often pairs with an [operations report](/guides/automate-weekly-ops-reporting/) for the owners across every active project.

## Frequently asked questions

### Does n8n have a Basecamp node?

Not a built-in one. n8n connects through the HTTP Request node with an OAuth 2.0 credential pointed at 37signals Launchpad, and a Webhook node receives Basecamp webhook events. Zapier and Make both have built-in Basecamp apps for common triggers and actions.

### Why does the Basecamp API return 400 Bad Request?

The most common cause is a missing User-Agent header. Basecamp requires every request to identify your application and include a link or email address. Generic HTTP clients that send no User-Agent, or a default one, are rejected.

### Can AI write our Basecamp client updates?

It can draft them from project activity, covering what was completed, what is next and what is waiting on the client. The project lead should review and post, because client updates carry commitments and tone that need a human check.

### How do Basecamp webhooks work?

Webhooks are created per project and fire on events such as new to-dos, completed to-dos, messages and comments. Each payload includes the event kind and the recording that changed, so a workflow can fetch more detail only when it needs it.

---

Source: https://www.lumeor.studio/tools/basecamp/
Published by Lumeor Studio, Newtown, PA. hello@lumeor.studio. Get a written scope: https://www.lumeor.studio/start/