How to automatically deliver scored leads to Slack, Zapier, Make, Google Sheets, HubSpot, or any webhook.
The AI SDR Agent can automatically send scored leads to your existing tools, with no manual CSV exports. Every time the agent surfaces new leads, they're delivered to whatever channels you configure.
You have four options, from simplest to most flexible:
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.
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).
Open your Pipeline page (https://humancloud.com/solution-dashboard/your-profile/leads), click Manage Integrations, open the Slack card, paste your webhook URL and click Save.
The next time the agent runs, new leads will appear in your Slack channel automatically.
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.
Open your Pipeline page, click Manage Integrations, open the Webhook card, paste your URL and click Save. The URL must start with https:// and be reachable on the public internet; we check it when you save and again before every send, and we don't follow redirects.
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.
Every webhook request is signed so you can tell it came from Human Cloud. Each request carries these headers:
X-HC-Event: leads.surfaced, or leads.test when you click TestX-HC-Delivery-Id: unique per request; use it to ignore duplicatesX-HC-Timestamp: when we sent it, in Unix secondsX-HC-Signature: sha256= followed by the hex HMAC-SHA256 of <timestamp>.<raw request body>, keyed with your signing secretTo get your signing secret, open the Webhook card in Manage Integrations and click Show signing secret. It starts with whsec_. Only people who can edit your profile can see it. To check a request in Node.js:
const crypto = require('crypto');
function isFromHumanCloud(rawBody, headers, secret) {
const ts = headers['x-hc-timestamp'];
if (Math.abs(Date.now() / 1000 - Number(ts)) > 300) return false; // older than 5 minutes
const expected = 'sha256=' + crypto.createHmac('sha256', secret).update(ts + '.' + rawBody).digest('hex');
const got = headers['x-hc-signature'] || '';
return got.length === expected.length && crypto.timingSafeEqual(Buffer.from(got), Buffer.from(expected));
}
Compute the signature over the raw body exactly as received, before parsing the JSON. Zapier and Make don't need this step.
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: an API key in the header Authorization: Bearer your-key. Create one in Manage Integrations, in the API Endpoint card. See Leads API and API Keys for the full reference.
Parameters:
format=json (default) or format=csvlimit=50 (default 50, max 200)offset=0 for paginationsince=2026-04-01T00:00:00Z: only leads surfaced after this time (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.
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.
| 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 and your team acts on them directly |
| Custom CRM | API endpoint: pull leads on a schedule with your own script |