Chatbot With Webhook Integration: What a Webhook Actually Does, the Two LiveChatBot Events, and Copy-Ready Messages for Your Developer (Free Copy Lines)

Chatbot with webhook integration means the chat tool tells another system the moment something happens, so nobody has to copy and paste. LiveChatBot sends two webhook events, ticket.created and ticket.solved. This guide explains the idea without jargon, shows what you can build, lists what is missing, and gives you copy-ready lines to send a developer or paste into a Zapier setup.

2webhook events: ticket.created, ticket.solved
3routes: webhooks, Zapier, REST API
₹0to start, 2 websites
0per-seat charges

⚡ In short

  • A webhook is a message one tool sends to a web address when an event happens.
  • LiveChatBot sends ticket.created and ticket.solved. There are no chat-level events.
  • You can catch them in Zapier without code, or in your own server with a developer.
  • Test with a throwaway address first, and never put secrets in a public link.
Chatbot with webhook integration in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

The idea

A chatbot with webhook integration in plain words: the doorbell, not the postman

Most integrations work by polling: your system asks the chat tool, again and again, “anything new?”. A webhook flips this. The chat tool rings a doorbell, a web address on your side, the instant something happens.

What travels

A small packet of data describing the event: that a ticket was created, and details about it. Your system reads it and decides what to do, such as adding a row to a sheet or sending an email.

Why it matters for a small business

It saves manual copying and removes the delay. A ticket created at midnight can be in your sheet, your inbox and your task list before you wake up.

What it is not

A webhook does not let outside systems change your chat. It only sends information out. For reading and writing data, a developer uses the REST API.

What LiveChatBot sends

The two events LiveChatBot sends by webhook

LiveChatBot supports two webhook events.

  • ticket.created. A new ticket exists, perhaps from an offline message or a chat you turned into a ticket.
  • ticket.solved. A ticket has been marked solved.

That is the full list. There is no webhook for every chat message, no event when a visitor arrives and no event for a lead form. For those, a developer can use the JS API on your site, where window.LiveChatBot offers open, close, show, hide, setVisitor, sendMessage, pageView and on.

Plan around this. Tickets are where your follow-up work lives anyway: an offline message becomes a ticket with an owner, and a customer ticket page needs no login. See how to turn a chat into a support ticket.

Free tool

Copy-ready lines for your developer and your Zap

Pick a tab, copy a line and paste it into an email or a task. Fill in the square-bracket parts yourself.

Please set up a receiving URL that accepts a POST request and replies with a success status quickly.
Please log every webhook we receive for the first week, with the time, so we can check nothing is missed.
Please add a way to check that a request really came from LiveChatBot before acting on it, and tell me what you can verify.
Please handle the same ticket arriving twice without creating a duplicate row.
Trigger: Webhooks, catch hook. Copy the custom URL it gives you.
Paste that URL into LiveChatBot for ticket.created.
Action: send an email or add a row to a Google Sheet with the ticket details.
Test: create a ticket yourself and confirm the Zap ran once.
Test 1: create a ticket from an offline message and note the time.
Test 2: mark it solved and check ticket.solved arrives.
Test 3: turn the receiver off for ten minutes and see what happens to events sent meanwhile.
Test 4: send two tickets within a minute and confirm both arrive.

Uses

Five jobs a webhook can do for a small team

Each of these works with the two events and a no-code tool.

  1. Email alert for new tickets to a shared mailbox, as covered in our guide to a free chatbot with email notifications.
  2. A row in Google Sheets per ticket, giving you a simple log and chart.
  3. A task in your to-do app, so every ticket has a visible next action.
  4. A message to a team group through a tool Zapier supports. LiveChatBot has no native Slack or Teams app.
  5. A thank-you step when a ticket is solved, such as a follow-up email you write yourself.

The step-by-step is in how to connect live chat to Zapier. Developers will find more routes on the integrations page.

Safe testing

