CHATBOTS

Discord Verification Quiz Role-Gate

Greets each new Discord member in their verification channel, runs a short rules-comprehension quiz via DM, and grants the Verified role only when they pass.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew member joins the Discord guildDiscordDiscord
  • ActionDM the rules-comprehension quiz to the memberDiscordDiscord
  • LogicScore answers against the key (pass/fail)
  • ActionGrant Verified role on pass, send retry on failDiscordDiscord
  • OutputLog attempt, score, and outcome to AirtableAirtableAirtable

What it does

When someone joins your Discord server, this bot DMs them a short multiple-choice quiz covering your community rules. It scores the answers, and only when they pass does it assign the Verified role that unlocks the rest of the server. Failures get a friendly retry, and every attempt is logged so moderators can spot patterns.

When to use it

Run this when open registration is letting in bots or rule-breakers and a single reaction-role gate isn't enough. It works for any community that wants proof a member actually read the rules before granting channel access.

How it works

  1. 1A new member joining the guild fires the trigger.
  2. 2The bot opens a DM and posts the quiz questions one at a time, collecting replies.
  3. 3A scoring step compares answers against the answer key and computes pass/fail.
  4. 4On a pass, the bot calls Discord to add the Verified role; on a fail it sends a retry prompt with the rules link.
  5. 5The outcome, score, and timestamp are appended to an Airtable log for moderator review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.