LEAD GENERATION

Dependents Daily Digest: Top New Companies Adopting Your Package, Triaged in Slack

Each morning, diffs the dependency graph against yesterday's snapshot, surfaces newly added company dependents, ranks them by ICP fit.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule triggers the dependency diff
  • ActionFetch current dependent repos and owning orgsGitHubGitHub
  • LogicDiff against prior snapshot for net-new company dependents
  • ActionEnrich each new org with industry and sizeBraveBrave Search
  • OutputPost ranked triage digest with claim/dismiss to SlackSlack

What it does

Delivers a short daily standup of who started depending on your package overnight. It compares today's dependent list to a stored snapshot, isolates net-new company dependents, ranks them by ICP fit, and posts a Slack digest where reps can claim or dismiss each lead inline.

When to use it

Use it when you want a low-friction daily ritual rather than a CRM dump. Ideal for small founder-led sales teams who want to eyeball new adopters every morning and route the good ones manually, keeping noise out of the CRM until a human says go.

How it works

  1. 1A daily schedule triggers the diff.
  2. 2GitHub returns the current set of dependent repos and owning orgs.
  3. 3The flow compares against the prior snapshot to find net-new company dependents.
  4. 4Brave Search enriches each new org with industry and size for ranking.
  5. 5A ranking step orders leads by ICP fit and trims noise.
  6. 6A Slack message posts the ranked digest with claim/dismiss actions for reps.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect Brave SearchWeb, news, image, video search.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.