Send AI Twin leads to your CRM (HubSpot, Salesforce, any)

Push every qualified lead into your CRM the moment it happens, using the signed lead webhook — directly or through Zapier, Make or n8n.

Updated August 3, 2026 7 min read

Every lead your twin captures can be pushed into your CRM the moment it happens. Today this runs through a signed webhook, which works with any CRM — including HubSpot, Salesforce, Pipedrive, Attio or an internal system — either directly or through an automation tool.

Native one-click apps for HubSpot and Salesforce are on the roadmap and not available yet. What's described below ships today. You can always check the live status of any capability at realitytwin.io/roadmap.

Set up the webhook

  1. Settings → Integrations → Webhook.
  2. Paste the URL that should receive leads (your endpoint, or a Zapier/Make/n8n catch hook).
  3. Save. Reality Twin generates a signing secret — copy it.
  4. Use Send test to fire a sample payload and confirm your endpoint answers with 2xx.

What we send

Reality Twin POSTs JSON for each new lead. This is the actual payload — no enrichment, no invented fields:

{
  "name": "Jane Visitor",
  "email": "jane@acme.com",
  "question": "Do you deliver to Austria?",
  "intent_score": 74,
  "lead_score": 94,
  "status": "hot",
  "source": "twin_chat"
}
  • name / email — what the visitor actually gave you.
  • question — the message that triggered the capture.
  • intent_score and lead_score — 0–100, how strong the buying signal was.
  • status — hot or warm, derived from intent.
  • source — twin_chat, contact_form, and so on.

Verify the signature

Every request carries an HMAC signature generated with your secret, so your endpoint can prove the call really came from us. Reject anything that doesn't match — otherwise anyone who learns your URL can inject leads.

Reaching HubSpot or Salesforce today

Point the webhook at a Zapier, Make or n8n catch hook and map the fields onto "Create/Update Contact" in your CRM. Ten minutes of setup, no code. If you have engineering capacity, posting to the CRM's own API from a small handler gives you full control over field mapping and deduplication.

Deduplication is handled by your CRM, not by us — both HubSpot and Salesforce match on email out of the box.

Best practices

  • Auto-assign Reality Twin leads to a specific queue or owner so they don't sit unclaimed.
  • Store lead_score as a numeric field — it's what makes the source reportable.
  • Tag the source so you can prove where the pipeline came from.
  • Answer fast: leads contacted within the hour convert best.

Frequently asked questions

Can I send low-score leads to CRM too?

Yes — set the threshold to 0. Most teams don't, because it clutters the pipeline.

Is the sync one-way or two-way?

One-way: Reality Twin → your CRM. Nothing is read back out of your CRM.

What if my endpoint is down?

The lead is still captured in Reality Twin — you'll find it under Leads and in the CRM view, so nothing is lost while you fix the endpoint.

Did this article solve your problem?

If not, email us — a human on the founding team replies, usually within a business day.