trello-automation
npx machina-cli add skill davepoon/buildwithclaude/trello-automation --openclawTrello Automation via Rube MCP
Automate Trello board management, card creation, and team workflows through Composio's Rube MCP integration.
Toolkit docs: composio.dev/toolkits/trello
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Trello connection via
RUBE_MANAGE_CONNECTIONSwith toolkittrello - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkittrello - If connection is not ACTIVE, follow the returned auth link to complete Trello auth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create a Card on a Board
When to use: User wants to add a new card/task to a Trello board
Tool sequence:
TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER- List boards to find target board ID [Prerequisite]TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD- Get lists on board to find target list ID [Prerequisite]TRELLO_ADD_CARDS- Create the card on the resolved list [Required]TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD- Add a checklist to the card [Optional]TRELLO_ADD_CARDS_CHECKLIST_CHECK_ITEM_BY_ID_CARD_BY_ID_CHECKLIST- Add items to the checklist [Optional]
Key parameters:
idList: 24-char hex ID (NOT list name)name: Card titledesc: Card description (supports Markdown)pos: Position ('top'/'bottom')due: Due date (ISO 8601 format)
Pitfalls:
- Store returned id (idCard) immediately; downstream checklist operations fail without it
- Checklist payload may be nested (data.data); extract idChecklist from inner object
- One API call per checklist item; large checklists can trigger rate limits
2. Manage Boards and Lists
When to use: User wants to view, browse, or restructure board layout
Tool sequence:
TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER- List all boards for the user [Required]TRELLO_GET_BOARDS_BY_ID_BOARD- Get detailed board info [Required]TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD- Get lists (columns) on the board [Optional]TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD- Get board members [Optional]TRELLO_GET_BOARDS_LABELS_BY_ID_BOARD- Get labels on the board [Optional]
Key parameters:
idMember: Use 'me' for authenticated userfilter: 'open', 'starred', or 'all'idBoard: 24-char hex or 8-char shortLink (NOT board name)
Pitfalls:
- Some runs return boards under response.data.details[]—don't assume flat top-level array
- Lists may be nested under results[0].response.data.details—parse defensively
- ISO 8601 timestamps with trailing 'Z' must be parsed as timezone-aware
3. Move Cards Between Lists
When to use: User wants to change a card's status by moving it to another list
Tool sequence:
TRELLO_GET_SEARCH- Find the card by name or keyword [Prerequisite]TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD- Get destination list ID [Prerequisite]TRELLO_UPDATE_CARDS_BY_ID_CARD- Update card's idList to move it [Required]
Key parameters:
idCard: Card ID from searchidList: Destination list IDpos: Optional ordering within new list
Pitfalls:
- Search returns partial matches; verify card name before updating
- Moving doesn't update position within new list; set pos if ordering matters
4. Assign Members to Cards
When to use: User wants to assign team members to cards
Tool sequence:
TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD- Get member IDs from the board [Prerequisite]TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD- Add a member to the card [Required]
Key parameters:
idCard: Target card IDvalue: Member ID to assign
Pitfalls:
- UPDATE_CARDS_ID_MEMBERS replaces entire member list; use ADD_CARDS_ID_MEMBERS to append
- Member must have board permissions
5. Search and Filter Cards
When to use: User wants to find specific cards across boards
Tool sequence:
TRELLO_GET_SEARCH- Search by query string [Required]
Key parameters:
query: Search string (supports board:, list:, label:, is:open/archived operators)modelTypes: Set to 'cards'partial: Set to 'true' for prefix matching
Pitfalls:
- Search indexing has delay; newly created cards may not appear for several minutes
- For exact name matching, use TRELLO_GET_BOARDS_CARDS_BY_ID_BOARD and filter locally
- Query uses word tokenization; common words may be ignored as stop words
6. Add Comments and Attachments
When to use: User wants to add context to an existing card
Tool sequence:
TRELLO_ADD_CARDS_ACTIONS_COMMENTS_BY_ID_CARD- Post a comment on the card [Required]TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD- Attach a file or URL [Optional]
Key parameters:
text: Comment text (1-16384 chars, supports Markdown and @mentions)urlORfile: Attachment source (not both)name: Attachment display namemimeType: File MIME type
Pitfalls:
- Comments don't support file attachments; use the attachment tool separately
- Attachment deletion is irreversible
Common Patterns
ID Resolution
Always resolve display names to IDs before operations:
- Board name → Board ID:
TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBERwith idMember='me' - List name → List ID:
TRELLO_GET_BOARDS_LISTS_BY_ID_BOARDwith resolved board ID - Card name → Card ID:
TRELLO_GET_SEARCHwith query string - Member name → Member ID:
TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD
Pagination
Most list endpoints return all items. For boards with 1000+ cards, use limit and before parameters on card listing endpoints.
Rate Limits
300 requests per 10 seconds per token. Use TRELLO_GET_BATCH for bulk read operations to stay within limits.
Known Pitfalls
- ID Requirements: Nearly every tool requires IDs, not display names. Always resolve names to IDs first.
- Board ID Format: Board IDs must be 24-char hex or 8-char shortLink. URL slugs like 'my-board' are NOT valid.
- Search Delays: Search indexing has delays; newly created/updated cards may not appear immediately.
- Nested Responses: Response data is often nested (data.data or data.details[]); parse defensively.
- Rate Limiting: 300 req/10s per token. Batch reads with TRELLO_GET_BATCH.
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List user's boards | TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER | idMember='me', filter='open' |
| Get board details | TRELLO_GET_BOARDS_BY_ID_BOARD | idBoard (24-char hex) |
| List board lists | TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD | idBoard |
| Create card | TRELLO_ADD_CARDS | idList, name, desc, pos, due |
| Update card | TRELLO_UPDATE_CARDS_BY_ID_CARD | idCard, idList (to move) |
| Search cards | TRELLO_GET_SEARCH | query, modelTypes='cards' |
| Add checklist | TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD | idCard, name |
| Add comment | TRELLO_ADD_CARDS_ACTIONS_COMMENTS_BY_ID_CARD | idCard, text |
| Assign member | TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD | idCard, value (member ID) |
| Attach file/URL | TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD | idCard, url OR file |
| Get board members | TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD | idBoard |
| Batch read | TRELLO_GET_BATCH | urls (comma-separated paths) |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/trello-automation/SKILL.mdView on GitHub Overview
Automate Trello board management, card creation, and team workflows through Composio's Rube MCP integration. Create cards, manage lists, assign members, and search across boards programmatically to streamline project work. This skill reduces manual clicks and accelerates Trello-driven processes.
How This Skill Works
The setup uses Rube MCP as the bridge to Trello. First, verify the MCP is available, then connect the Trello toolkit and ensure the connection is ACTIVE. Core workflows use predefined tool sequences (e.g., locate boards and lists, create cards, then optionally add checklists) and require IDs like idList and idCard rather than names. Store IDs returned by calls so downstream steps (like adding checklist items) succeed.
When to Use It
- Add a new task card to a specific Trello board and list with a title and description.
- Audit or restructure a board by listing boards, retrieving list details, and inspecting members and labels.
- Move a card from one list to another to reflect a status change (e.g., Backlog to In Progress).
- Assign one or more teammates to a card to establish ownership and responsibility.
- Search across boards for a card by keyword, then update its details or attach a checklist.
Quick Start
- Step 1: Add Rube MCP as an MCP server (https://rube.app/mcp) and connect the Trello toolkit; authorize Trello if prompted.
- Step 2: Run RUBE_SEARCH_TOOLS to verify tool schemas and confirm the Trello connection is ACTIVE.
- Step 3: Create a card by following the sequence: TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER -> TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD -> TRELLO_ADD_CARDS (idList, name, desc); add a checklist with TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD if needed.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any operation.
- Store returned IDs (e.g., idCard, idChecklist) immediately; downstream steps rely on them.
- Handle nested API responses defensively; extract IDs from inner objects when needed.
- Use 24-char hex IDs for idList/idBoard rather than board names to avoid ambiguity.
- Respect rate limits by batching checklist items (one API call per item) and spacing requests.
Example Use Cases
- Create a new onboarding task card on the project board's To Do list with a detailed description.
- Add a 3-item checklist to a newly created card and populate each item programmatically.
- Move a feature card from Backlog to In Progress when development starts and update the due date.
- Assign assignees to a card to reflect team ownership and track responsibility.
- Search for a card across boards by keyword and update its due date and labels.
Frequently Asked Questions
Related Skills
github-initiative-pulse
athola/claude-night-market
'Outputs markdown digests and CSV exports for GitHub issues and PRs.
basecamp-automation
davepoon/buildwithclaude
Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.
clickup-automation
davepoon/buildwithclaude
Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.
coda-automation
davepoon/buildwithclaude
Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
jira-automation
davepoon/buildwithclaude
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
linear-automation
davepoon/buildwithclaude
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.