SendToTeam + Trello Integration

SendToTeam connects to Trello via the Trello REST API using a Power-Up token that you authorize through Trello's standard OAuth flow. The token grants access to boards you specify — your AI employees cannot browse boards outside the ones you share. The integration reads cards, lists, labels, custom fields, checklists, and due dates; it writes by creating cards, updating card details, moving cards between lists, and adding comments.

The primary pattern is bi-directional sync between AI employee tasks and Trello cards. When the assistant begins a task (drafting a blog post, composing outreach, building a report), a Trello card is created in your "In Progress" list with the task description, assigned member, and due date. When the draft is ready for review, the card moves to "In Review" with a comment containing a link to the draft. When you approve, the card moves to "Done." Your Trello board becomes a visual dashboard of the assistant output without anyone updating cards manually.

The integration also reads Trello boards for task context. A content team might maintain a "Blog Topics" board where each card represents a post to write, with custom fields for target keyword, word count, and audience. The assistant reads cards in the "Ready to Draft" list, picks the card with the earliest due date, and uses the card's details as the content brief. When drafting is complete, it updates the card with a link to the draft and moves it to "Review." The board drives the workflow end to end.

Project health reports aggregate data across your boards. The assistant queries all cards on a board, calculates metrics — cards created this week, cards completed, cards overdue, average time in each list — and formats the results as a summary. For a team managing multiple project boards, a weekly report shows velocity trends: which projects are on track, which are accumulating overdue cards, and where bottlenecks sit in the workflow.

The integration works with Trello's label system, checklists, and attachments. Labels applied to cards are preserved and readable, so your automation assistant can differentiate tasks by type (e.g., "Blog" vs. "Email" vs. "Report" labels) and prioritize accordingly. Checklist items can be read for subtask context and updated as individual steps are completed.