Overview
Trello integration enables Praxos to manage boards, lists, and cards in your Trello workspace.Features
- Create and update boards
- Manage lists
- Create, move, and update cards
- Add comments and attachments
- Manage labels and due dates
- Add members to cards
- Checklist management
Setup
1. Get API Credentials
- Go to Trello Power-Ups Admin Portal
- Click “New” to create a new Power-Up
- Note your API Key
2. Generate Token
- Visit:
https://trello.com/1/authorize?expiration=never&name=Praxos&scope=read,write&response_type=token&key=YOUR_API_KEY - Click “Allow”
- Copy the token
3. Configure Praxos
Add to.env:
Usage Examples
Board Management
List BoardsCard Operations
Create CardComments and Activity
Add CommentChecklists
Create ChecklistLabels
Add LabelConfiguration
Environment Variables
Board Templates
Configure default board structure:Advanced Features
Webhooks
Real-time notifications for:- Card created/updated/moved
- Comments added
- Checklist items completed
- Members added/removed
Bulk Operations
Card Templates
Create cards from templates:Trello Power-Ups
Enhance with Power-Ups:- Calendar view
- Custom fields
- Card aging
- Voting
- Time tracking
Troubleshooting
Authentication Issues
Invalid Token- Token may have expired (if not set to “never”)
- Regenerate token
- Update
.envfile
- Verify token has read/write scope
- Check API key is valid
- Ensure user has board access
Rate Limits
Trello rate limits:- 100 requests per 10 seconds per token
- 300 requests per 10 seconds per API key
Praxos implements request queuing and automatic retry with backoff.
Board Not Found
- Verify board ID is correct
- Check user has access to board
- Board may have been deleted or archived
Best Practices
- Use clear, descriptive card titles
- Leverage labels for categorization
- Set due dates for time-sensitive tasks
- Use checklists to break down complex tasks
- Archive completed cards regularly
- Maintain consistent board structure
Security
- API keys and tokens encrypted
- Per-user credential isolation
- Secure webhook validation
- Regular token rotation recommended