Workflow Entry & Configuration

This section initializes the workflow by listening to incoming requests from the LINE Messaging API and retrieving configuration details from Google Sheets. It merges the event data with the config, then determines initial folder information (such as whether to store files by date or file type). Nodes in this group:

• LINE Webhook Listener Receives POST requests (file messages) from LINE.
• Get Config Reads configuration data (parent folder, allowed file types, etc.) from a Google Sheet.
• Merge Event and Config Data Combines the LINE event data and config data.
• Determine Folder Info Calculates folder names based on the config (e.g., date folder name, file type folder name).

Folder Search & Creation

This section handles the logic for finding or creating the appropriate Google Drive folders. It checks if a date folder exists (when Store by Date is enabled) and whether a file type folder is required (when Store by File Type is enabled). Nodes in this group:

• Search Date Folder / Check Existing Date Folder / Check if Store by Date is Enabled Looks for or creates a date-based folder.
• Create Date Folder / Set Date Folder ID reates and stores the date folder ID if it doesn’t exist.
• Search File Type Folder / Check Existing File Type Folder / Check if Store by File Type is Enabled Similarly handles file type subfolder logic.
• Create File Type Folder / Set File Type Folder ID Creates and stores the file type folder ID.
• Merge Final Parent Folder Data / Configure Final Parent Folder ID Merges the final folder IDs (date folder + file type folder) to determine where the file should be placed.

Upload, Log, & Reply

Once the file is validated and the correct folder determined, the workflow uploads the file to Google Drive and logs the details in a Google Sheet. Finally, it checks whether replies are enabled and, if so, sends a message back to the LINE user (either confirming a successful upload or reporting an error). Nodes in this group:

• Upload File to Google Drive Uploads the validated file to the determined folder path.
• Log File Details to Google Sheet Records the file name, upload date, URL, and file type in Google Sheets.
• Check Reply Enabled Flag Verifies if replies to LINE are turned on in the config.
• Send LINE Reply Message Sends a text reply back to the user via LINE, either containing the file’s Google Drive URL or an error message.

File Retrieval & Validation

In this group, the workflow fetches the binary content of the file from the LINE API and validates whether the file type is allowed (e.g., image, audio, video). If the file type is not permitted, the workflow throws an error which will be used to send an appropriate reply message back to LINE. Nodes in this group:

• Get File Binary Content Retrieves the actual file data from the LINE Messaging API.
• Validate File Type Checks the file’s MIME type against an allowed list from the config and throws an error if disallowed.

Line Save File to Google Drive and Log File's URL

Purpose and structure

This folder contains the Line Save File to Google Drive and Log File's URL workflow. Its executable nodes use code, googleDrive, googleSheets, httpRequest, if, merge, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

LINE Webhook Listener

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1924_Code_Webhook_Export_Webhook.json MIT; preserve source notices.