How to do it
- Collect highlights An n8n or Make flow gathers the week's top threads, answered questions, and new members and sends them to the REST API.
- Draft the roundup The agent drafts a highlights thread for Bluesky and Mastodon and a single LinkedIn post, crediting members by handle where they agreed.
- Moderator reviews A moderator approves or edits in the inbox; nobody is thanked publicly without the team checking the context.
- Keep the cadence Schedule permission lets the agent post the roundup at the same time each week.
This week in the community: 140 new members, a great guide on local dev with Docker from @mira, and 3 long-standing questions finally answered. Thread with links below. Thanks to everyone who helped a newcomer this week.
Make the community's work visible
Members stay in communities where their contributions are noticed. Public updates do that at scale: they thank people, show newcomers what the community is like, and point outsiders to the best discussions. The raw material already exists in your forum or chat. An agent can gather and draft it; a moderator knows the context behind every name.
Setup
- Connect the networks your members use. Community-driven audiences are often on Mastodon and Bluesky, as well as LinkedIn for professional communities.
- Build a weekly flow in n8n or Make that sends highlights to the REST API. See API and SDK.
- In brand memory, write the community's tone, how you credit people, and topics that stay inside the community.
Permissions
The community agent needs draft and schedule. Keep it draft-only: public shout-outs involve real people, and a moderator should confirm each one. If several moderators share the work, they each approve from the inbox, and the audit log shows who approved each post.
Measuring community updates
Track visits back to your community and new member signups from tagged links built with the UTM builder. Per-post metrics show engagement where networks provide it. The best signal is often inside the community: members sharing the roundup.
Pitfalls
- Naming people who prefer privacy. Ask before tagging and keep an opt-out list in brand memory.
- Cross-posting chat screenshots. They often contain other members' names. Use text and link instead, and add alt text to any image.
- Hashtag overload on Mastodon. One or two relevant tags are enough.
Templates that fit: thank-you post, poll post, Bluesky intro post.