CHATBOTS

Reconcile Discord contributor roles against GitHub activity weekly

On a weekly schedule, an agent audits every member holding a contributor role, compares it to live GitHub activity.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList members with contributor roleDiscordDiscord
  • ActionLoad stored GitHub linksPostgreSQLPostgres
  • ActionRe-check live GitHub activityGitHubGitHub
  • LogicClassify each member's drift
  • OutputPost reconciliation plan to staff channelDiscordDiscord

What it does

Keeps your contributor roles honest over time. Once a week an agent walks every member who currently holds a gated role, re-checks their GitHub contribution status, and flags drift — members whose linked account was deleted, renamed, or no longer meets the threshold — then proposes the corrective role changes for the community lead to confirm.

When to use it

Use this when roles granted long ago have gone stale: people who deleted their GitHub, switched handles, or were granted manually without verification. It prevents the contributor tier from quietly inflating with members who no longer qualify.

How it works

  1. 1A weekly schedule triggers the audit.
  2. 2The Discord action lists all members currently holding a contributor role.
  3. 3The Postgres action loads each member's stored GitHub link, and the GitHub action re-checks live contribution status.
  4. 4The agent reasons over each case — broken link, dropped below threshold, or still valid — and drafts a reconciliation plan.
  5. 5The output posts the proposed removals and reasons to a staff review channel in Discord for one-click approval.

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.