LEAD GENERATION
Agent-Qualified GitLab SDK Adopters Routed to Territory Owners
An agent investigates each new GitLab SDK adopter, decides fit and territory from research, then either creates a Salesforce lead and DMs the assigned rep in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled GitLab search for new adoptersGitLab
- ActionAgent researches each org for fitExa
- LogicBranch on fit verdict and inferred territory
- ActionCreate qualified Salesforce lead with ownerSalesforce
- OutputDM territory rep in Slack; log low-fit to PostgresSlack
What it does
Uses an agent to do the judgment a human SDR would: research each new adopter, decide whether it is a real commercial fit, infer the right territory, and route accordingly. Strong fits become Salesforce leads with a rep DM; weak fits go to a nurture log instead of cluttering the pipeline.
When to use it
Use this when raw adoption volume is high and naive routing wastes rep time — you want qualification and territory assignment handled before anything reaches a human.
How it works
- 1A scheduled GitLab search surfaces new public repos that adopted your SDK.
- 2The agent researches each org with web search to assess size, industry, and buying fit.
- 3A logic branch splits on the agent's fit verdict and inferred territory.
- 4For qualified leads, a Salesforce lead is created with the agent's notes and owner assignment.
- 5Slack DMs the assigned territory rep with the brief; low-fit signals are written to Postgres for nurture.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ExaNeural search across the web.
- 3Connect SalesforceAccounts, opportunities, cases.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect PostgresAny Postgres URL — query, write, migrate.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Lead Generation workflows
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.
Score Zoom webinar poll answers into a tiered outreach queue
When a Zoom webinar ends, pull each attendee's poll responses, compute an intent score, and write a tiered (Hot/Warm/Cold) outreach queue to Airtable for the sales team to work.
Classify open-text webinar poll answers with AI and enrich the lead record
For webinars that use free-text poll questions, an AI step reads each attendee's written answers, classifies intent and pain points into structured fields.
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.
Agent-driven Brave intent harvest with enrichment and Gmail draft outreach
A CEO-driven agent harvests intent signals from Brave, enriches each prospect via web research, writes a personalized cold email.
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.
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.