Meeting Transcript Analysis Flow Error

[nicolas]

https://www.gumloop.com/pipeline?workbook_id=iNecYLsWMBvENfRBHHoJqS&run_id=BuaWqdaA68VhkMDoeu8ck2

https://www.gumloop.com/pipeline?workbook_id=iNecYLsWMBvENfRBHHoJqS

I’m building an automation that:

1. Monitors a Google Drive folder for new meeting transcript files
2. Analyzes the transcript to identify ALL problems discussed
3. Creates structured problem briefs with names and descriptions
4. Emails these problems briefs (eventually will create Basecamp projects) in the correct lines e.g., problem name 1, description 1, name 2, description 2, etc.

Current Issue

My flow fails with this error:

Invalid Google Drive file link or ID. A proper Google Drive file link must start with 'https://drive.google.com/file/d/'

The Google Drive Folder Reader successfully finds files, but the Google Drive File Reader can’t process the file format it receives.

My Current Flow Structure

1. Google Drive Folder Reader - Monitors a specific folder for transcript files
2. Google Drive File Reader - Attempts to read the file contents but fails
3. Join List Items - Combines file contents into one text
4. Chunk Text - Splits text into manageable chunks
5. Extract Data - AI analyzes text to identify problems and descriptions
6. Flatten List of Lists - Processes the extracted data
7. Combine Text - Formats problems and descriptions
8. Gmail Sender - Sends email with the analysis results

What I’ve Tried

• Checked the Google Drive Folder Reader configuration
• Verified the file format in Google Drive
• Added Error Shield to catch failures
• Tried different connection configurations

Questions

1. How do I correctly connect the Google Drive Folder Reader to the File Reader?
2. Is there a specific format needed for the file links?
3. Should I be using a different approach to read the file contents?
4. Are there any example flows that successfully read and process Google Drive files?
5. Is there anything I’m missing to ensure this runs properly?

Any help would be greatly appreciated! I’m trying to automate our weekly meeting follow-ups to ensure no problems slip through the cracks.

[Gumloop_Bot]

Hey @nicolas! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
   

3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

[Wasay-Gumloop]

Hey @nicolas – The Google Drive Folder Reader node outputs the file object itself (denoted by the file name), not the drive or the file link. Hence you can pass the output onto a standard File Reader node to scrape the contents.

On the File Reader node you can hover and select Configure Inputs and enable File Name as a dynamic input:

Next, you can pass the File output from the Drive Folder Reader node onto the File Reader node:

Let me know if this makes sense and works for you

[nicolas]

It makes sense! However, it didn’t work. Run here.

It appears that the file reader is attempting to identify individual file types, despite the Google Drive Folder Reader correctly scanning the files.

I went over multiple possibilities with Gummie but it’s honestly tripping and consistently going agaisnt having a File Reader node at all

[Wasay-Gumloop]

Yeah this is super strange. Do you mind deleting and re-adding the Google Drive Folder Reader node and giving it another run please?