call_analyzed for structured intake
Post-call analysis is where summaries and custom fields live. That is the usual trigger for CRM writes so you are not storing empty analysis objects from call_ended.
Retell webhook integrations
A Retell webhook is how the voice agent stops being a phone conversation and starts being work in your systems. Wrk Less sets up the endpoint, verifies the signature, and routes each event into CRM, calendars, alerts, and the automations your operations team already trusts.
Webhook setup
Retell documents account-level and agent-level webhook URLs and events including call_started, call_ended, call_analyzed, transcript updates, and transfer states. Wrk Less picks the events that match your operating rules—not every event by default.
Post-call analysis is where summaries and custom fields live. That is the usual trigger for CRM writes so you are not storing empty analysis objects from call_ended.
Deliveries include X-Retell-Signature. Wrk Less verifies authenticity, then maps a stable payload into n8n or your destination. Unsigned traffic never creates a lead.
Retries happen. Integrations key off call ID so a duplicate webhook does not create a second contact or a second appointment.
What we connect
Create or update the person, attach the transcript summary, tag the source as the voice agent, and open the next task for whoever owns follow-up. No retyping from a dashboard.
If the agent collected a preferred window, the workflow checks real availability, books when your rules allow, or creates a “needs scheduling” task when the slot is gone. Humans still own exceptions.
SMS, email, or a channel ping when a call is urgent, a transfer fails, or a high-intent seller is waiting. Quiet hours apply so your phone is not buzzing for every after-hours FAQ.
Onboarding packets, document requests, estimate drafts, or internal tickets can fire from the same payload. Deterministic steps do the filing; AI only fills fields you asked it to extract.
How this differs from agent setup
Retell AI voice agent setup covers greetings, tools, phone routing, and boundaries. This page is the integration layer: webhook URL, event choice, field mapping, and what your team sees two minutes after the caller hangs up.
If you searched “Retell webhook,” you are usually trying to get data out of Retell and into the rest of the business. That is the job Wrk Less takes.
FAQ
A Retell webhook is an HTTP POST Retell sends to a URL you control when something happens on a call—such as the call starting, ending, or finishing post-call analysis. Wrk Less uses that payload to update your CRM, book or log appointments, notify staff, and run custom automation.
Use call_analyzed when you need the summary, sentiment, success flag, or custom extracted fields. call_ended does not include call_analysis. Wrk Less wires the event that matches the job: live alerts on call_started or transfer events, structured records on call_analyzed.
Yes. The webhook is the handoff. From there Wrk Less maps fields into your CRM, calendar, or job board, creates or updates the contact, and only books time when your rules and availability allow it.
Retell signs deliveries with an X-Retell-Signature header. Wrk Less verifies that signature, uses the raw request body, and only then writes to downstream systems. Endpoints are not left open as anonymous public forms.
No. n8n is a common destination because Wrk Less already operates workflow automation there, but the same Retell webhook can post to another automation tool or a custom endpoint if that is what your stack needs.
Sources
Get the payload into the tools you already use