Prospecting
How to Route Enriched Leads to Outreach Tools
Send enriched leads where reps work: which records belong in the CRM or a sequencer, what each tool receives, per-send limits and the checks to run first.
By the GTM Scoop team · Published · 4 min read
Enriched records only pay off when they reach the tool where someone acts on them. A list that sits in a downloads folder helps nobody, and one pushed everywhere at once creates duplicates, double touches and arguments about who owns an account.
This post covers how to decide where each record should go, what GTM Scoop sends to each tool, the limits to plan around, and the checks worth running before you press send.
Decide where each record belongs
- The CRM (Salesforce, HubSpot or Zoho CRM) for records that need an owner, a stage and a history: inbound leads, target accounts, anything an account executive will work.
- The sequencer (Instantly or Apollo) for records going straight into an outreach campaign.
- Clay or Notion when the records need more research or review before anyone contacts them.
- Slack or Microsoft Teams to tell a channel that a new list is ready, with the records in the message.
- Snowflake or ClickHouse when the records feed reporting, scoring or your own models.
Many teams use two at once: the CRM as the record of who owns an account, and the sequencer for the outreach itself. Decide which one is the source of truth for ownership before the first send.
What GTM Scoop can send
Send from a list you bought, from an analysis run's matched prospects, from the rows you pick in a run's results, or send a prospect report. Records get a Domain column when they have a website or a work email to take it from.
What each tool receives
Salesforce
Records become Leads or Contacts (Leads unless you choose), up to 500 per send. Prospect reports can go too.
HubSpot
Records become contacts, and a contact with the same email is updated instead of added twice. Up to 500 per send, plus prospect reports.
Zoho CRM
Records become Leads or Contacts, matched on email, up to 500 per send. A prospect report arrives as a Lead with the report as a note.
Instantly
Records become leads in the campaign you pick, up to 200 per send. Reports are not sent to Instantly.
Apollo
Records become contacts in your Apollo account, optionally added to one of its lists, up to 200 per send. Reports are not sent to Apollo.
Clay and Notion
Clay: Records and prospect reports go into a Clay table, up to 200 records per send. Notion: Records are added to the database you pick, up to 100 per send. Reports can also go to a page.
Slack and Microsoft Teams
Slack: Records and prospect reports post to the channel you pick when you send, up to 500 records per send. Teams: Records and reports post to the channel you pick when you send, up to 500 records per send.
Snowflake and ClickHouse
Snowflake: Rows are inserted into GTMSCOOP_PROSPECTS, up to 500 per send. ClickHouse: Rows are inserted into a gtmscoop_prospects table, up to 500 per send.
Each tool connects with a sign-in or an API key of its own; the integrations page lists how each one connects and what it can bring in.
Limits to plan around
- Per send: up to 500 records to Salesforce, HubSpot, Zoho CRM, Slack, Teams, Snowflake and ClickHouse; up to 200 to Instantly, Apollo and Clay; up to 100 to Notion. Split bigger lists into several sends.
- Each account can send 60 times an hour. A send to Apollo, Clay, Instantly, Notion, Slack or Teams that runs past 45 seconds stops and tells you how many records did not go.
- Sends to Salesforce, HubSpot, Zoho CRM, ClickHouse and Snowflake are made from the signed-in web app. The other tools also accept sends made with your API key.
Checks before you send
- De-duplicate against the CRM. Match people on email and companies on the Domain column, so existing records are updated or skipped rather than added again.
- Remove anyone on your suppression list. An opt-out recorded in one tool has to hold in all of them.
- Look at how each record was matched and spot-check a sample, especially before a large campaign.
- Make sure every record bound for an email sequence has a work email; a record without one does little in an email campaign.
- Agree the owner. Let the CRM's assignment rules decide who owns a new lead, rather than whoever happened to send it.
- Send the top accounts to the CRM first and the rest to the sequencer, so the people who own accounts see them before automation does.
Three routing patterns
Inbound leads
Enrich each new lead, send it to the CRM as a Lead, let assignment rules route it by territory and size, and let the owner decide whether it goes into a sequence. CRM enrichment for HubSpot and Salesforce covers the enrichment half.
Outbound to a new segment
Build the audience, unlock the accounts you will work this month, send them to an Instantly campaign or to Apollo in batches of 200, and send the same accounts to the CRM so replies have a record to land on.
Lookalike prospects
Run a lookalike analysis on your best customers, send the closest matches to the CRM for account executives, put the rest into a sequence, and post the list to the team's Slack or Teams channel so everyone knows it exists. How to find lookalike companies explains the analysis.
Automate the sends
Sends to Apollo, Clay, Instantly, Notion, Slack and Teams can be scripted with an API key, so a scheduled job can push each day's new prospects into a campaign. CRM and warehouse sends stay in the signed-in web app, where a person makes them. The Send to Tools API reference has the request for each tool.
Try it in GTM Scoop
Connect Salesforce, HubSpot, Instantly, Apollo and 7 more tools, then send enriched records where your team works.