LINE OA Streaming Import Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

LINE Messaging Office Account (OA) helps you collect customers' conversational and behavioral data and then use it for analytics, triggers, and personalization for marketing purposes. With this integration, you can import message/event data from LINE OA into Treasure Data.

Supported Webhook Events

This integration receives all webhook events sent by LINE Messaging API, including:

• Message events (text, image, video, audio, file, location, sticker)
• Follow events (when users add your account as a friend)
• Unfollow events (when users block your account)
• Join events (when your account joins a group or room)
• Leave events (when your account leaves a group or room)
• Member join/leave events
• Postback events
• Beacon events
• Account link events
• Device link/unlink events

For a complete list of webhook events and their data structures, refer to the LINE Messaging API documentation.

Prerequisites

• Basic Knowledge of Treasure Data.
• Basic knowledge of LINE Messaging Office Account

Requirements and Limitations

• Support fetching conversational data
• The LINE webhook has to be enabled
• The LINE Messaging API has to be enabled
• The webhook link should be set up correctly
• You must create a database and tables in Plazma before creating sources to ingest data in those tables
• LINE Messaging API only allows one webhook URL per channel. If you need to use multiple tools that require webhooks or have existing system integrations, you must use an intermediary service like Zapier to distribute webhook events to multiple destinations including Treasure Data

Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following link:
https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/

Import from LINE OA via TD Console

Create Authentication

1. Perform the following steps to create a new authentication with a set of credentials.
2. Select Integrations Hub.
3. Select Catalog.
4. Search for your Integration in the Catalog; hover your mouse over the icon and select Create Authentication.

5. Ensure that the Credentials tab is selected and then enter credential information for the integration.

New Authentication Fields

Create a Source

1. Open TD Console.
2. Navigate to Integrations Hub > Authentications.
3. Locate your new authentication and select New Source.

Create a Connection

1. Type a source name in the Data Transfer Name field.
2. Select Next.
3. The Create Source page displays with the Source Table tab selected.

Identify a Source Table

1. Configure the destination table where LINE OA data will be stored.

2. Select Next.

Data Preview

You can see a preview of your data before running the import by selecting Generate Preview. Data preview is optional and you can safely skip to the next page of the dialog if you choose to.

1. Select Next. The Data Preview page opens.
2. If you want to preview your data, select Generate Preview.
3. Verify the data.

Data Placement

For data placement, select the target database and table where you want your data placed and indicate how often the import should run.

1. Select Next. Under Storage, you will create a new or select an existing database and create a new or select an existing table for where you want to place the imported data.

2. Select a Database > Select an existing or Create New Database.

3. Optionally, type a database name.

4. Select a Table> Select an existing or Create New Table.

5. Optionally, type a table name.

6. Choose the method for importing the data.

   • Append (default)-Data import results are appended to the table. If the table does not exist, it will be created.
   • Always Replace-Replaces the entire content of an existing table with the result output of the query. If the table does not exist, a new table is created.
   • Replace on New Data-Only replace the entire content of an existing table with the result output when there is new data.

7. Select the Timestamp-based Partition Key column. If you want to set a different partition key seed than the default key, you can specify the long or timestamp column as the partitioning time. As a default time column, it uses upload_time with the add_time filter.

8. Select the Timezone for your data storage.

9. Under Schedule, you can choose when and how often you want to run this query.

Run once

1. Select Off.
2. Select Scheduling Timezone.
3. Select Create & Run Now.

Repeat Regularly

1. Select On.
2. Select the Schedule. The UI provides these four options: @hourly, @daily and @monthly or custom cron.
3. You can also select Delay Transfer and add a delay of execution time.
4. Select Scheduling Timezone.
5. Select Create & Run Now.

After your transfer has run, you can see the results of your transfer in Data Workbench > Databases.

Copy the Source ID

The source ID (UUID v4) is issued upon Source creation.

After creating the Source, you are automatically taken to the Sources listing page.

1. Search for the source you created.
2. Click on "..." in the same row and select Copy Unique ID.

This Unique ID is the Source ID required when configuring the webhook URL in LINE Messaging API.

Configure Webhook URL in LINE Messaging API

To receive LINE OA events in Treasure Data, you must configure the webhook URL in your LINE Messaging API settings.

1. Log in to the LINE Developers Console.

2. Select your LINE Official Account channel.

3. Navigate to the Messaging API tab.

4. In the Webhook settings section, enter the webhook URL:

   For US region:

   https://line-in-streaming.treasuredata.com/v1/task/{source_id}

   For Tokyo region:

   https://line-in-streaming.treasuredata.co.jp/v1/task/{source_id}

   Replace {source_id} with the Source ID you copied in the previous step.

5. Click Verify to test the webhook connection.

6. Enable the Use webhook toggle.

7. Optionally, enable Webhook redelivery to retry failed webhook deliveries.

8. Click Update to save the settings.

Data Ingestion

The connector can start ingesting LINE OA event data into Treasure Data as soon as the first event is triggered after successful webhook configuration and source creation.

Data Schema

Events Table Schema

The Events Table contains detailed webhook event data from LINE Messaging API. Each row represents a single webhook event with the following structure:

Example Event Data

Message Event Example:

{
  "event_mode": "active",
  "event_type": "message",
  "event_deliverycontext": "{\"isRedelivery\":false}",
  "event_timestamp": 1764739548058,
  "destination": "U26272c69eb9c705cdb310034a13d8a2c",
  "event_source": "{\"userId\":\"U7df7e1515baea0a9898c2d8553d016d1\",\"type\":\"user\"}",
  "event_webhookeventid": "01KBHAS125354QY30EQDB80MXV",
  "event_replytoken": "a24d6cd95f4e4cceb74505a3c67fa1f0",
  "record_uuid": "c32f42c1-6464-312e-8a73-64b19c6c8116",
  "event_message": "{\"text\":\"Hello\",\"id\":\"590404062261018659\",\"type\":\"text\"}",
  "time": 1764739556
}

Postback Event Example:

{
  "event_mode": "active",
  "event_type": "postback",
  "event_deliverycontext": "{\"isRedelivery\":false}",
  "event_timestamp": 1764739548788,
  "destination": "U26272c69eb9c705cdb310034a13d8a2c",
  "event_source": "{\"userId\":\"U7df7e1515baea0a9898c2d8553d016d1\",\"type\":\"user\"}",
  "event_postback": "{\"data\":\"second-menu\",\"params\":{\"newRichMenuAliasId\":\"second-menu\",\"status\":\"SUCCESS\"}}",
  "event_webhookeventid": "01KBHAS1TNJ9W3GZZSAYG8WSEW",
  "event_replytoken": "e6a713af40ed416e8844db6638705d01",
  "record_uuid": "5289e93e-d7c2-3a7d-9ba0-8de86cc53e4f",
  "time": 1764739552
}