CHATBOTS

Welcome first-time contributors in Discord on their first merge

When a pull request is merged in GitHub, this checks whether it's the author's first merge, matches them to a Discord member, posts a public welcome in the contributors channel.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPull request mergedGitHubGitHub
  • LogicIs this the author's first merge?
  • ActionLook up linked Discord memberPostgreSQLPostgres
  • ActionPost welcome shout-out in channelDiscordDiscord
  • OutputLog milestone to NotionNotionNotion

What it does

Turns a merged pull request into a community moment. The instant someone's PR lands, the workflow detects whether it was their very first merged contribution, finds their linked Discord account, and celebrates them by name in the contributors channel — then records the milestone for your community changelog.

When to use it

Use this to make first-time contributors feel seen the moment their work ships, and to build a running log of who joined the contributor ranks and when. It pairs naturally with a role-gating workflow that grants the Contributor role.

How it works

  1. 1A GitHub webhook fires when a pull request is merged.
  2. 2A logic step checks whether this is the author's first merged PR in the repo.
  3. 3The Postgres action looks up the author's verified Discord member ID.
  4. 4If it's a first merge and a Discord link exists, the Discord action posts a public welcome shout-out tagging the new contributor.
  5. 5The Notion action appends the contributor and PR details to the community milestone log.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect DiscordCommunity channels + voice + bots.
  4. 4
    Connect NotionPages, databases, comments.
  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.