CHATBOTS

Auto-assign tiered Discord roles from GitHub contribution volume

On a daily schedule, this tallies each member's merged PRs in your repo and promotes them through Discord role tiers (Newcomer, Contributor.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionRead member-to-GitHub directoryPostgreSQLPostgres
  • ActionFetch merged-PR count per memberGitHubGitHub
  • LogicMap count to role tier
  • ActionApply tier role, remove lower tierDiscordDiscord
  • OutputPersist updated tierPostgreSQLPostgres

What it does

Keeps Discord roles in sync with how much each person has actually contributed. Once a day it pulls each linked member's lifetime merged-PR count from GitHub and assigns the matching tier role — promoting people automatically as they cross the next threshold, with no manual review.

When to use it

Use this when a single Contributor role is too blunt and you want recognition tiers (e.g. 1+ PRs = Contributor, 10+ = Trusted, 50+ = Core Maintainer) that update themselves as the community grows.

How it works

  1. 1A scheduled trigger runs the workflow once per day.
  2. 2A Postgres action reads the member directory mapping Discord IDs to GitHub usernames.
  3. 3The GitHub action fetches each member's merged-PR count in the repo.
  4. 4A logic step maps each count to its tier (Newcomer, Contributor, Trusted, Core).
  5. 5The Discord action applies the new tier role and removes any lower tier it replaces.
  6. 6The run writes the updated tier back to Postgres so promotions are auditable.

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
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.