LEAD GENERATION

Route repeat visitors to the right CRM owner or net-new dossier

On each repeat-visit signal, checks whether the company already exists in Salesforce.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRepeat-visit signal receivedHTTP webhook
  • ActionLook up the domain in SalesforceSalesforce
  • LogicBranch on existing account vs net-new
  • ActionEnrich net-new accounts with firmographicsExa
  • OutputNotify owner or create assigned lead dossierSalesforce

What it does

A returning visitor might be an open opportunity, an existing customer, or a brand-new account, and each needs different handling. This workflow checks Salesforce first, then routes: known accounts notify their owner, unknown ones become enriched net-new dossiers assigned to an SDR.

When to use it

Use it when your org lives in Salesforce and you want intent signals to respect existing account ownership instead of double-touching live deals or stepping on AE territory.

How it works

  1. 1A webhook fires on a confirmed repeat-visit signal with the company domain.
  2. 2The workflow looks up the domain in Salesforce.
  3. 3A branch decides the path: if the account exists, it notifies the current owner of fresh intent; if not, it continues to enrichment.
  4. 4For net-new accounts, Exa pulls firmographics and contacts.
  5. 5A new Salesforce lead with the dossier is created and round-robin assigned to an SDR for follow-up.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect ExaNeural search across the web.
  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.