Will this hit prospects my AEs are already working?

No. Before doing anything else, the agent drops any visitor whose Warmly record already shows a match in your CRM pipeline, so you are only ever touching net-new people.

What happens if Apollo cannot find a verified email for a visitor?

The visitor is skipped for this run rather than pushed into Salesforce or Apollo with placeholder data. They can be picked up on a later run if Apollo gets new data.

How do I keep out-of-ICP titles out of my sequence?

You give the agent a list of in-bounds titles when you set the workflow up. Anyone whose verified Apollo title is outside that list is skipped, so the sequence stays clean.

Can I use HubSpot instead of Salesforce?

Yes. The same pattern works with HubSpot. Tell the agent to file a contact in HubSpot instead, and keep the Apollo enrollment step exactly the same.

Do I need a paid Apollo plan?

You need an Apollo plan that allows a master API key, which is what unlocks sequence enrollment. The free tier does not include it.

Warmly to Salesforce and Apollo: auto-enroll warm site visitors

Build an agent-based workflow that runs on a cron every 4 hours and turns newly identified Warmly site visitors into Salesforce leads enrolled in an Apollo outbound sequence.

On each run, do the following:

1. Call the Warmly action List Warm Visitors to pull identified people who visited my site since the last run (look back at least 4 hours, with a small overlap to be safe). I want the visitor list, not the account-level list.

2. From the Warmly result, drop any visitor whose response shows a CRM intersection (Warmly returns a flag/object indicating the person or account already exists in my CRM pipeline). Those are already being worked by an AE and must not be re-touched.

3. For each remaining net-new person, call Apollo People Search to confirm a verified work email and current title. Match by full name + company domain from the Warmly record.

4. Apply an ICP title filter. I will provide the in-bounds titles as a workflow input (for example: VP of Sales, Head of RevOps, Director of Demand Gen, CMO, Chief Revenue Officer). If the Apollo-verified title is not in the ICP list, skip the person so the sequence stays clean.

5. For each qualified person, call Salesforce Create Lead with: FirstName and LastName from Warmly, Title from Apollo (the verified one), Company from Warmly, Email from Apollo, LeadSource set to "Warmly visitor", and a Description that lists the pages they viewed on my site and their session count (both from the Warmly response). If a Salesforce lead with the same email already exists, skip the create and log it instead of erroring.

6. Then call Apollo Add Contacts to Sequence to enroll the new Apollo contact in my designated warm-visitor follow-up sequence. I will provide the sequence ID and the sending mailbox(es) as workflow inputs.

Configuration I will provide on first run:

Warmly API key and organization ID
Apollo master API key
Salesforce connection
ICP title allowlist
Apollo sequence ID for the warm-visitor follow-up
Sending mailbox email address(es) used by that sequence

Guardrails:

Never enroll anyone whose Warmly record shows an existing CRM intersection (current customers, open opps, contacts already owned by a rep).
If Apollo cannot return a verified email for a person, skip them rather than push a partial lead.
De-dupe against Salesforce by email before creating leads.
On per-record errors (Apollo 429, Salesforce permission error, etc.), continue with the next visitor and surface a summary at the end of the run.

At the end of each run, produce a short summary: total visitors pulled, how many were dropped for CRM intersection, how many were filtered out by ICP, how many leads were created in Salesforce, and how many were enrolled in the Apollo sequence.

What it does

Pulls the latest identified visitors from your Warmly workspace every four hours.
Skips anyone whose record already shows up in your CRM pipeline so reps are not double-touched.
Verifies a current work email and job title in Apollo, and only keeps people whose title matches your ICP.
Files each qualified visitor in Salesforce as a lead tagged Warmly visitor, with the pages they viewed and their session count in the description.
Enrolls the qualified person in your designated warm-visitor follow-up sequence in Apollo from the mailbox you choose.

What you’ll need

A Warmly workspace with identified visitor traffic.
An Apollo account with a master API key and a warm-visitor follow-up sequence already built.
A Salesforce login with permission to create leads.
Your ICP target titles (the roles the warm-visitor sequence is meant for).

How to customize it

Change the cadence. Run it hourly, every two hours, or once a day depending on traffic volume.
Swap the Apollo sequence. Point it at a different campaign by season, persona, or campaign theme.
Tune the ICP title list. Widen it to capture more buyers or tighten it to keep junior contacts out.
Edit the Salesforce lead source label or description format to match how your team reports on intent leads.

Use cases

Lead Enrichment
Data Sync

Turn Warmly site visitors into Salesforce leads and an Apollo sequence

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts