{"id":"44f037d9-6210-4767-bc38-8ee934c86fe7","shortId":"jAhBuC","kind":"skill","title":"basecamp-automation","tagline":"Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.","description":"# Basecamp Automation via Rube MCP\n\nAutomate Basecamp operations including project management, to-do list creation, task management, message board posting, people management, and to-do group organization through Composio's Basecamp toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Basecamp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n3. If connection is not ACTIVE, follow the returned auth link to complete Basecamp OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage To-Do Lists and Tasks\n\n**When to use**: User wants to create to-do lists, add tasks, or organize work within a Basecamp project\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List projects to find the target bucket_id [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOSETS` - Get the to-do set within a project [Prerequisite]\n3. `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS` - List existing to-do lists to avoid duplicates [Optional]\n4. `BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS` - Create a new to-do list in a to-do set [Required for list creation]\n5. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get details of a specific to-do list [Optional]\n6. `BASECAMP_POST_BUCKETS_TODOLISTS_TODOS` - Create a to-do item in a to-do list [Required for task creation]\n7. `BASECAMP_CREATE_TODO` - Alternative tool for creating individual to-dos [Alternative]\n8. `BASECAMP_GET_BUCKETS_TODOLISTS_TODOS` - List to-dos within a to-do list [Optional]\n\n**Key parameters for creating to-do lists**:\n- `bucket_id`: Integer project/bucket ID (from GET_PROJECTS)\n- `todoset_id`: Integer to-do set ID (from GET_BUCKETS_TODOSETS)\n- `name`: Title of the to-do list (required)\n- `description`: HTML-formatted description (supports Rich text)\n\n**Key parameters for creating to-dos**:\n- `bucket_id`: Integer project/bucket ID\n- `todolist_id`: Integer to-do list ID\n- `content`: What the to-do is for (required)\n- `description`: HTML details about the to-do\n- `assignee_ids`: Array of integer person IDs\n- `due_on`: Due date in `YYYY-MM-DD` format\n- `starts_on`: Start date in `YYYY-MM-DD` format\n- `notify`: Boolean to notify assignees (defaults to false)\n- `completion_subscriber_ids`: Person IDs notified upon completion\n\n**Pitfalls**:\n- A project (bucket) can contain multiple to-do sets; selecting the wrong `todoset_id` creates lists in the wrong section\n- Always check existing to-do lists before creating to avoid near-duplicate names\n- Success payloads include user-facing URLs (`app_url`, `app_todos_url`); prefer returning these over raw IDs\n- All IDs (`bucket_id`, `todoset_id`, `todolist_id`) are integers, not strings\n- Descriptions support HTML formatting only, not Markdown\n\n### 2. Post and Manage Messages\n\n**When to use**: User wants to post messages to a project message board or update existing messages\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project and bucket_id [Prerequisite]\n2. `BASECAMP_GET_MESSAGE_BOARD` - Get the message board ID for the project [Prerequisite]\n3. `BASECAMP_CREATE_MESSAGE` - Create a new message on the board [Required]\n4. `BASECAMP_POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` - Alternative message creation tool [Fallback]\n5. `BASECAMP_GET_MESSAGE` - Read a specific message by ID [Optional]\n6. `BASECAMP_PUT_BUCKETS_MESSAGES` - Update an existing message [Optional]\n\n**Key parameters**:\n- `bucket_id`: Integer project/bucket ID\n- `message_board_id`: Integer message board ID (from GET_MESSAGE_BOARD)\n- `subject`: Message title (required)\n- `content`: HTML body of the message\n- `status`: Set to `\"active\"` to publish immediately\n- `category_id`: Message type classification (optional)\n- `subscriptions`: Array of person IDs to notify; omit to notify all project members\n\n**Pitfalls**:\n- `status=\"draft\"` can produce HTTP 400; use `status=\"active\"` as the reliable option\n- `bucket_id` and `message_board_id` must belong to the same project; mismatches fail or misroute\n- Message content supports HTML tags only; not Markdown\n- Updates via `PUT_BUCKETS_MESSAGES` replace the entire body -- include the full corrected content, not just a diff\n- Prefer `app_url` from the response for user-facing confirmation links\n- Both `CREATE_MESSAGE` and `POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` do the same thing; use CREATE_MESSAGE first and fall back to POST if it fails\n\n### 3. Manage People and Access\n\n**When to use**: User wants to list people, manage project access, or add new users\n\n**Tool sequence**:\n1. `BASECAMP_GET_PEOPLE` - List all people visible to the current user [Required]\n2. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n3. `BASECAMP_LIST_PROJECT_PEOPLE` - List people on a specific project [Required]\n4. `BASECAMP_GET_PROJECTS_PEOPLE` - Alternative to list project members [Alternative]\n5. `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` - Grant or revoke project access [Required for access changes]\n\n**Key parameters for PUT_PROJECTS_PEOPLE_USERS**:\n- `project_id`: Integer project ID\n- `grant`: Array of integer person IDs to add to the project\n- `revoke`: Array of integer person IDs to remove from the project\n- `create`: Array of objects with `name`, `email_address`, and optional `company_name`, `title` for new users\n- At least one of `grant`, `revoke`, or `create` must be provided\n\n**Pitfalls**:\n- Person IDs are integers; always resolve names to IDs via GET_PEOPLE first\n- `project_id` for people management is the same as `bucket_id` for other operations\n- `LIST_PROJECT_PEOPLE` and `GET_PROJECTS_PEOPLE` are near-identical; use either\n- Creating users via `create` also grants them project access in one step\n\n### 4. Organize To-Dos with Groups\n\n**When to use**: User wants to organize to-dos within a list into color-coded groups\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get the to-do list details [Prerequisite]\n3. `BASECAMP_GET_TODOLIST_GROUPS` - List existing groups in a to-do list [Optional]\n4. `BASECAMP_GET_BUCKETS_TODOLISTS_GROUPS` - Alternative group listing [Alternative]\n5. `BASECAMP_POST_BUCKETS_TODOLISTS_GROUPS` - Create a new group in a to-do list [Required]\n6. `BASECAMP_CREATE_TODOLIST_GROUP` - Alternative group creation tool [Alternative]\n\n**Key parameters**:\n- `bucket_id`: Integer project/bucket ID\n- `todolist_id`: Integer to-do list ID\n- `name`: Group title (required)\n- `color`: Visual color identifier -- one of: `white`, `red`, `orange`, `yellow`, `green`, `blue`, `aqua`, `purple`, `gray`, `pink`, `brown`\n- `status`: Filter for listing -- `\"archived\"` or `\"trashed\"` (omit for active groups)\n\n**Pitfalls**:\n- `POST_BUCKETS_TODOLISTS_GROUPS` and `CREATE_TODOLIST_GROUP` are near-identical; use either\n- Color values must be from the fixed palette; arbitrary hex/rgb values are not supported\n- Groups are sub-sections within a to-do list, not standalone entities\n\n### 5. Browse and Inspect Projects\n\n**When to use**: User wants to list projects, get project details, or explore project structure\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List all active projects [Required]\n2. `BASECAMP_GET_PROJECT` - Get comprehensive details for a specific project [Optional]\n3. `BASECAMP_GET_PROJECTS_BY_PROJECT_ID` - Alternative project detail retrieval [Alternative]\n\n**Key parameters**:\n- `status`: Filter by `\"archived\"` or `\"trashed\"`; omit for active projects\n- `project_id`: Integer project ID for detailed retrieval\n\n**Pitfalls**:\n- Projects are sorted by most recently created first\n- The response includes a `dock` array with tools (todoset, message_board, etc.) and their IDs\n- Use the dock tool IDs to find `todoset_id`, `message_board_id`, etc. for downstream operations\n\n## Common Patterns\n\n### ID Resolution\nBasecamp uses a hierarchical ID structure. Always resolve top-down:\n- **Project (bucket_id)**: `BASECAMP_GET_PROJECTS` -- find by name, capture the `id`\n- **To-do set (todoset_id)**: Found in project dock or via `BASECAMP_GET_BUCKETS_TODOSETS`\n- **Message board (message_board_id)**: Found in project dock or via `BASECAMP_GET_MESSAGE_BOARD`\n- **To-do list (todolist_id)**: `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS`\n- **People (person_id)**: `BASECAMP_GET_PEOPLE` or `BASECAMP_LIST_PROJECT_PEOPLE`\n- Note: `bucket_id` and `project_id` refer to the same entity in different contexts\n\n### Pagination\nBasecamp uses page-based pagination on list endpoints:\n- Response headers or body may indicate more pages available\n- `GET_PROJECTS`, `GET_BUCKETS_TODOSETS_TODOLISTS`, and list endpoints return paginated results\n- Continue fetching until no more results are returned\n\n### Content Formatting\n- All rich text fields use HTML, not Markdown\n- Wrap content in `
` tags; use ``, ``, `