a retune bot can be one more trigger in that flow. it posts a signed event to your webhook node when a lead comes in, when someone takes over a chat, and when a chat ends.
in the video a small receiver on a laptop stands in for n8n, so you can see each request and its signature check.
there are five events. you tick the ones each endpoint should get.
data.fields.each body has the bot, a link to the chat and the conversation up to the last 20 messages. the x-retune-event-id header stays the same on retries and replays, so you can drop duplicates on it.
every request is signed, and the signature comes in the x-retune-signature header. the your server tab in the webhooks docs has a node.js and a python snippet to check it. either one fits in a code node.
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.
make works the same way. add the webhooks module with a custom webhook, click run once, then send the test event from retune.
if your n8n 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, then marks it "gave up 5/5". a "not found" or other client error isn't retried.
the deliveries log shows every attempt with the response and the exact body. hit replay and the same event goes out again, with the same event id and a replay header. deliveries are stored, so a restart of retune doesn't lose the queue.
the lead, the handover and the finished chat are triggers. the crm step, the owner's message and the monthly sheet are the flow you already build.
if you're just starting to sell bots to local businesses, selling chatbots to local businesses is the letter for that part.
a chat ends when it's archived or the visitor starts over. it doesn't end on its own when the chat goes quiet. if a flow needs that, run it on a schedule in n8n instead.
you can't add your own headers to an endpoint. if a client's api needs a key, put it in n8n and let the flow call the api.
there's no summary in the payload. if you want one, add an ai step to your flow.
the tab lists the last 50 deliveries.
an endpoint can be any address your retune can reach, so it fits a flow you already run. it won't fit a client who has no flow and wants the leads to just appear somewhere.
if a client asks for something the bot doesn't do, email me and i'll build it. i'll be wrong sometimes, so look before you ship it to a client. the same bot can also answer agents like claude code over mcp, if a client asks for that.
if a client only wants leads in a sheet, send chatbot leads to zapier is the short version. for a crm, read connect your website chatbot to your crm.
olive