a retune bot sends each lead out as a webhook. if the other end doesn't answer, it waits and tries again for a few minutes, and it shows you every try.
there's no hubspot or pipedrive button in retune. it's a webhook: retune posts the lead to a url, and something on the other side puts it in your crm.
that something is usually zapier, make or n8n. each has a crm step, and the webhooks tab has setup guides for all three. if you run your own server, you can point the webhook there instead.
most crm apis want a key in a header, and retune can't add your own headers to a request. so the key lives in zapier, make, n8n or your server, not in retune.
if you want a crm button you click once and never think about, this isn't it. if you're fine with one zap or one flow in the middle, it works.
in the video, the second address is a stand-in crm set up to fail. it answers with an error twice. retune waits and tries again. the third try works.
if the other end doesn't answer within ten seconds, or answers with a server error, retune tries again. it tries five times, spread over a bit more than ten minutes.
if the crm is down longer than that, the lead sits in the log as "gave up 5/5" until you replay it. check the tab now and then.
every delivery is a stored row, so a restart doesn't lose the ones waiting. click a row to see each attempt, what came back and the exact data that went out. once the crm is back, hit replay and the same lead goes out again.
a wrong address, the kind that comes back "not found", isn't retried. it's marked failed, so you can fix the address and replay it.
webhooks aren't switched on for new accounts by themselves. sign up, then email me and say you want webhooks on your bot. once they're on, a webhooks tab shows up on the bot.
you add an endpoint with the url from zapier, make, n8n or your server. you tick lead captured, send a test event, and watch it show up as delivered. the step-by-step for zapier is in send chatbot leads to zapier, and the n8n one is in chatbot webhook to n8n.
the lead goes out once per chat, when the visitor answers the bot's last question. it carries their answers, the conversation up to the last 20 messages and a link to the chat in retune. how the conversation shows in the crm record depends on your zap or flow. a notes field is the usual place to map it.
a visitor who leaves before the last question doesn't send a lead. their chat is still in retune, but nothing goes to the crm.
each endpoint shows how many deliveries went through and how many failed in the last 24 hours, so it's worth a look each day.
it only sends. it doesn't read anything back from the crm, so a change you make there doesn't show up in retune.
if you replay a lead that already got through, the crm may get it twice. every event has an id that stays the same on replays, so a flow can drop the copy if you set it up that way.
the tab lists the last 50 deliveries.
it fits a small business that already has a crm and one person who can set up a zap or a flow. if nobody on your side wants to touch zapier, a native crm app will suit you better.
if leads pile up faster than you can call them, chatbot lead qualification scores each one before it goes anywhere.
if something here doesn't fit your crm, tell me which one you use and i'll look at it.
olive