Trello

Trello is the kanban-board work surface most teams ran on before everyone migrated to Jira, Linear, or Notion — and which a lot of teams still use because the simple model fits the work better than anything heavier. When the integration lands, myai will treat Trello as a live data source — boards, lists, cards, checklists, all queryable from chats and writable from automations through the Trello REST API.

What you'll be able to do

• Pull board state into a chat — "show me all cards in 'Doing' across the marketing boards" returns a structured table inline.
• Card writes from automations — create cards, move between lists, update checklists, add labels when conditions fire elsewhere in your stack.
• Checklist progress tracking — for the boards where the checklist within each card is what actually drives the work.
• Label-scoped queries — every "blocked" card, every "customer-reported" card, queryable as a structured set.
• Webhook triggers — board or card changes can kick off downstream automation without polling.
• Workspace-aware credential — one connection reaches every board your token has access to.

How it'll work

Trello API key + token. Generate at trello.com/app-key, then authorize a user token. The integration handles the auth header composition automatically.

Tell us you want Trello

Use cases we're hearing

• Cross-board reporting — function reads multiple Trello boards (sprint, content, customer-success), joins them into a single weekly digest.
• Workflow-automation bridging — Trello card changes drive downstream actions in Slack, email, or CRM without Trello-native automation rules.
• Cross-tool task aggregation — Trello cards alongside Linear, Jira, Asana items in a single daily view for hybrid-tool organizations.

Reference

• Connection model: Trello API key + user token (Bearer-less header composition)
• Scope: ~40 operations across boards, lists, cards, checklists, labels, members, webhooks
• Per-board permissions enforced — token scope determines what the integration can see