Community Ops Crew
Events and the member database stay aligned. The weekly summary shadows for a week before it posts.
For
The community has events, Slack, and a member database. Follow-ups often have no owner.
When you're done
Events land in the database. The weekly summary goes out on time. Unowned follow-ups get flagged.
How
- 01 Stand up the community ops line.
Connect the events tool, Slack, and the member database.
- 02 Set the weekly beat.
Events write into the database. The weekly summary goes out. Unowned follow-ups get chased. It tells you what slipped.
- 03 Shadow one week with no public post.
Do not post in public yet. You check the summary and the list.
- 04 Go live only after the list is right.
The original listing frames this as a fleet that buys back a slice of time, not one catch-all chat.
Notes
What's good: the summary and the follow-ups have an owner. Memory is not the system. The catch: post in public on week one and a wrong list goes out.
Prompt
Set up a new bot for me to run community ops on a weekly schedule. Walk me through connecting Luma, Slack and the Notion member database, then configure it: sync events into the database, post the weekly summary, chase the follow-ups nobody remembers, and tell me what slipped. Ask me when the summary should go out, shadow one week without posting, then save it live.
原文 https://botdirectory.ai/bots/community-ops-crew/
Related plays
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About