Community · n8n

Celebrate GitHub Star Milestones in Slack Automatically

An n8n workflow that checks your repository's star count on a schedule, detects when you cross a milestone like 100, 500 or 1,000 stars, and posts a celebration message to Slack — so your team gets a morale boost the moment the community rallies behind your project.

difficulty Beginnersetup 25 minresult A Slack celebration fires the moment your repo crosses each star milestone
  1. 1

    Schedule the check

    Add a Schedule Trigger running every few hours. Star growth doesn't need minute-level precision, and a light cadence keeps you well within GitHub's generous API limits.

  2. 2

    Fetch the star count

    An HTTP Request to https://api.github.com/repos/{owner}/{repo} returns the repo metadata including stargazers_count. A token in the header raises your rate limit but isn't strictly required for public repos.

  3. 3

    Detect a crossed milestone

    A Code node reads the previous count from static data, checks whether any milestone in your list falls between the old and new counts, and outputs the crossed milestone (or nothing). It then stores the new count for next time.

  4. 4

    Only continue if a milestone was hit

    An IF node stops the run unless a milestone was crossed. Most runs end here quietly — the workflow only speaks up when there's something to celebrate.

  5. 5

    Celebrate in Slack

    A Slack node posts a festive message — 🎉 We just hit {{milestone}} stars on GitHub! — with a link to the repo. Small automated wins like this keep a team energized about their open-source momentum.

Frequently asked questions

Why poll instead of using the star webhook?

GitHub does have a `star` webhook, but it fires on every single star, making milestone detection noisy. Polling the count on a schedule and comparing against the last stored value is simpler and lets you cleanly detect 'we just crossed 500'. It also works for repos where you can't add webhooks.

How does it remember the last count?

The workflow stores the previous star count in n8n's workflow static data (`getWorkflowStaticData`). Each run compares the current count to the stored one, checks whether any milestone lies between them, then saves the new count. No external database needed.

Can I customize the milestones?

Yes — they're just an array in a Code node: `[100, 250, 500, 1000, 2500, 5000, 10000]`. Add or change values freely. You could also make it fire every 1,000 stars automatically past a threshold, so big projects keep celebrating without editing the list.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.