LEAD GENERATION

Stargazer Dev-Rel Outreach Draft to Gmail

For each qualified new stargazer, it drafts a personalized, non-salesy dev-relations email referencing their actual GitHub work and saves it as a Gmail draft for a human…

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew star on repo (GitHub watch webhook)GitHubGitHub
  • ActionFetch profile and recent public reposGitHubGitHub
  • LogicQualify: skip bots and empty profiles
  • ActionDraft grounded dev-rel emailOpenAI
  • OutputSave as Gmail draft for human reviewGmailGmail

What it does

Turns a fresh star into a ready-to-review outreach draft. The workflow looks at the stargazer's profile and recent public activity, writes a short, genuine dev-rel email that references something specific they've built, and leaves it as a Gmail draft so a person stays in the loop before anything sends.

When to use it

Use this when you want personalized stargazer outreach at volume but refuse to auto-send cold email. Good for developer advocates who want the writing done but the judgment kept human.

How it works

  1. 1A GitHub webhook fires when someone stars the repo.
  2. 2The flow pulls the stargazer's profile plus their most recent public repos and languages.
  3. 3A qualification gate skips bots, accounts with no email signal, and profiles with zero public activity.
  4. 4An LLM step drafts a concise email grounded in the person's real work — no generic praise.
  5. 5The draft is created in Gmail (not sent) addressed to the inferred contact, with a subject and reviewer note.
  6. 6The reviewer opens Gmail, edits if needed, and sends.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.