LEAD GENERATION

Tag new stargazers who are already accounts in Attio as expansion signals

When someone stars your repo, checks whether their company already exists in Attio; if it does, logs the star as an expansion/engagement signal on that account instead…

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew star on watched repoGitHubGitHub
  • ActionSearch Attio for matching companyAttio
  • LogicBranch: existing account vs net-new
  • ActionLog engagement note on accountAttio
  • OutputAlert rep in Slack for net-newSlack

What it does

Not every stargazer is a net-new lead — sometimes it's an engineer at an existing customer or open opportunity. This workflow checks each new stargazer's org against your Attio CRM. If a matching company exists, it appends an engagement note ("engineer starred OSS repo") to that account as an expansion signal rather than spawning a duplicate record.

When to use it

Use this when your repo is popular enough that stargazers overlap with your existing pipeline, and you want product engagement to surface on current accounts for expansion and champion-tracking.

How it works

  1. 1A new star fires the trigger and the stargazer's org is resolved.
  2. 2The flow searches Attio for a company matching the org domain or name.
  3. 3A branch checks whether a match was found.
  4. 4If matched, it logs a timestamped engagement note on the existing account.
  5. 5If unmatched, it posts to Slack so the rep can decide whether to create a new prospect.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect AttioReal-time CRM with structured data + powerful views.
  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.