Send Toran leads into Reapit

Who this is for

UK letting agents and estate agents who run Reapit CRM (AgencyCloud) and already receive portal leads in Internet Registrations.

What you need

• A Toran Pro or Business plan. The outbound webhook is a paid-plan feature (see the plan table).
• Reapit internet registrations already set up for your agency, plus Reapit's confirmation that emails from your own website are imported. Reapit sets up the mailbox and forwarding rules and tests them with you.
• A paid Zapier plan. Webhooks by Zapier, the trigger this recipe uses, is not on Zapier's Free plan.
• A Gmail or Microsoft 365 mailbox connected to Zapier, to send the lead email from.

Setup, step by step

1. 1. Check with Reapit first. Ask Reapit support which address your website's lead emails should go to, which Source name to use, and whether emails sent from your mailbox will be picked up. Reapit ignores emails that do not match one of its templates, so this quick check saves a lot of guessing.

2. 2. Create a Catch Hook and connect Toran. In Zapier: New Zap → trigger Webhooks by Zapier → event Catch Hook; copy the URL. In Toran: your widget → Design → Chat & alerts → Outbound webhook, paste, save. Optional: set Send to webhook to Warm + Hot so cold enquiries stay out of Reapit.

3. 3. Send a test lead. Click Send test webhook in Toran, then test the trigger in Zapier. You should see "Test Lead" with event lead.test, which Zapier keeps as sample data.

4. 4. Filter. Add Filter by Zapier with two rules: only continue if event exactly matches lead.captured AND email exists. Reapit's format needs an email address; phone-only leads still reach you through Toran's alerts.

5. 5. Send the lead email. Add your mailbox's Send Email action (Gmail or Microsoft Outlook). To: the address Reapit gave you. Subject: anything, for example Website enquiry. Body type: plain text. Body, one field per line, with a space after each colon (each item in square brackets is a field you insert from the Toran trigger):

   Name: [name]
   Telephone: [phone]
   E-mail: [email]
   Source: Company Website
   Enquiry Type: Lettings
   Message: [ai_summary] Visitor wrote: [metadata notes] Page: [source] Tier: [tier] Toran lead: [lead_id]

   Keep the whole message on one line. Reapit reads the email line by line, so a line break inside the AI summary could cut it short. Leave out the Marketing Consent Given line: Toran does not ask visitors for marketing consent, and Reapit's format lets you leave the line out.

6. 6. Turn the Zap on. New registrations are collected on Reapit's schedule, so allow a little time before you go looking for one.

Field mapping

Line names follow Reapit's published default format. Address, Mobile, and Property Ref lines are optional in that format; Toran has no address or property reference to send.

Test it with a sample lead

The dashboard test is stopped by your filter, as it should be. To test end to end, start a chat on your own website and leave a name and an email you control. Check Internet Registrations for it, then reject it so it never becomes an applicant. If nothing shows up, check the email in your mailbox's Sent folder against the format above and send it to Reapit support: it is the same check they run for any missing website lead.

This is what a real lead looks like when it reaches Zapier:

{
  "event": "lead.captured",
  "lead_id": "8d2b5f10-7c3e-4a9b-b6e1-2f4a9c0d7e33",
  "widget_id": "c41f8a26-9e0b-4d17-a3c5-6b8e2d1f0a94",
  "name": "Priya Shah",
  "email": "priya.shah@example.co.uk",
  "phone": "+447700900123",
  "score": 74,
  "tier": "warm",
  "source": "https://example-lettings.co.uk/to-rent/two-bed-flat-islington",
  "ai_summary": "Looking for a two-bed flat in Islington from early November, working professional with a reference from her current landlord. Wants a viewing this week.",
  "timestamp": "2026-10-13T09:41:27.000Z",
  "metadata": {
    "notes": "Is the Islington flat still available? Can I view on Thursday?",
    "utm_source": "rightmove",
    "utm_medium": "referral",
    "utm_campaign": null,
    "company_name": null
  }
}

What does not carry over

• The full chat transcript. Toran sends a short AI summary of the conversation, not the conversation itself. The full chat stays in your Toran dashboard.
• Applicant requirements as fields. Bedrooms, budget, areas, and move date are not structured fields in the webhook. When the visitor mentioned them, they are in the AI summary for your negotiator to enter on the applicant.
• Property reference and address. Toran sends the page the visitor was on, not a Reapit property reference.
• Marketing consent. Toran does not collect it, so the registration arrives as "not asked".
• A direct applicant record. Every lead goes through Internet Registrations for your team to accept, merge, or reject.

About the signature

Every request from Toran carries an X-Toran-Signature header. Zapier's Catch Hook does not check it. In this recipe the protection is the Catch Hook URL itself, which is long and impossible to guess: keep it private, and if it ever leaks, create a new Catch Hook and paste the new URL into Toran. If you need every lead verified, point Toran at your own endpoint instead and check the signature there, as described in the webhook reference.

Frequently asked questions