Case study / Meta API · Community automation
An Instagram join bot for a growing hiking community
One automation that answers “how do I join?” across Instagram DMs, story replies and post comments — so the admin team no longer types the same welcome message all day.
The problem
As the Lifestyle Hikers page grew, the same questions arrived all day — “How do I join?”, “Send the link”, “Can I get the WhatsApp?” — in three different places: DMs, story replies and post comments.
The bot had to answer only genuine join questions, never spam, and stay reliable enough to still make sense months later.
What I built
- 01
Three entry points, two event types
DMs and story replies arrive as message events and share one reply path. Comments arrive as comment events and need a private reply sent against the comment ID.
- 02
Only reply when the intent is clear
A keyword filter (join, link, group, whatsapp, how to join, signup, member, community) means “beautiful hike” gets left alone. Most bad automation isn’t broken — it’s too eager.
- 03
No bot talking to itself
Echo events, edits and read receipts are filtered out, so the workflow never mistakes its own replies for new messages.
- 04
A welcome that does the onboarding
The reply walks people through following the page, the website, the community form and turning up to hikes — with WhatsApp access after real participation.
Results
- Comment “join” on a post → private DM. Reply “join” to a story → welcome DM. Send “join” in a DM → welcome DM.
- Replies only to clear join intent; ordinary comments are ignored.
- No self-reply loops once echo and non-message events were filtered.
- The token type and testing gotchas are documented, so the setup can be maintained without relearning Meta’s quirks.
Have a similar problem?
Let’s make
something work.
Automation & AI projects start at J$60,000 per workflow. Tell me what you’re dealing with and you’ll get a clear proposal within a few days.
More case studies