How to Automate LINE to Google Drive File Intake?
Description
Handle file messages from LINE in one place. Incoming images, videos, or documents are saved into Google Drive and recorded in Google Sheets. A simple reply can confirm the upload back to the sender when enabled.
A webhook listens for LINE events and reads settings from a Google Sheet, including the parent folder, allowed file types, and whether to reply. The flow builds folder names by date and by file type based on flags, then searches Google Drive and creates any missing folders. It downloads the file from the LINE API, checks the MIME type, and renames it with the event timestamp before upload. A log entry adds the file name, type, time, and a Drive link. If replies are on, a message goes back to the user through LINE.
You will need a LINE Messaging API channel, Google Drive access, and a Google Sheet for the config. After setup, teams get structured storage, clear audit logs, and faster handling of customer files. This is useful for support teams receiving IDs, receipts, or claims, and for operations staff who collect media from the field. Expect fewer errors, less manual sorting, and quicker response times.
Tools Required
What this workflow does?
- Webhook capture of LINE file messages and events
- Config driven setup from Google Sheets for parent folder, allowed types, and reply rules
- Smart folder structure by date and by file type with on demand creation in Google Drive
- File validation by MIME type before upload to keep storage clean
- Timestamp based file naming using the LINE event time
- Upload to the correct parent folder and log the Drive link
- Google Sheets logging of file name, type, upload time, and URL
- Optional LINE reply to confirm success or report errors
What are the benefits?
- Reduce manual download and upload work from 30 minutes a day to under 5 minutes
- Automate folder routing and naming to cut filing errors by up to 90%
- Unify LINE, Google Drive, and Google Sheets so teams can find files and logs fast
- Scale to handle high message volume without adding staff
- Block unwanted formats by enforcing an allowed file type list
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with LINE Messaging API, Google Drive and Google Sheets. See the Tools Required section above for links to create accounts with these services.
- Create a LINE Messaging API channel and get your Channel access token. In the LINE Developers console, set the webhook URL to the test URL shown in the LINE Webhook Listener node in n8n, then enable the webhook.
- In n8n, double click the Get File Binary Content and Send LINE Reply Message nodes, create a new HTTP Header credential, and add Authorization: Bearer your LINE Channel access token. Save the credential and select it for both nodes.
- Open the Get Config node in n8n and click the credential dropdown to create a new Google Sheets OAuth2 credential. Follow the on screen steps and grant access to your Google account.
- Open the Google Drive nodes (Search, Create, Upload) and create a Google Drive OAuth2 credential. Follow the on screen steps and grant access to the same Google account.
- Prepare a Google Sheet for settings. Include fields for Parent Folder ID, Store by Date, Store by File Type, Allowed Types, and Reply Enabled. Enter your Parent Folder ID from Google Drive.
- In the Get Config node, set the sheetId and range to your config sheet. Make sure the column names match the fields used by the workflow.
- Click Execute Node on the LINE Webhook Listener to expose the test URL. Send a file to your LINE bot and confirm the webhook receives the event.
- Check Google Drive to see that date and file type folders are created as needed and that the file is uploaded with a timestamped name.
- Open the logging Google Sheet to confirm a new row with file name, type, upload time, and Drive link. If nothing appears, verify the Sheets credential and the range mapping.
- If the bot replies with a type not allowed message, update the Allowed Types list in your config sheet. When testing is complete, switch the webhook to the production URL in the LINE Webhook Listener node and update the LINE console.
Need help or want to customize this?
Ask in the Free Futurise Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
