Discord community verification bot
Community Verification Automation
Python Discord bot for Amazon FBA communities—four-question DM intake, Verified role automation, and GoHighLevel webhook lead sync.
Background & Context
DiscordVerifyBot is a runnable Python bot for an Amazon FBA community. On member join it welcomes users in #✅-verify-access, collects four FBA questionnaire answers (primary DM flow; alternate /verify modal path), assigns a Verified role (or notifies admins if hierarchy fails), and POSTs results to a GoHighLevel webhook. Entry point is a single ~540-line bot.py using discord.py, aiohttp, and dotenv.
Community operators were burning time manually verifying new members and assigning roles. Public chat answers leak intent data; delays hurt onboarding; inconsistent checks create access gaps. The bot gates privileged channels behind a private Q&A that also captures CRM-ready lead fields: interest, experience, challenge, and selling vs researching status.
Sessions live in bot.verification_sessions (in-memory). Docs are explicit: users who join while the bot is offline need manual recovery; /verify requires an existing session. Role hierarchy must keep the bot’s top role above Verified. DISCORD_BOT_TOKEN is required; GOHIGHLEVEL_WEBHOOK_URL is optional (warns if missing).
The Challenge
An Amazon FBA Discord community needed gated access and structured lead capture without forcing new members to answer sensitive questions in public channels—or relying on staff DMs at scale. Without a coherent discord community verification bot foundation, Community Verification Automation stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Tekvers implemented a discord.py verification bot: join-triggered welcome + ✅ reaction, sequential DM (or slash-modal) Q&A, Verified role grant with hierarchy fallbacks, and aiohttp JSON webhook sync to GoHighLevel. Tekvers delivered a maintainable discord community verification bot system for Community Verification Automation using Python, discord.py, aiohttp, python-dotenv, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Join-triggered private intake
`on_member_join` clears prior session state, posts a welcome embed in `#✅-verify-access`, adds a ✅ reaction, and stores session step/answers/guild/join metadata—so verification starts immediately without public chat Q&A.
Four-question FBA questionnaire
Questions cover FBA interest, prior experience, biggest challenge, and selling vs researching status. Primary path: reaction → DM replies; alternate: `/verify` opens a `VerificationModal` TextInput (max 1000) per step with progress embeds.
Role grant + CRM handoff
On completion the bot assigns/creates Verified (positioning under the bot role when possible), DMs success, POSTs webhook payload keys `interest` / `experience` / `challenge` / `status`, and deletes the session—with admin channel notice + user DM if role assignment is forbidden.
What We Delivered
- Single-module Python Discord bot (`bot.py`) with discord.py ≥2.5 and intents for members/message content
- Join welcome flow in `#✅-verify-access` with ✅ reaction gate
- Four-question DM verification sequence plus `/verify` modal alternate path
- Automatic Verified role create/assign with dual strategies and admin fallback
- GoHighLevel webhook POST via aiohttp (mapped answer keys)
- Slash command sync in `setup_hook`; OAuth invite URL printed on ready
- Env-based config (`DISCORD_BOT_TOKEN`, optional `GOHIGHLEVEL_WEBHOOK_URL`)
- Documented Replit/runtime workflow (pip install + `python bot.py`)
Outcomes & Impact
- Faster gated onboarding for FBA Discord members
- Private answer capture suitable for community ops and CRM follow-up
- Reduced staff time on repetitive verification DMs
- Clear access boundary: unverified members do not receive Verified by default
New FBA members answer four private questions, get Verified access, and land in GoHighLevel automatically. Tekvers shipped practical community automation—with honest limits around in-memory sessions and Discord role hierarchy—rather than inventing a multi-tenant bot platform.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.