LEAD GENERATION

Weekly Fork-and-Clone Momentum Digest of Top Accounts

On a weekly schedule, ranks repos that forked or heavily cloned yours, enriches the orgs behind the most active forks, and ships a prioritized account digest to Notion and Slack.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionPull recent forks from GitHubGitHubGitHub
  • ActionFetch fork owner org and activityGitHubGitHub
  • LogicRank by activity; keep org-owned above threshold
  • ActionEnrich top orgs via ExaExa
  • ActionWrite ranked digest to NotionNotionNotion
  • OutputPost top accounts to SlackSlack

What it does

Each week it looks at who forked your repo and which orgs show real engineering activity on those forks, then surfaces the companies investing the most effort with your code as a ranked list of target accounts.

When to use it

Use this when forks are a stronger signal than stars for your tool — teams that fork and build on it are evaluating seriously. The weekly cadence gives sales a steady, deduplicated feed of accounts to work rather than a noisy real-time stream.

How it works

  1. 1A weekly schedule fires the run.
  2. 2Pull the list of forks created or updated in the last seven days from GitHub.
  3. 3For each fork, fetch the owning org and commit activity to gauge real usage.
  4. 4Rank by activity and keep only org-owned forks above a threshold.
  5. 5Enrich the top orgs with Exa for company size and funding context.
  6. 6Write the ranked digest to a Notion database for the week.
  7. 7Post the top accounts summary to Slack with links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect ExaNeural search across the web.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.