LEAD GENERATION
Detect GitLab Repos Switching Off a Competitor SDK
Flags public GitLab commits that remove a competitor's package and add yours in the same change, scores the switch intent.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled GitLab commit search on manifestsGitLab
- LogicConfirm competitor removed and your SDK added in diff
- LogicScore switch intent; drop low-signal repos
- ActionStore switch and upsert HubSpot dealHubSpot
- OutputAlert competitive-deals Slack channelSlack
What it does
Finds the highest-intent developer leads: repos that drop a rival library and adopt yours in a single commit. It reads the commit diff, confirms both the removal and the addition, scores the switch, and routes only strong signals to sales.
When to use it
Use this when win-back and competitive displacement matter — you want to engage a team exactly when they have already chosen you over a competitor, and arm your rep with the before/after to anchor the conversation.
How it works
- 1A scheduled GitLab search pulls recent public commits touching dependency manifests.
- 2A logic step parses each diff to confirm a competitor package was removed AND yours was added in the same change.
- 3A scoring branch weighs repo activity and stars; low-signal switches are dropped.
- 4Qualified switches are written to Postgres and upserted into HubSpot as a competitive-displacement deal.
- 5Slack alerts the competitive-deals channel with the diff summary and a recommended talk track.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect HubSpotCRM, deals, marketing, support.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Lead Generation workflows
Manual Brave keyword sweep into an Airtable research board
On demand, sweeps a topic across Brave Search, clusters the results by buying stage with an LLM, and writes a deduplicated research board to Airtable with company, source URL.
Fast-track hot webinar leads into HubSpot and ping the rep on Slack
After a webinar, identify attendees whose poll answers signal high purchase intent, create or update their HubSpot contact with a lead score.
Webhook-triggered Brave rising-keyword check into a Notion trend queue
When an external trend or alert tool fires a webhook with a keyword, checks Brave for current intent volume and freshness, has an LLM judge whether it's a real warm signal.
Fuzzy-match badge companies to Salesforce accounts and enrich
Resolves messy hand-typed company names from badge scans to canonical Salesforce accounts using domain and fuzzy-name matching, enriches missing firmographics.
Daily rollup of scored webinar leads from Airtable into HubSpot lists
On a schedule, read newly scored webinar leads from Airtable, sync each into the matching HubSpot tiered list (Hot/Warm/Cold).
Instantly triage uploaded badge CSVs and notify the SDR lead
Accepts a badge-scan CSV via webhook, validates and dedupes it on the spot, checks each attendee against HubSpot.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.