Test a webhook without risking real data

Webhooks send real information, so test with care.

Use a throwaway receiver first

Free request-catcher pages show you every incoming message. Use one with a test ticket, never with a customer’s real details.

Keep the address private

Treat the receiving URL like a password. Anyone who knows it can send fake events to it.

Check retries and duplicates

Ask what happens if your receiver is down, and whether the same event might arrive twice. Build your receiver so a repeat does no harm.

Limit what you act on

Do not trigger refunds, deletions or other irreversible actions straight from an incoming event without a human check.

Worked example

An illustrative example: a bakery that logs every ticket

This is a made-up example to show the shape of a setup, not a real customer.

A small bakery takes custom cake enquiries through its website chat. After closing time, the away form collects a phone number and the message becomes a ticket.

  1. The ticket.created event goes to a Zapier webhook.
  2. Zapier adds a row to a shared sheet with the date, name, phone and message.
  3. A second step emails the baker a short summary.
  4. In the morning the baker calls, marks the ticket solved, and ticket.solved adds a “done” mark in the sheet.

Total cost on the LiveChatBot side: nothing beyond the free plan. After a month, the sheet shows how many enquiries arrive after hours and which days are busy, which helps decide whether to extend opening hours.

Before you build

Settle these before any chatbot with webhook integration goes live

A short planning pass avoids rework.

Who owns the receiver?

Someone has to look at it when it breaks. Name them.

What happens when it fails?

If Zapier is paused or your server is down, are events lost? Decide whether a daily manual check of the ticket list is the backup.

How much will it cost?

Zapier has task limits on its free tier. Count your monthly tickets and multiply by the number of steps in the Zap.

What data goes where?

Do not copy sensitive details into a shared sheet that many people can open. India’s DPDP Act 2023 is a good reason to be careful with personal data.

Limits

What a chatbot with webhook integration here does not cover

To avoid surprises, here is what is not part of LiveChatBot.

  • No native apps for HubSpot, Salesforce, Zoho, Slack or similar tools. You connect them through Zapier, webhooks or the API.
  • No webhook for every message or visitor event.
  • No WhatsApp inbox, only a WhatsApp button card.
  • No iOS team app, but an Android one.
  • “Powered by LiveChatBot” stays on all plans.

Developer documentation is not published on livechatbot.in yet, so ask our team for it. Meanwhile, pricing is simple: the free plan includes webhooks, and there are no per-seat charges.

Frequently asked questions

What events does LiveChatBot send by webhook?

ticket.created and ticket.solved.

Do I need a developer for a chatbot with webhook integration?

Not always. Zapier can catch a webhook and send an email or add a sheet row without code. A developer is needed for your own server.

Is there a webhook for each chat message?

No. Only the two ticket events are available, and a developer can use the JS API on the page for other signals.

Can a webhook change anything in my chat?

No. Webhooks send information out. To read or write data, a developer uses the REST API.

Does the free plan include webhooks?

Yes, and there are no per-seat charges.

Keep reading

Related guides

📘

Chatbot With SMS Notifications: Is a Text Really the Best Alert for Your Team? Compare SMS, Phone Push, Email and WhatsApp (Free Alert Scorecard)

Read the guide →

🧭

Chatbot With REST API: Five Jobs a REST API Can Do for Your Business, and a Quick Quiz to Decide If You Need It Yet (Free Route Quiz)

Read the guide →

🛠️

Chatbot With Email Notifications: Why the Alert Email Never Arrives, the Terms Behind It, and How to Test Delivery (Free Email Jargon Glossary)

Read the guide →

More to read

More guides on this topic

📘

Add Chatbot to WordPress and Then Tell Your Team: Rollout Messages for Staff, Customers and Your Own Site (Free Copy-Ready Lines)

Read the guide →

Send ticket events where your team already works

Free plan for two websites with webhooks, Zapier and a REST API. Start free on livechatbot.in.