Basecamp + AI: Use Basecamp Through Juma's AI Workspace
Connect Basecamp to Juma and read projects, post messages, manage to-dos, and turn project work into finished deliverables and client reports through chat.
Key takeaways
Yes, you can use Basecamp through AI
37signals made Basecamp agent-accessible in 2026, and Juma connects over OAuth to read projects and post work back.
Read and write through chat
Summarize message boards, find and update to-dos, post messages, and drop finished deliverables onto the right project.
AI access on Basecamp's terms
Basecamp ships no native AI by design; Juma is the agent you bring, so the tool stays calm and uncluttered.
Fill the gaps Basecamp leaves on purpose
By pairing it with Google Analytics for client reporting, Webflow for publishing, and your ad accounts for campaigns.
400+ marketing teams use Juma
Including Salesforce, Maersk, and Costa Coffee. 4.9/5 on G2.
Enterprise-grade by default
SOC 2 Type II, ISO 27001, GDPR, HIPAA. Zero data retention from AI providers. Strategy, taste, and judgment stay human.
Can I access Basecamp through AI?
This is a notable stance, and it shapes the integration. 37signals ships no native AI inside Basecamp because, in their words, it is hard to make AI that is genuinely good and welcomed by users. Instead they built the rails (a revamped API, a command-line interface, and an agent skill) so teams can bring their own assistant. As DHH put it, anything you can do in Basecamp, agents can now do too. Juma is that assistant: AI access on Basecamp's terms, which keeps Basecamp calm and uncluttered rather than bolting features onto it.
The connection runs at the user level: each teammate authorizes Juma with their own Basecamp login over OAuth, so the projects, to-dos, and messages Juma can reach match that person's existing access. Because Basecamp's agent surface supports write actions, Juma can post messages, create and update to-dos, and upload files, not just read. Destructive actions like trashing a project sit behind a confirmation step. What comes back stays inside the Juma workspace, a teammate reviews each output before it ships, and Juma keeps zero data retention with AI model providers.
What can Juma do with Basecamp?
Through Juma, the team works with Basecamp for catching up on projects, managing to-dos, posting updates to message boards, centralizing files, and turning project work into finished deliverables, all from chat. Because Basecamp's agent surface supports both reads and writes, Juma can hand back a real artifact and post it to the right project.
01 · Catch up
Catch up on a project in one question
Ask in chat how the Marketing Dashboard project is coming along, or to summarize the last twenty messages in a project's board, and get a clear read without scrolling. Basecamp keeps each project's work in a calm, fixed structure (message board, to-dos, schedule, files), which makes it well suited to a plain-language summary. The answer comes back as a short brief on status, open to-dos, and recent decisions, ready to share with the team or a client.
02 · Manage to-dos from
Manage to-dos from a conversation
Tell Juma to add a to-do list for a launch, assign owners and due dates, or mark items complete as work lands. Basecamp's to-dos are the backbone of how teams track delivery; managing them in chat means the plan discussed in a conversation becomes real Basecamp work everyone can see. The team can also copy a set of tasks into another project's checklist, so recurring setups do not get rebuilt by hand each time.
03 · Post updates
Post updates and replies to the message board
Ask Juma to draft a client-ready project update and post it to the right message board, or to reply on a thread in the project's voice. Message boards are where Basecamp keeps the project conversation calm and on the record. Drafting the update in chat means it arrives structured and on-brand, with a teammate reviewing before it posts, so the board stays a trustworthy log rather than a stream of half-formed notes.
04 · Centralize reference files
Centralize reference files and briefs
Ask the team to upload a brief, a one-pager, or a set of reference files to a project, drafted in the project's brand voice from Project knowledge. Basecamp is often where a project's documents and decisions live; placing finished briefs there in chat keeps the project self-contained. The brief arrives ready for a teammate to review, and the project stays the single place the client and the team both look.
05 · Turn project work
Turn project work into deliverables and reports
Ask for the campaign brief stored in a project to become actual assets, or for a client performance report to be written and posted to the board. Basecamp tracks the work and the client conversation but ships no analytics or content tools by design. Juma reads the project, acts across the rest of the stack, and posts the finished result back, so a brief becomes a published page or a paid campaign, and a month of results becomes a report the client sees in Basecamp.
How does Juma + Basecamp replace your client-reporting busywork?
Most teams run Basecamp plus a separate analytics tool plus a writing tool plus a reporting deck plus the hours spent copying results between them, because Basecamp keeps itself deliberately simple. With Juma + Basecamp, our teams keep Basecamp as the calm home for project work and drop the manual middle: the hand-built client report, the retyped status update, and the copy-paste from analytics into a slide.
Juma does not replace Basecamp, and it does not try to add features Basecamp left out on purpose. The projects, to-dos, and message boards are the calm structure the work runs on. What disappears is the busywork around Basecamp, the hand-built client reports, the retyped status updates, the separate writing tool, and the hours spent moving results from analytics into a deck. House of Growth produces 160 articles per month and saves 85+ hours of manual work using Juma; the same compression applies to client work that used to need several tools and a coordinator to keep a project moving. Juma augments the team, it does not replace it, and a person reviews every output before it goes out.
What does Basecamp work best with in Juma?
Because Basecamp keeps itself deliberately minimal, the strongest pairings fill the gaps it leaves on purpose: pair Basecamp with Google Analytics for the reporting it does not include, with Webflow to publish the work it tracks, and with your Google Ads and Meta Ads accounts to run the campaigns its briefs describe.
The reporting layer Basecamp leaves out
Basecamp coordinates the work and the client conversation but ships no analytics by design. The team pulls the Google Analytics read in chat, writes a client-ready performance report, and posts it straight to the project's message board where the client already looks. This pairing is the most useful one for a Basecamp team, because the results layer has to come from somewhere, and Basecamp will never be that layer on its own.
From a to-do to a published page
The deliverable is tracked as a Basecamp to-do; the team drafts it together in brand voice; Webflow publishes it; the to-do gets marked done and the live link gets posted to the project. Basecamp tracks that a page is owed but cannot produce or ship it, so this pairing closes the loop from assignment to published in one chat, with a teammate reviewing before anything goes live.
From a stored brief to a live campaign
Because campaign briefs often live in a Basecamp project, the team can read a brief straight from the board and act on it across Google Ads, Meta Ads, and social channels like Instagram, then post performance back to the project. Basecamp holds the intent and the client relationship; the ad platforms are where the campaign runs. This pairing turns a brief that would otherwise sit in a to-do into real assets, a live campaign, and a results update the client can see.
How to connect Basecamp to Juma
To connect Basecamp to Juma:
Open Integrations
Click your name in the bottom-left corner of Juma, then Integrations.
Find Basecamp
Under Productivity integrations.
Connect
Click Connect, sign in to Basecamp, and authorize Juma over OAuth. The connection runs at the user level, so the projects and to-dos Juma can reach match your Basecamp access.
Done
Basecamp is now available across every Juma project and chat. Juma will prompt the team to use Basecamp when relevant, or ask directly: "Use Basecamp to summarize the latest messages in the Website Launch project and draft a client update."
Trusted by marketing teams that ship
Customer outcomes
240+ teams
Security & compliance
Questions, answered
Can I use Basecamp with ChatGPT or Claude instead of Juma?
Yes. 37signals made Basecamp agent-accessible, so it works with assistants like ChatGPT and Claude as well as Juma. What Juma adds is a marketing workspace: persistent project context (one project per client, with brand voice and prior decisions remembered), multi-tool composition (work with Basecamp alongside Google Analytics, Webflow, and your ad accounts in one chat), finished deliverables instead of chat responses, and team controls like audit logs, SSO/SAML, and SOC 2 Type II. For one person posting the odd update, a raw assistant is fine. For a team running client work, project context and tool composition are what change the day.
Can Juma post to Basecamp and update to-dos, or only read?
Both. Basecamp's agent surface supports write actions, so through Juma the team can post messages and replies to message boards, create and update to-dos, mark them complete, and upload files, as well as read and summarize any project. Destructive actions like trashing a project or changing who has access are gated behind a confirmation step. A teammate reviews each output before it posts, so the project board stays a trustworthy record rather than filling with unreviewed AI activity.
How much does it cost to use Basecamp through Juma?
Juma prices by what gets done, not by which model ran. Tasks consume credits: low-effort tasks are 1 to 100 credits, high-effort tasks like a client report or campaign assets are 100 to 500 credits, and failed tasks cost zero. Free, Pro, and Enterprise plans all include unlimited seats and access to Basecamp through the connector; they differ only in monthly credit volume. The Basecamp subscription is separate, and Juma does not resell Basecamp.
Does the Basecamp + Juma integration support agencies managing multiple clients?
Yes. Juma is built for agencies, and Basecamp is a popular home for agency client work. Projects in Juma organize knowledge per client (brand voice, prior decisions, asset library), and each person's Basecamp connection works across every project they touch, matching their Basecamp access. 400+ marketing teams use Juma, including agencies like Wavemaker, Mindshare, and Mission North. SOC 2 Type II and ISO 27001 compliance covers client data handling, and Enterprise plans add SSO/SAML and private cloud deployment. Unlimited seats mean the whole agency works in the same Basecamp projects with no per-user fees.
Does Basecamp have AI built in, and how is that different from Juma?
Basecamp deliberately ships no native AI. 37signals chose to make Basecamp agent-accessible instead (a revamped API and an agent skill) so teams bring their own assistant rather than having AI bolted onto the product. Using Basecamp through Juma fits that design: Basecamp stays calm and uncluttered, and Juma is the agent that reads projects, posts updates, and turns project work into deliverables across the rest of the marketing stack. The tool keeps its simplicity; the AI lives in the workspace around it.
Can I cancel Basecamp and just use Juma?
No. Juma works with Basecamp's projects, to-dos, and message boards to coordinate work, so it is the AI layer on top of Basecamp, not a replacement for it. What the team can drop is the busywork around Basecamp: the hand-built client reports, the retyped status updates, the separate writing tool, and the copy-paste from analytics into a deck. Basecamp stays the calm home for project work; the manual middle is what goes away.
Does Juma store my Basecamp data?
Juma reads Basecamp on demand: only the data a specific question needs is pulled, not a bulk export. Results stay inside the Juma workspace under the team's control, encrypted with AES-256 in-transit and at-rest. Juma's zero data retention policy with AI model providers means Basecamp data is never used to train any third-party model. SOC 2 Type II and ISO 27001 audits are available on request. Basecamp can be disconnected at any time without affecting the rest of the Juma workspace.
Ask AI about us
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
What's on your plate today?
Start typing a task and Juma will figure out the rest.