LEAD GENERATION

New GitLab SDK Adopter to HubSpot + Slack Warm Intro

Watches public GitLab repos for first-time imports of your SDK, enriches the committer's org, creates or updates a HubSpot lead.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled GitLab search for new SDK importsGitLabGitLab
  • LogicDedup against already-seen repos and orgsPostgreSQLPostgres
  • ActionRecord new adopter in PostgresPostgreSQLPostgres
  • ActionUpsert company and lead in HubSpotHubSpotHubSpot
  • OutputPost warm-intro brief to sales Slack channelSlack

What it does

Detects when a public GitLab repository newly adds your SDK as a dependency, then turns that signal into a routed warm lead. It deduplicates so an existing adopter never re-triggers, syncs the account into HubSpot, and pings the right rep in Slack with everything needed to reach out.

When to use it

Run this when developer adoption is your top-of-funnel signal and you want to catch teams the moment they try your library — before a competitor or before they churn out of the trial. Ideal for devtools, API, and infra companies with an open-source SDK.

How it works

  1. 1A scheduled poll searches public GitLab for new commits adding your package name to manifest files (package.json, requirements.txt, go.mod).
  2. 2A dedup check against Postgres filters out repos and orgs already seen, so only first-time adopters pass.
  3. 3The repo owner and org are resolved, and the new adopter is recorded in Postgres.
  4. 4A HubSpot upsert creates or updates the company and a lead contact with the repo URL and detected version.
  5. 5A Slack message posts the warm-intro brief to your sales channel with owner, repo, and suggested opener.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  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.