Chatbot With Make Integration: Build a Webhook Scenario From Chat to Sheet, Mail or Team Message, Step by Step (Free Build Timeline)
Chatbot with Make integration usually means one thing in practice: your chat tool sends an event to a web address, and a Make scenario picks it up and does the follow-up work. LiveChatBot has no native Make app, but it does have webhooks, a REST API and Zapier, which is enough to build a reliable scenario. This guide walks through the build in six steps, with the honest limits.
⚡ In short
- LiveChatBot does not have a native Make module. The route is webhooks into a Make custom webhook.
- Webhooks fire on ticket.created and ticket.solved, so the scenario starts from a ticket, not from every chat message.
- Build the scenario first, copy its web address into LiveChatBot, then send a test ticket.
- Make has its own plans and limits, so check them before you rely on it.

The idea
What a chatbot with Make integration really means
When a vendor says “works with Make”, it can mean three different things. A ready-made module you pick from a list. A webhook you point at Make yourself. Or only a vague claim that “it connects to anything”.
LiveChatBot belongs in the second group. It has no module in Make’s app list. What it offers is a plain, documented way to push events out: when a ticket is created or solved, LiveChatBot calls a web address you choose and sends the ticket details.
That is a good fit for Make, because Make’s custom webhook trigger exists to receive exactly that. Your scenario wakes up, reads the fields, and then does whatever you build: add a row, send an email, post a team message, create a task.
If you want the fuller picture of every connection route, our integrations page lists them, and the guide on chatbot integration for CRMs shows the same routes aimed at a contact list.
Fit check
When Make is the right tool, and when it is not
Make is strongest when your follow-up has several steps and a few branches. Examples: a new ticket creates a row, then emails the owner, then tags the contact, and only for tickets that mention a product you sell.
Good fits
- Follow-ups with two or more steps in sequence.
- Routing by a field, such as sending sales questions to one person and support to another.
- Checking a condition before acting, such as skipping tickets from your own team.
Poor fits
- A single action, like one row in a sheet. A two-step Zap or a direct approach is quicker. See our Zapier walkthrough.
- Anything that must react to every chat message. The webhooks cover ticket events only.
- Work that needs live lookups inside the chat reply. That needs the REST API and your own code.
Choose the simplest tool that does the job. Complexity you do not need is cost you pay later.
Try it
The six-step build timeline
Follow the steps in order. Build the receiving end first, so there is somewhere for the event to land.
Start a new scenario and add a custom webhook as the first module. Make shows you a web address. Copy it.
Paste that address as the webhook target for the ticket events. Ask our team for developer documentation if you need the exact setup details.
Create a test ticket from a chat or the away form. Make receives it and learns the field names.
Map the fields you want, such as name, email and message, into a sheet row, an email or a team message.
Add one condition so test or internal tickets do not trigger real actions. A simple rule on the email field is enough.
Turn the scenario on, send one more ticket and check every output. Then set a monthly reminder to re-test.
Fields
Which details you can route with a chatbot with Make integration
The webhook carries the ticket data, so plan around what a ticket holds: the customer’s contact details, the message text and the status. Once Make has a sample, you can use those fields anywhere in the scenario.
A few routing ideas that need no code:
- By status. Use ticket.created to add a row marked “open” and ticket.solved to update it to “closed”.
- By keyword. Add a filter that looks for words like “refund” or “quote” in the message and send those to different people.
- By time. Tickets from the after-hours form can go to a morning digest instead of an instant ping.
Where do tickets come from? Visitors can leave a message through the away form when you are offline, and a chat can be turned into a ticket by your team. Both create the event your scenario listens for.
Testing
Make the scenario safe before customers rely on it
Automations fail quietly. A changed column name or an expired connection can stop follow-ups without any visible error. Build these three habits.
Use a test address
Run every change with a test ticket that has an obviously fake email. Delete test rows afterwards.
Handle errors on purpose
Turn on Make’s error notifications so a failed run reaches your inbox. Decide what should happen when the sheet is full or the email service is down.
Re-test monthly
Send one test ticket on the first of each month. Check the sheet, the mail and the message. It takes five minutes and catches silent breakage.
Also write down who owns the scenario. If the person who built it leaves, the connection should not leave with them.
Honest limits
What this route does not do
Be clear about the boundaries before you plan around them.
- No native Make module or app-store listing. The route is a webhook you set up yourself.
- Webhooks cover ticket.created and ticket.solved, not every message.
- No two-way sync. Make can receive events; it will not change a ticket’s status inside LiveChatBot unless you build that through the REST API.
- No WhatsApp inbox, no iOS team app, and “Powered by LiveChatBot” stays on every plan.
Make also has its own pricing and operation limits, which are separate from LiveChatBot. Check them against your expected ticket volume. If your needs are small, the free chatbot integration guide shows how to stay inside free limits.
Next steps
Start small with your chatbot with Make integration, then add branches
Do not begin with a ten-module scenario, and do not try to automate everything on day one. Build one: ticket in, row out. Run it for a week. Then add the email, then the filter, then the branch.
Keep a short log of each change and the date you made it. Each addition should solve a problem you actually saw, not one you imagined. If your first scenario just fills a sheet and your team checks it daily, that is already a working system.
Create your free account at livechatbot.in, turn on the away form so tickets have a source, and see the pricing page for the free plan limits. When you are ready for more connections, read how live chat API snippets can open chat from your own buttons.
Frequently asked questions
Does LiveChatBot have a native Make integration?
No. There is no Make module. You connect through webhooks that call a custom webhook in your Make scenario, or through Zapier or the REST API.
Which events can start a Make scenario?
The webhook events are ticket.created and ticket.solved. Everything else needs the REST API.
Do I need to code to build a chatbot with Make integration?
Not for a basic scenario. You paste a web address and map fields. A developer helps only for custom work such as two-way sync.
Is the webhook free on LiveChatBot?
Yes, webhooks are included on the free plan. Make has its own plans and limits.
Should I use Make or Zapier?
Use whichever you already know. Make suits multi-step branching; Zapier suits quick two-step links. Both can receive the same events.
Keep reading
Related guides
Chatbot With HubSpot Integration: What Real Integration Means, How to Test a Vendor’s Claim, and the Zapier Route LiveChatBot Offers (Free Handoff Checklist)
Connect your chat to Make
Free plan, webhooks included, no per-seat charges. Start free on livechatbot.in and build your first scenario.