LINE Vehicle Bot Admin

Operations

LINE Vehicle Support Dashboard

Last refreshed: -

- Checking

Main activity

Today, local time

Attention required

Items operators may need to review

Active Session

Current conversations that are not idle or complete

0 active

Session states

Share of current sessions by step

Activity

Repair requests, staff-contact requests, and recent checks

Pending users

Users waiting for approval or setup

Start Here

This dashboard controls your local LINE OA bot server. For a first test, confirm LINE settings, keep Vehicle API mock mode on, approve your LINE user, add one vehicle permission, then try the Test Console or your real LINE chat.

Use Server Settings to confirm your public webhook URL.
Use LINE Settings to save your channel token and secret.
Use Users & Permissions to approve who can check which plate.
Use Test Console to simulate messages before using real LINE.

Who Is Waiting

Session States

แจ้งซ่อม

ติดต่อเจ้าหน้าที่

Recent Vehicle Checks

Pending Users

LINE Settings

Connect this local bot server to your LINE Official Account. Get the Channel Access Token and Channel Secret from LINE Developers. The webhook URL shown here is the one to paste into LINE Developers.

Use in LINE OA: https://ma0bot.com/webhook/line

Server Settings

Controls how this app runs locally and how LINE reaches it through Cloudflare Tunnel. Cloudflare should route to http://localhost:3000; LINE should call the webhook URL shown below.

Vehicle API Settings

Choose how the bot looks up vehicle location: mock data for testing, the real API later, or Playwright browser automation as a temporary bridge. The LINE flow stays the same while you switch providers here.

Vehicle lookup modemock uses demo data, api calls the Vehicle API, playwright runs a browser flow once it is implemented. API enabled Use mock vehicle location response API base URLExample: https://api.company.com Endpoint pathExample: /vehicles/location HTTP methodChoose how the future API expects requests. Authentication typeSelect the authentication style your Vehicle API uses. Bearer tokenStored encrypted. Used only when auth type is bearer token. API key nameHeader or parameter name, for example X-API-Key. API key valueStored encrypted. Custom headers JSONAdvanced option. Must be valid JSON. Request parameter name for license plateExample: plate, licensePlate, or registrationNo. Example response JSONPaste a sample API response here for your reference.

Response mapping fields plate latitude longitude address speed ignition last update time vehicle name

Playwright lookup settings Playwright enabled Run browser headless Login URLVehicle portal login page or starting URL. UsernamePortal username, if needed. PasswordStored encrypted. Leave masked value unchanged to keep current. Expected vehicle labelOptional exact full vehicle label expected after search. Flow statusFor your notes while we build the browser flow. Flow notesPaste human-readable steps or selector notes here. Result mapping notesDescribe where plate, address, lat/lng, speed, ignition, and last update appear on the page.

Example request preview

Bot Flow Settings

Edit the wording the bot sends, the labels shown on LINE buttons, and the typed messages that trigger each action. Button labels also work when typed manually. For trigger fields, separate extra phrases with commas, for example Check Vehicle Location, location, รถอยู่ไหน.

Keep {{plate}} in the confirm plate message so the selected license plate appears in the reply.

Users & Permissions

Unknown LINE users are created as pending. Set a user to active before they can check vehicles. Customer ID is assigned manually here by you; later it can come from your CRM/customer system or Vehicle API if you connect one.

Use strict permission mode when each customer should only see specific plates. Use allow-all mode when every active user may check any vehicle.

Permission Settings

Users

Vehicle Permissions

Active Sessions

Shows where each user is in the guided flow. If someone gets stuck, click Clear to reset them back to the main menu. Sessions automatically expire after 10 minutes of inactivity.

Logs

Use this page to audit webhook events, user messages, permission checks, Vehicle API calls, and LINE replies. Filter by user, plate, result, or action, then export CSV when needed.

Test Console

Simulate a LINE user without opening LINE. Use the same LINE user ID that exists in Users & Permissions, then send messages like Check Vehicle Location, 1 กก-1234, and Confirm.