Toran feeds your WhatsApp stack
AiSensy, WATI, and every WhatsApp Business API tool start working after someone opens a chat. Most of your website visitors never do. Toran sits upstream — on the site — and catches the visitor who would have left, scores them, and hands them to whatever runs your WhatsApp stack: a bot, a broadcast list, a CRM, or a human.
The honest version
Toran doesn't broadcast, and it doesn't replace a WhatsApp Business API platform if that's what you actually need. What it does: capture and score the website visitor those tools structurally can't see, then feed that lead — with score, source, and context — into the WhatsApp stack you already run. Works with. Feeds. Never replaces.
How it works
1. Toran captures
The widget engages the visitor on your site — before they've decided whether to message anyone on WhatsApp at all.
2. Toran scores
AI + behavioral scoring rates the lead hot, warm, or info, and writes a short summary of what they were asking about.
3. Toran feeds it out
A signed webhook fires on every captured lead — to your team's WhatsApp, or into AiSensy, WATI, or any CRM via Zapier, Make, or n8n.
The recipe: Toran → Zapier → AiSensy
This is the concrete, no-code path most WABA-tool users want. The same recipe works for WATI, Interakt, or any CRM — swap the destination step.
1. Create a Catch Hook in Zapier. New Zap → trigger Webhooks by Zapier → event Catch Hook. Copy the URL Zapier gives you.
2. Paste it into Toran. Dashboard → your widget →Design → Chat & alerts → Outbound webhook → save, then click Send test webhook to confirm delivery.
3. Add AiSensy as the action. AiSensy lists both Zapier and Pabbly Connect on its own integrations page — add its "add/update contact" action and map
tierto the audience list so hot leads land where your broadcast and bot can reach them.4. Map the fields.
name,email,phoneto the contact;scoreandtierto a priority field or tag;sourceto the page they were on;aiSummaryto a note so whoever (or whatever bot) picks up the conversation starts warm instead of cold.5. Filter out test sends. Real leads arrive as
event = lead.captured; the dashboard's test button sendsevent = lead.test. Add a Filter step so test data never reaches your live audience.
Prefer WATI, Interakt, HubSpot, or something else? Same five steps, different destination action — see the full Zapier & Make recipe for the complete payload reference, the Make/n8n variant, and signature verification.
What Toran sends
Every captured lead arrives as one signed JSON payload. The fields that matter for feeding a WhatsApp stack:
| Field | What it's for |
|---|---|
| name / email / phone | Visitor-supplied contact details. At least one of email/phone is always present. |
| score | AI lead score, 0–100 — the classifier's read on how likely this visitor is worth a fast reply. |
| tier | hot, warm, or info — the field most destinations filter on. |
| source | The page URL the lead came from (source_page_url), so you know what they were looking at. |
| aiSummary | A short, owner-visible digest of what the visitor was asking about — never the raw chat transcript. |
| metadata | utm_source / utm_medium / utm_campaign and other context, so attribution survives the handoff. |
Full field types, request headers, and signature verification: see the payload reference.
Where the lead can go
AiSensy
Feed a scored website lead into your AiSensy audience so its bot and broadcast lists work the contact warm.
WATI
Push captured leads into WATI's workflow so your shared inbox starts with the score and page context already attached.
Interakt
Land the scored lead in Interakt's contact list before your chatbot or inbox ever sees the conversation.
HubSpot, Zoho, or any CRM
The webhook is a plain signed JSON POST. Anything Zapier, Make, or n8n can reach — which is most CRMs — can receive Toran leads.
Zapier alone lists 5,000+ apps in its directory — if your CRM exists, the webhook can almost certainly reach it.
Complement, not replacement — said plainly
If AiSensy, WATI, or Interakt already run your broadcast campaigns and your in-WhatsApp bot, Toran isn't asking you to switch. It's the layer before all of that: the website visitor who never opens WhatsApp, captured and scored, then handed to the stack you already trust. If the only job you need done is catching website leads, Toran can also run alone — no WABA account required.
Frequently asked questions
Does Toran replace AiSensy, WATI, or my CRM?
No. Toran runs upstream of all of them — on your website, before a visitor ever opens WhatsApp. It captures and scores that visitor, then feeds the lead into whatever runs your WhatsApp stack: AiSensy or WATI's bot and broadcast tools, your CRM, or a human on your team. Complements your stack; it doesn't replace it.
What's the actual mechanism — is this a real integration or just a link?
It's a real, signed webhook. Toran POSTs every captured lead (name, email, phone, score, tier, source page, AI summary, and UTM metadata) to your URL the moment it's captured, HMAC-signed so you can verify it came from Toran. Point it at a Zapier Catch Hook, Make webhook, or n8n node and it lands wherever you configure — no code required for the no-code path.
Which Toran plans include the webhook?
Webhook egress is included on Pro (10 agents) and Business. See the full field reference and setup steps on the Zapier & Make recipe page.
Do I need to be technical to set this up?
No. The no-code path is Toran → Zapier (or Make, or Pabbly Connect) → your CRM: paste a webhook URL into Toran's dashboard, click "Send test webhook," and map fields in Zapier. See the step-by-step recipe for the full walkthrough.
Is there a first-party AiSensy or WATI connector?
Not yet — today's path is the generic signed webhook through Zapier or Pabbly Connect, both of which AiSensy and WATI already support on their side. That covers the job now; a first-party destination preset is a possible later build, not something you need to wait for.
Catch the visitor your stack never sees.
Free, no time limit, no credit card. Add the webhook when you're ready to feed it into AiSensy, WATI, or your CRM.