LEAD GENERATION

Attach Hiring Signals to Salesforce Opportunities or Open New Leads

Routes each new hiring signal in Salesforce: if an open opportunity exists it logs the signal as a task on it, otherwise it creates a deduplicated lead.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew scored account arrivesPostgreSQLPostgres
  • ActionLook up account and open dealsSalesforce
  • LogicBranch: deal vs. lead vs. dedup
  • ActionLog task or create deduped leadSalesforce
  • OutputWrite outcome back for auditPostgreSQLPostgres

What it does

This applies smart routing logic so hiring signals land in the right place in Salesforce. A signal for an account with a live deal becomes a timely activity on that opportunity; a signal for an unknown account becomes a fresh lead, checked against existing records first so you never spawn duplicates.

When to use it

Use it when Salesforce is your source of truth and duplicate prevention matters. It suits AE-and-SDR teams who need new intent reflected on in-flight deals ("they are hiring three more engineers, push the bigger package") without polluting the org with redundant leads.

How it works

  1. 1A new scored account from the harvester triggers the run.
  2. 2Salesforce is queried for a matching account and any open opportunity.
  3. 3A branch decides the path: open opportunity, existing-but-no-deal, or net-new.
  4. 4With an open opportunity, a task carrying the hiring signal and recommended play is logged against it.
  5. 5With no match, a deduplicated lead is created using domain and company-name matching.
  6. 6The outcome and Salesforce record id are written back to Postgres for auditing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.