basecamp-cliManage Basecamp (via bc3 API / 37signals Launchpad) projects, to-dos, messages, and campfires via a TypeScript CLI. Use when you want to list/create/update Basecamp projects and todos from the terminal, or when integrating Basecamp automation into Clawdbot workflows.
Install via ClawdBot CLI:
clawdbot install emredoganer/basecamp-cliThis repo contains a standalone CLI.
npm i -g @emredoganer/basecamp-cliCreate an integration (OAuth app) in 37signals Launchpad:
Then:
basecamp auth configure --client-id <id> --redirect-uri http://localhost:9292/callback
export BASECAMP_CLIENT_SECRET="<secret>"
basecamp auth loginBASECAMP_CLIENT_SECRET is intentionally NOT stored on disk by the CLI.Generated Mar 1, 2026
A software development team uses the CLI to automate daily stand-up updates by creating Basecamp to-dos from terminal scripts. This reduces manual entry and ensures tasks are logged consistently across sprints.
A marketing agency integrates the CLI into their workflow to list and update Basecamp projects for client campaigns. This allows quick status checks and task assignments from the command line, improving team coordination.
A distributed team uses the CLI to manage Basecamp messages and campfires directly from terminals. This streamlines communication for remote workers who prefer command-line tools over web interfaces.
A freelance designer employs the CLI to create and update Basecamp to-dos for client projects. This helps track deadlines and deliverables efficiently without switching contexts from development environments.
A company offers this CLI as part of a larger automation platform, charging subscription fees for enhanced Basecamp integrations. This model targets businesses seeking streamlined project management tools.
A consultancy uses the CLI to provide custom Basecamp automation solutions for clients, generating revenue through service fees. This model leverages the CLI's flexibility for tailored workflows.
The CLI is maintained as open-source software, with revenue generated from donations, sponsorships, or premium support packages. This model fosters community adoption and contributions.
💬 Integration Tip
Ensure secure handling of the BASECAMP_CLIENT_SECRET via environment variables and automate OAuth token refreshes in CI/CD pipelines for reliable integration.
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications.
Advanced desktop automation with mouse, keyboard, and screen control
Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation".
Browser automation via Playwright MCP server. Navigate websites, click elements, fill forms, extract data, take screenshots, and perform full browser automation workflows.