Spot accounts publishing new code repositories

Each week, checks your accounts for newly published public code repositories, has AI flag work related to what you sell, saves the repos and alerts the owner.

7 stepsWeekly check

The workflow diagram

Spot accounts publishing new code repositories: workflow diagramThe 7 steps of this workflow, from its trigger to the final step.Every Thursday, for each target account. Scores, schedules and toolsBWWHENTRIGGEREvery Thursday, for eachtarget accountScores, schedules and toolsRead new public repositories. Paid per resultDATHENRead new publicrepositoriesPaid per resultAny new repositories?Any newrepositories?Related to what you sell?. Waits and logicBWTHENRelated to what you sell?Waits and logicRelevant?Relevant?Save the repositories. Audiences and recordsBWTHENSave the repositoriesAudiences and recordsAdd to Building in public. Audiences and recordsBWTHENAdd to Building in publicAudiences and recordsAlert the owner. AIMEEAITHENAlert the ownerAIMEEThis path stops hereThis path stops hereThis path stops hereYesNoYesNo
This is the workflow BrandWell builds on your canvas when you add it. You can change any step.

What this workflow does

Each week, checks your accounts for newly published public code repositories, has AI flag work related to what you sell, saves the repos and alerts the owner.

Why it works. A new SDK or internal tool going public shows where an engineering team is investing before any announcement does.

Nothing is sent outside your team, so nothing waits for approval.

How it works

It starts: Every Thursday, for each target account, or run it now.

  1. 1

    Read new public repositories

    Runs a BrandWell data lookup and brings the result back into the workflow.

  2. 2

    Any new repositories?

    If yes, it goes on to "Related to what you sell?". If no, it stops for that person.

  3. 3

    Related to what you sell?

    AIMEE classifies, extracts or writes using your instruction.

  4. 4

    Relevant?

    If yes, it goes on to "Save the repositories". If no, it stops for that person.

  5. 5

    Save the repositories

    Saves what was found onto the record.

  6. 6

    Add to Building in public

    Saves the people to an audience you can use anywhere.

  7. 7

    Alert the owner

    AIMEE tells the right person, with the context they need.

What you need

  • Workflow Wallet funds for paid lookups
  • AIMEE in your BrandWell plan
  • A list of target accounts

What it costs

Paid steps are charged per result from your Workflow Wallet, and you set the limit.

  • Assumes AIMEE is already enabled in your plan. Subscription fees are separate.
  • Execution estimates are not a total campaign price. External tool subscriptions, model usage, advertising spend and delivery costs are separate unless explicitly itemized.

$5.32 typical per 100 account checks, up to $5.32

Free sources run first when they can answer. You see a price before anything paid runs. Estimates use current customer prices.

Data partners

Free sources run first, then the rest in the order this workflow tries them.

  • Read new public repositories

    • PredictLeads