LINE Chatbot Development with Dialogflow is a course in building chatbots on LINE Official Account that understand Thai messages with Dialogflow intents and entities, connect through the LINE Messaging API, send Flex Messages and pull data from Firestore or Google Sheets through fulfillment. It suits developers, business owners and customer service teams who run a LINE channel.
LINE is the main channel Thai customers use to contact businesses, so a chatbot on a LINE Official Account can answer repeated questions, collect details and hand work on at any time. Google's Dialogflow helps a bot understand Thai messages written in many different ways through intents and entities, without hand-writing a rule for every case, and connects to back-end data through fulfillment.
This course starts by creating a LINE Messaging API channel and a Dialogflow ES agent, then designs intents, entities, parameters and contexts for Thai conversations. Learners connect the agent to LINE both through the built-in integration and through their own Node.js webhook, send Flex Messages and quick replies, build fulfillment that reads data from Firestore and Google Sheets, and get to know Conversational Agents (Dialogflow CX) for more complex work, finishing with a product enquiry chatbot workshop. (2 days, 6 hours per day, 12 hours in total, Beginner level.)
Course Details
This course is the 2026 edition of LINE Chatbot Development with Dialogflow. It runs for 2 days, 6 hours per day (12 hours in total, 09:00-16:00), as lectures with labs. Beginner level. This edition keeps Dialogflow ES at its core, because it is still fully available and offers a no-cost Trial Edition, and adds Conversational Agents (the new name for Dialogflow CX), which Google recommends for complex bots. It adds writing your
own webhook with Node.js and the current @line/bot-sdk, sending Flex Messages and quick replies, and reading data from Firestore and Google Sheets. Learners use their own LINE Official Account and Google Cloud accounts; some services need a billing account and are charged by usage. This course differs from LINE AI Chatbot with Gemini and ChatGPT, which answers with an LLM directly. Learners take home a lab guide, sample agent files and webhook source code.
Section 1: An Overview of the LINE Messaging API
Section 2: Lab: Setting Up Your Tools
Section 3: Lab: Creating a LINE Official Account and Channel
Section 4: Introducing Dialogflow
Section 5: Lab: Intents, Entities and Parameters
Section 6: Lab: Contexts and Conversation Design
Section 7: Lab: Connecting Dialogflow to LINE
Section 8: Lab: Your Own Webhook with Node.js
Section 9: Lab: Fulfillment for Back-End Systems
Section 10: Workshop: Reading Data from Google Sheets
Section 11: Conversational Agents (Dialogflow CX)
Section 12: Workshop: A Product Enquiry Chatbot
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
An intent is what the user wants, such as asking a price or booking a slot. You add many training phrases to teach the bot which messages mean that intent. Parameters are values extracted from the message using entities, such as a date, product name or quantity. If details are missing, slot filling makes the bot ask until it has what it needs, and contexts carry values on to the next question.
There are two ways. The first is to create a Messaging API channel in the LINE Developers Console, enter its channel ID, channel secret and channel access token in Dialogflow's Integrations menu, then copy the webhook URL back into LINE and enable the webhook. The second is to write your own webhook with Node.js and @line/bot-sdk and pass messages to Dialogflow with detectIntent, which gives more control over replies.
Fulfillment is used when the bot must reply with data that changes with the real system, such as checking an order, looking up a price or saving a booking. When an intent with fulfillment enabled is matched, Dialogflow sends a request with the parameters to your webhook. Your code reads or writes data, for example in Firestore or Google Sheets, and returns the reply. You can write it in the inline editor or as your own webhook service.
Dialogflow ES designs conversations with intents and contexts and suits small to medium bots. It is still fully available and has a no-cost Trial Edition. Conversational Agents, the new name for Dialogflow CX, uses flows and pages as a state machine for complex conversations and adds LLM-powered playbooks and generators, but is charged by usage. Google suggests considering CX as bots grow more complex. This course starts with ES and gives an overview of CX so you can decide.
It suits developers who want to build chatbots on LINE OA, business owners and customer service teams who want fewer repetitive replies, marketing and IT teams who manage a LINE channel, and anyone interested. You do not need to program, since most work happens in the Dialogflow console, though some JavaScript makes the webhook labs easier.
Bring a laptop that can run the Node.js LTS release, VS Code and Git, a smartphone with the LINE app, and your own LINE and Google accounts. A free LINE Official Account plan and the Dialogflow ES Trial Edition cover most labs, but some topics, such as Conversational Agents or fulfillment running on Google Cloud, need the learner's own billing account and are charged by usage.
Articles are published in Thai.
Today's web sites, mobile apps and partner services all talk to each other through REST APIs, so teams that already use Django need to expose their data as APIs that are well designed, secure, documented and testable. The Django REST Framework is the standard…
REST is a way of designing web services that treats data as resources reached through URLs, communicates statelessly and uses HTTP methods such as GET, POST, PUT and DELETE for their intended meaning, returning JSON that mobile apps, web pages and other…
Web APIs sit at the heart of modern systems, serving single-page web apps, mobile apps, back-office services and integrations between organisations. A well-designed API speaks plain REST, validates data before saving it, reports errors in one consistent…
