CHATBOTS

Role-gate new Discord members by verified GitHub contribution

When a new member runs /verify in Discord, this checks whether their linked GitHub account has merged a PR into your repo and grants the Contributor role only if it has.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMember runs /verify slash commandDiscordDiscord
  • ActionSearch merged PRs by GitHub usernameGitHubGitHub
  • LogicBranch on merged-PR count (>= 1)
  • ActionAssign Contributor role to memberDiscordDiscord
  • OutputReply with verification resultDiscordDiscord

What it does

Gates the Contributor role behind a real, merged contribution. A new member runs a `/verify` slash command with their GitHub handle, the workflow confirms they have at least one merged pull request in your repository, and only then assigns the gated Discord role. Everyone else gets a friendly nudge on how to qualify.

When to use it

Run this for open-source communities where you want channels, voting, or perks reserved for people who have actually shipped code — not just anyone who joined the server. It stops drive-by self-promoters from claiming contributor status.

How it works

  1. 1The Discord `/verify` slash command fires with the member's claimed GitHub username.
  2. 2The GitHub action searches merged PRs authored by that username in the target repo.
  3. 3A logic branch checks the merged-PR count: zero means unverified, one or more means verified.
  4. 4If verified, the Discord action assigns the Contributor role to the member.
  5. 5If not, the workflow replies in the channel with the contribution guide link and exits without granting the role.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  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.