Sign inStart your trial

BasecampBasecamp
01Integration field card

Basecamp Integration & Workflow Automation

Run Basecamp on autopilot. Keep the veto.

140 actions

Cards move, to-dos update, and schedule entries shift in Basecamp before you realize what fired. Rills proposes each change; you approve before it goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential project management action from Basecamp arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

BASECAMP · CARD REVIEW
78

Move 6 stalled cards to On-Hold column in Basecamp?

6 cards unchanged for 9+ days across 3 active projects

Same pattern approved last sprint cycle

No schedule entry updates logged against any of these cards

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Basecamp automation

Project management decisions pile up quietly in Basecamp: a card moves to the wrong column, a schedule entry updates before the client agreed, a to-do gets reassigned without the person knowing. The ones that go out unreviewed are the ones you hear about later.

When Basecamp runs unsupervised

Basecamp has no shortage of actions that look routine until they aren't. A single wrong move on a card table or a stale schedule entry ships to everyone on the project before you've read the context.

  • Moving a card to a column posts a status change the client sees before you've confirmed the work is done.
  • Updating a schedule entry shifts a deadline that a teammate has already planned around, with no warning.
  • Creating a card table column adds structure to a live project board that may not match the agreed workflow.
  • Deleting a Campfire line removes a message that someone else may be referencing in a thread.
  • Updating a to-do reassigns ownership in a way that can strand work between two people with neither acting.

What Rills does inside Basecamp

Rills watches for the conditions you define, then surfaces a proposal before it touches your project. Whether that's a card move triggered by a status in another tool, an Update Schedule Entry call queued after a client email, or a batch of Update To-Do reassignments flagged for review, each action waits for your call.

The card moves, the deadline shifts, the to-do changes hands; none of it happens until you say so.

Why Basecamp has no triggers and how Rills fills the gap

Basecamp does not emit events that start workflows on their own, which means Basecamp automation depends on something upstream doing the watching. Rills fills that gap by polling on a schedule or reacting to triggers from connected tools, then proposing Basecamp actions when the conditions match.

  • A scheduled poll checks for overdue to-dos using Update To-Do conditions and queues a reassignment proposal when nothing has moved in a set window.
  • An upstream CRM or form tool fires a signal that Rills translates into a Move Card to Column proposal, held for approval before the board changes.
  • A recurring check on Update Schedule Entry conditions surfaces deadline conflicts before they go out to the project team.
  • A time-based sweep detects stale card table columns and proposes a Delete Card Table Column On-Hold Section action, waiting for you to approve Basecamp changes before anything is removed.
04. Actions

What Rills can do in Basecamp

2 of 140 actions across reads, writes, and updates.

  1. 01

    Create Card in Column

    Add a new card to a specific column in your Basecamp project's card table, optionally including task details and due dates. Use this to organize and track work items as they move through different stages of your project workflow.

  2. 02

    Complete To-Do

    Mark a to-do item as completed in Basecamp to track task progress and keep your project organized. This helps you maintain visibility into what's been finished across your team's work.

05. FAQ

Common questions about Basecamp automation

06. NEXT MOVE

Approve every Basecamp change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.