Every Monday morning, each employee gets a personal e-mail built from the team's Trello boards: their deadlines, unanswered mentions and team news — enriched with an AI digest of the industry week.
Built for a multi-location retail company in Poland
The team runs its daily work on Trello — but the Monday overview didn't run itself. What's overdue, which mentions were never answered, what did the rest of the team post last week: assembling that picture by hand was everyone's job, so it was nobody's.
Now a Monday-morning run builds a personal briefing for every employee: their tasks due in the next 14 days with overdue items first, new team-wide tasks, and every mention they haven't responded to — where a reply or even an emoji reaction counts as an answer. Managers additionally see boards of other teams and receive business recommendations.
The industry section is prepared separately on Friday: an LLM digests the week's articles from an industry news portal into a readable summary, and — analyzing the same articles as a business advisor — proposes up to five sourced recommendations. If nothing that week is business-relevant, it deliberately returns none instead of inventing filler.
Two runs, connected by files: Friday prepares the AI-written news summary and recommendations; Monday reads the team's Trello boards, builds a personal report for each employee and attaches Friday's output — recommendations for managers only.
Friday · news prep
Industry news portal
public articles, last 7 days
Article scraping
headless browser, full text
LLM · two passes
week summary + business advice
News summary
summary.html · for everyone
Recommendations
recommendations.html · managers
Monday · personal reports
Trello API
cards, comments, emoji reactions
Shared index
mentions + team tasks, one pass
Report builder
one personal briefing per person
delivered to each employee
PostgreSQL
report history in the panel · Friday's files feed Monday's reports
Runs Friday afternoon
Runs Monday morning
A report that fails on Monday morning is worse than no report — so every step assumes something else might be down.
Every Trello API call retries automatically with growing delays — a rate limit or hiccup never kills the whole run.
Each card's comments are fetched once and mapped to all mentioned employees at once, drastically cutting API calls.
Extra boards are listed per manager, not implied by a role flag — visibility into other teams stays deliberate.
The runs share only files. If Friday's scraping fails, Monday's reports still go out — just without the news section.
--test and --dry-run write reports to a timestamped folder without sending e-mails or touching the database.
A missing e-mail, unmatched account or inaccessible board logs a warning and is summarized at the end — it never stops the other reports.
Technology: Python · Trello API · headless browser · LLM APIs · e-mail · PostgreSQL/Django · cron
Today the system is a reporter: it informs once a week. The same foundation — Trello access, an LLM and a schedule — can grow into an agent that proposes and takes actions.
Instead of an HTML block in a manager's inbox, the agent creates a ready Trello card with a suggested deadline and the cited source — the manager just accepts or rejects.
When the same task or mention slips for the third week running, the agent notifies the manager with a short rationale and posts a reminder comment on the card.
Track several industry, regulatory and competitor feeds — including the market-intelligence agent's data — and synthesize one coherent weekly picture.
The same weekly index could power a chat interface: ask "what's overdue for X?" and get the answer immediately, not next Monday.
If your team's status lives in boards, chats and inboxes, an automation can assemble it while everyone sleeps. Let's talk about your weekly rhythm.
Discuss your workflow