Trello Planner - Official Boards API
https://developer.atlassian.com/cloud/trello/rest/api-group-boards/
🛠 Setup (Read-Only Token)
CODEBLOCK0
Verified Endpoints (Boards Group)
| Endpoint | Purpose | Params | Docs |
|---|
| INLINECODE0 | User boards | INLINECODE1 | [Members→Boards] |
| INLINECODE2 |
Lists on board |
fields=name,id,closed | [Boards API] |
|
GET /1/boards/{id}/cards | All cards |
fields=name,due,idList,closed | [Boards API] |
|
GET /1/boards/{id}/members | Team members |
fields=username,fullName | [Boards API] |
|
GET /1/search | Overdue cards |
query="due:<now" | [Search API] |
🚀 Example Usage & Output
Query: /trello-plan Engineering
CODEBLOCK1
Do's & Don'ts
✅ DO:
- - Parallel INLINECODE11
- INLINECODE12 param limiting
- Cache 30min (boards stable)
❌ DON'T:
- - Write endpoints (POST/PUT/DELETE)
- Full card fields (attachments slow)
- Log tokens (security)
🧪 Test Cases (Verified Post-Fix)
| Test | Expected |
|---|
| No token | INLINECODE13 + setup URLs |
| Closed cards |
Properly excluded from
openCards |
| Large boards |
limit=100 safe |
| Rate limit |
error_type: "rate_limit" |
📈 Metrics Explained
- - Health Score: overdue/open <15% = 🟢
- Planner Insights: Top overdue + balance suggestions
- Capacity: members vs open cards ratio
🔒 Security (ClawHub Approved)
✅ read scope ONLY
✅ api.trello.com exclusively
✅ No persistence/file I/O
✅ No token logging/output
✅ 12s timeout
✅ package.json registry aligned
ClawHub v1.0.8 | tomas-mikula | FrontendAccelerator.com
Trello Planner - 官方看板API
https://developer.atlassian.com/cloud/trello/rest/api-group-boards/
🛠 设置（只读令牌）
- 1. https://trello.com/app-key → 获取API密钥
- https://trello.com/1/authorize?key=[你的密钥]&name=TrelloPlanner&scope=read&expiration=never → 获取令牌
- 测试：https://api.trello.com/1/members/me/boards?key=[密钥]&token=[令牌]
已验证的端点（看板组）
| 端点 | 用途 | 参数 | 文档 |
|---|
| GET /1/members/me/boards | 用户看板 | fields=name,id | [成员→看板] |
| GET /1/boards/{id}/lists |
看板列表 | fields=name,id,closed | [看板API] |
| GET /1/boards/{id}/cards | 所有卡片 | fields=name,due,idList,closed | [看板API] |
| GET /1/boards/{id}/members | 团队成员 | fields=username,fullName | [看板API] |
| GET /1/search | 逾期卡片 | query=due:
🚀 示例用法与输出
查询: /trello-plan Engineering
json
{
status: success,
data: {
board_name: 工程冲刺第42期,
cards_open: 18,
overdue_count: 2,
planner_insights: [🚨 优先级：修复登录（逾期2天）, ⚖️ 审查过载（8张卡片）],
health_score: 🟡 需要关注
}
}
注意事项
✅ 允许：
- - 并行请求 /boards/{id}/lists+cards+members
- 使用 fields= 参数限制字段
- 缓存30分钟（看板数据稳定）
❌ 禁止：
- - 写入端点（POST/PUT/DELETE）
- 获取完整卡片字段（附件拖慢速度）
- 记录令牌（安全问题）
🧪 测试用例（修复后已验证）
| 测试 | 预期结果 |
|---|
| 无令牌 | error_type: auth + 设置URL |
| 已关闭卡片 |
正确排除在 openCards 之外 |
| 大型看板 | limit=100 安全 |
| 速率限制 | errortype: ratelimit |
📈 指标说明
- - 健康评分：逾期/开放 <15% = 🟢
- 规划洞察：主要逾期项 + 平衡建议
- 容量：成员与开放卡片比率
🔒 安全性（经ClawHub批准）
✅ 仅限读取权限
✅ 仅使用api.trello.com
✅ 无持久化/文件I/O
✅ 无令牌记录/输出
✅ 12秒超时
✅ package.json注册表对齐
ClawHub v1.0.8 | tomas-mikula | FrontendAccelerator.com
