LEAD GENERATION

Dependent-Repo Harvester to Salesforce Accounts

Scrapes the public repos that depend on your package, maps each owning organization to a company.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled dependents harvest
  • ActionScrape dependent repos and owning orgsApify
  • ActionFetch org and maintainer detailsGitHubGitHub
  • LogicKeep orgs not already in Salesforce
  • ActionCreate account and contact in SalesforceSalesforce
  • OutputAttach dependency evidence noteSalesforce

What it does

Organizations that import your package into their own repos are using your tech in production-adjacent code. This workflow uses a scraper to harvest the public dependent repos, resolves each owning org to a company, and creates Salesforce accounts and contacts for the ones not already in your CRM, attaching which repo and file declared the dependency.

When to use it

Use it when your package has a public dependents graph and you want to turn real adoption into named accounts for product-led sales outreach.

How it works

  1. 1A scheduled run launches the harvest.
  2. 2Run an Apify actor to scrape the dependents and their owning GitHub orgs.
  3. 3Pull org and maintainer details from the GitHub API for each owner.
  4. 4Filter to organizational owners and drop accounts already in Salesforce.
  5. 5Create the company as a Salesforce account and the maintainer as a contact.
  6. 6Attach a note with the dependent repo, file, and detection date as adoption evidence.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ApifyActors, scrapers, datasets.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  3. 3
    Connect SalesforceAccounts, opportunities, cases.
  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.