New audio files added to a Google Drive folder are turned into text and logged in Google Sheets. The flow stores the file in Amazon S3, runs Amazon Transcribe, and then records the transcript, file name, and timestamps in a sheet for easy tracking. Teams that record calls, meetings, or training sessions can use this to keep a clean, searchable record with no manual copy and paste.

Here is how it works step by step. A Google Drive event starts the run when a file appears in a chosen folder. The file is uploaded to Amazon S3 and tagged so you know the source is Drive. The flow fetches the S3 object key, starts a Transcribe job using that S3 path, and pauses at a webhook until it is time to continue. It then checks the Transcribe job, prepares fields like recording name and transcription date, and appends a new row to Google Sheets A to D. This creates a simple pipeline from upload to transcript to log.

To set this up, you need Google Drive, Google Sheets, and AWS accounts with access to S3 and Transcribe. Give S3 and Transcribe the right permissions, set the Drive folder, and update the sheet ID and range. Expect faster turnaround, fewer data entry errors, and a higher daily volume with the same team. It is great for content teams, support groups, and operations that process voice notes or calls at scale.

• Google Drive event watches a specific folder and starts the run when a file is created.
• Amazon S3 upload stores the file and adds a source tag for easy tracking.
• Amazon S3 list retrieves the object key used to name and track the Transcribe job.
• Amazon Transcribe starts a job using the S3 media file path and a clear job name.
• Wait node pauses the run and resumes by webhook when you are ready to continue.
• Amazon Transcribe get checks job status and returns details for logging.
• Set node formats fields like recording name and transcription date.
• Google Sheets append writes one row per file across columns A to D.

• Reduce manual work from 20 minutes per file to 2 minutes
• Streamline audio processing by 80% from upload to log
• Improve logging accuracy by 90% by removing copy and paste
• Connect Google Drive, Amazon S3, Amazon Transcribe, and Google Sheets in one flow
• Handle up to 10 times more recordings without extra staff

1. 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.
2. You'll need accounts with Google Drive, Google Sheets, Amazon S3 and Amazon Transcribe. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create Google Drive OAuth. Double click the Google Drive Trigger node, choose Credential to connect with, click Create new credential, and follow the on screen steps to sign in.
4. Create Google Sheets OAuth. Double click the Google Sheets node, click Create new credential, and connect your Google account.
5. Create an AWS credential. Double click any AWS node, click Create new credential, and enter your AWS Access Key ID, Secret Access Key, and Region. Make sure the IAM user has S3 and Transcribe permissions.
6. Open the Google Drive Trigger node and set the folder to watch. Enable file download if you want to upload the exact file content to S3.
7. Open the AWS S3 upload node and set your bucket name. Map the file name to the Drive file name. If needed, map the binary data from the trigger to the File Content field.
8. Check the AWS S3 list node and make sure it points to the same bucket. Confirm it returns the uploaded object key during a test run.
9. Open the AWS Transcribe start job node and confirm the media file URI matches your bucket and key. Pick the correct language settings in AWS if required.
10. Open the Wait node and copy the webhook URL. Plan how you will call this URL when the transcript is ready. You can trigger it manually for testing or call it from an external monitor.
11. Open the AWS Transcribe get job node and verify the job name matches the one used when starting the job.
12. Open the Set node and map fields for recording name, transcription date, and transcript text. Make sure these match the values you want to log.
13. Open the Google Sheets node and set the target spreadsheet and range A:D. Use Append as the operation to add a new row per file.
14. Test end to end by uploading a small audio file to the Drive folder. Wait for the run to complete and check that a new row appears in the sheet with the transcript.
15. Troubleshoot common issues: fix AWS IAM permissions if S3 or Transcribe calls fail, confirm the bucket region, check that the audio format is supported by Transcribe, and verify the webhook call resumes the run.