CHATBOTS

Verify Discord identity via GitHub OAuth and store the link

When a member clicks Link GitHub, this completes a GitHub OAuth handshake, confirms ownership of the account, records the Discord-to-GitHub mapping in Postgres.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOAuth callback webhookHTTP webhook
  • ActionExchange code, read GitHub profileGitHubGitHub
  • LogicReject if GitHub account already linked
  • ActionUpsert verified identity mappingPostgreSQLPostgres
  • OutputDM member link confirmationDiscordDiscord

What it does

Establishes a trustworthy link between a Discord member and their real GitHub identity. Instead of trusting a typed-in handle, it runs a GitHub OAuth handshake so the member proves they own the account, then persists the verified mapping for every other workflow to rely on.

When to use it

Set this up first if you plan to role-gate or tier members by GitHub activity. It removes impersonation — nobody can claim a prolific contributor's handle, because verification requires logging into that GitHub account.

How it works

  1. 1A member clicks the Link GitHub button, firing an HTTP webhook with their Discord ID and an OAuth callback code.
  2. 2The GitHub action exchanges the code for a token and reads the authenticated user's profile.
  3. 3A logic step confirms the returned GitHub ID is not already linked to a different Discord account.
  4. 4The Postgres action upserts the verified Discord-to-GitHub mapping.
  5. 5The Discord action DMs the member confirming the link succeeded and which account is now bound.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect DiscordCommunity channels + voice + bots.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.