Leadialer + REsimpli Integration
REsimpli doesn't offer a public API for outside tools to write to directly, so the reliable path is its official Zapier app. Leadialer's signed webhooks feed a Zap that creates or updates the lead in REsimpli; a second Zap can push new REsimpli leads into Leadialer for dialing.
What the REsimpli integration does
REsimpli is built for exactly the investors Leadialer calls for — so the two belong together even though REsimpli doesn't expose a public write API. The supported bridge is REsimpli's official Zapier app: Leadialer fires a signed webhook the moment a call completes, an appointment is booked, a lead turns warm, or someone opts out, and your Zap writes that result into REsimpli.
Flowing the other way, REsimpli's new-lead trigger in Zapier can POST each fresh seller lead straight into Leadialer's REST API, where the AI voice agent starts working it on your next dialing session. Every webhook is HMAC-signed and retried up to three times, so a briefly-down Zap doesn't lose events.
What syncs
- Events out via signed webhooks: calls, bookings, warm leads, opt-outs
- Leads in via the Leadialer REST API
Setup
- 1In Zapier, create a Zap starting with "Webhooks by Zapier → Catch Hook" and copy the hook URL.
- 2In Leadialer (Profile → CRM Integrations → Outgoing Webhooks), add that URL and pick the events you want.
- 3Add a REsimpli action step in the Zap to create/update the lead.
- 4Leads in: add a Zap from REsimpli's new-lead trigger that POSTs to Leadialer's /api/v1/leads endpoint with an API key.
Field mappings
- Events out — each webhook carries { event, timestamp, data } with the lead's name and the event specifics (outcome + score + summary, or booking date/time), which you map onto REsimpli fields inside the Zap
- Leads in — POST /api/v1/leads accepts phone (required), firstName, lastName, phone2, phone3, email, propertyAddress, propertyCity, propertyState, propertyZip, notes, and an optional campaignId. Duplicates and Do Not Call numbers are rejected automatically.
Events Leadialer sends
call.completedFires when a call finishes — includes the outcome, the lead's score, and the AI-written call summary.
appointment.bookedFires when Alex books or reschedules an appointment — includes the date and time in your timezone and how it was booked (call or text).
lead.warmFires when a lead's score crosses the warm threshold — includes the score and whether it came from a call or a text thread.
lead.opted_outFires when a lead texts STOP — so you can suppress them in your other tools too.
Frequently asked questions
Why does REsimpli need Zapier when other CRMs don't?
REsimpli doesn't publish an API that outside tools can write to directly. Its official Zapier app is the supported integration surface, so that's the path Leadialer documents.
Is the connection real-time?
Leadialer fires the webhook the moment the event happens and retries up to three times. How quickly the Zap runs after that depends on your Zapier plan's polling and task schedule.
Does Leadialer charge extra for this?
No — webhooks and the REST API are included. Your only third-party cost is whatever your Zapier plan charges for tasks.
How do I verify the webhooks are really from Leadialer?
Every delivery is signed with an HMAC-SHA256 X-Leadialer-Signature header. With Zapier as the receiver you can generally trust the hook URL's obscurity, but the signature is there if you build your own endpoint.