Connecting Your Outbound Tools
How to automatically deliver scored leads to Slack, Zapier, Make, Google Sheets, HubSpot, or any webhook.
Automatic Lead Delivery
The AI SDR Agent can automatically send scored leads to your existing tools — no manual CSV exports needed. Every time the agent surfaces new leads, they're delivered to whatever channels you configure.
You have four options, from simplest to most flexible:
Option 1: Slack Notifications
Get a formatted message in your Slack channel every time new leads are surfaced. Each notification includes the lead's name, title, company, score, HC signals, and direct links to their email and LinkedIn.
Step 1: Create a Slack Incoming Webhook
Go to api.slack.com/messaging/webhooks and create an incoming webhook for the channel where you want lead notifications. Copy the webhook URL (it looks like https://hooks.slack.com/services/T.../B.../xxx).
Step 2: Paste the URL in Your SDR Settings
Go to Solution Dashboard → Team → SDR Agent → Edit ICP. Scroll to the Lead Delivery section and paste your Slack Webhook URL. Click Save.
Step 3: Done
The next time the agent runs, new leads will appear in your Slack channel automatically.
Option 2: Webhook (Zapier, Make, n8n, or Custom)
Send leads as a JSON payload to any URL. This works with Zapier, Make (Integromat), n8n, or any custom endpoint. From there, you can route leads to Google Sheets, HubSpot, Clay, EmailBison, or any tool in your stack.
Step 1: Get Your Webhook URL
- Zapier: Create a new Zap with "Webhooks by Zapier" as the trigger → "Catch Hook" → Copy the webhook URL
- Make: Create a new scenario with "Webhooks" → "Custom webhook" → Copy the URL
- Custom: Use any URL that accepts POST requests with JSON body
Step 2: Paste the URL in Your SDR Settings
Go to Solution Dashboard → Team → SDR Agent → Edit ICP. Scroll to Lead Delivery and paste your webhook URL. Click Save.
Step 3: Map the Payload
The webhook sends a JSON payload with this structure:
{
"event": "leads.surfaced",
"solutionId": "your-solution-id",
"leads": [
{
"name": "Jane Smith",
"title": "VP of Marketing",
"company": "PepsiCo",
"domain": "pepsico.com",
"email": "jane@pepsico.com",
"linkedin": "https://linkedin.com/in/janesmith",
"score": 87,
"signals": "viewed_profile(3x), saved_in_category",
"surfacedAt": "2026-04-08T12:00:00Z"
}
]
}
In Zapier/Make, map these fields to the appropriate columns in your Google Sheet, HubSpot contact properties, or Clay enrichment workflow.
Option 3: API Endpoint (Pull-Based)
For full control, use the leads API to pull leads on your own schedule. This is ideal for custom scripts, cron jobs, or your assistant pulling leads daily.
Endpoint: GET /api/solutions/{solutionId}/leads
Authentication: Requires a logged-in session (cookie-based auth).
Parameters:
format=json(default) orformat=csvlimit=50(default 50, max 200)offset=0for paginationsince=2026-04-01T00:00:00Z— only return leads surfaced after this date (for incremental pulls)
Example:
GET /api/solutions/your-id/leads?format=csv&since=2026-04-01
Returns a CSV with columns: Name, Title, Company, Domain, Email, LinkedIn, Score, Signals, SurfacedAt.
Option 4: Manual CSV Export
From the Leads tab, click the Export button to download all scored leads as a CSV file. The CSV includes a Signals column with HC behavioral data for each lead.
This is the simplest option but requires you to remember to export regularly. We recommend one of the automated options above for consistent lead flow.
Recommended Workflows
| Your Stack | Best Setup |
|---|---|
| Clay + EmailBison | Webhook → Zapier/Make → Google Sheet → Clay API → EmailBison |
| HubSpot | Webhook → Zapier → Create HubSpot Contact with HC signal properties |
| HeyReach (LinkedIn) | Webhook → Zapier → Google Sheet → HeyReach campaign import |
| Slack-first team | Slack webhook — leads appear in your channel, team acts on them directly |
| Custom CRM | API endpoint — pull leads on a schedule with your own script |
